CMDB: document the rebuilt object detail page
The v2 layout is now object.php, so the user page and the two developer
guides that described the old one are updated.
CMDB.md — the detail-page section is rewritten:
- header: class icon, the signal colour taken from the item's own data,
and the chips that are also the controls (state, parent)
- the four headline numbers, and what each one means
- Details: cards for filled fields, empty ones collapsed
- Connections: the merged panel, with a table of the four KINDS and how
each one is created, and why the tally counts by kind rather than by
direction
- "Adding a relationship — in either direction", with the worked preview
sentence — this is new capability, not just a new layout, so it gets
its own section
- blast radius reframed as a left-to-right chain
- Impact Panel / Inline Mini-Graph sections removed; a note explains what
they were merged into and why
Developer guides:
- foundations: the detail-page file-table row, and a new warning under
"two kinds of link" that a relationship ROW is directional and the UI
can now write it either way — no direction column, no second row, the
inverse still comes from inverse_verb at render time. Anything creating
a relationship must decide which end is the subject rather than
assuming it is the current object.
- impact guide: renderBlastRadius() -> blastHtml(), and a note that
cmdbDirectImpact()'s buckets are now consumed by connectionsHtml() /
connectionTally() instead of being rendered as three panels.
Three i18n lessons added to the foundations guide's verification section,
all earned this session:
- parity is NOT enough — audit placeholders too. {depth} was added to
blast_headline_other in EN only and parity passed perfectly.
- keys built by concatenation are invisible to a grep.
- prove there are no unresolved keys from the RENDERED page, since a
missing key falls back to its own name.
Checked: every pathed file reference still resolves, all three internal
anchors resolve, no object2 references remain anywhere.
CMDB: correct drift in the three developer guides and the module page
Small factual fixes found while auditing docs/cmdb.md against the code:
- foundations guide claimed "three" AI features and listed two. The third,
"suggest a relationship", only ever existed in the design doc. Says so
now, with a warning to check api/cmdb/ before trusting that doc.
- file table was missing create_impact_diagram.php (#973), the three AI
settings endpoints, cmdb/help.php, and the ticket_cmdb_objects table.
- known gaps now list the tree view and the unbuilt AI feature.
- impact guide s11 said the graph visualisation was still V2 "and this
ships as a grouped list" - contradicting s10 on the same page, which
documents the Network Mapper handoff that answers it.
- lang key counts had drifted (582 and 547 against an actual 586). The
foundations guide carries the total; the impact guide no longer repeats
a number that has to be maintained in two places.
- CMDB.md said the help guide has 12 sections; it has 14.
- CMDB.md now frames docs/cmdb.md as pre-build design rationale rather
than "the full design and roadmap", and lists ticket_cmdb_objects.
Pairs with #974 in the app repo.
CMDB: document the blast-radius diagram handoff
Records why this is a handoff to Network Mapper rather than a second
graph renderer, and the layout/connector/provenance rules.
CMDB: impact analysis developer guide + blast radius on the user page
The module had no developer guide at all despite being the most complex
one, so this adds the first: how the blast radius is computed, why most
links are deliberately ignored, and the two traps (direction is not a
boolean; a function_exists guard on the company filter fails open).
Scoped per feature to match the other guides. A foundations guide covering
the data model, class system and tenancy invariant is still owed.