[endrix]

Summary

The hierarchy outline (modelled on mlir-viewer's) lists views by instance name. That's the whole story for a workflow hierarchy, but too little for a product whose units have their own structure: a specification's chapters, its documents by title, and the clauses in each. This lets a producer shape its rows, with optional fields on HierarchyOutlineEntry:

• role: 'group': a heading over other rows (a folder, a layer) that only opens and closes. It's transparent to paths (hierarchyPathChildren): hierarchyEntryAt and the trails look through it, so a document's path is still its id and a group is never a crumb. While rendered, rows are kept by row id, since a group has no path to look it up by.
• role: 'node': a node inside the view above, named by the producer's nodeId and found through wf:graphNodeId. That key is now on every node: the same line feat: links, file targets and editable fields in the property panel #100 and feat: a status source, node states from a report drawn with the run overlay #101 add, so whichever merges second resolves a one-line overlap.
  • A click selects and centres the node, opening that view first when another is shown.
  • A double click runs the canvas's own double-click listeners on it, so it does what the canvas would.
• label, detail, family, badges: what the row says and what follows it (the filter matches both), the node family's colour from the profile, and badges in the header's tones.
• Current row: the current view's row opens along with its own group rows, so the units on screen are listed.
• Layout: a labelled row drops the file chip; the detail gives way before the label; the panel takes up to 380 px, never more than half the editor.
• clientBehavior.outlineTitle: the panel's title and its button's tooltip ("Hierarchy" by default). The filter just says "Filter…".

A hierarchy that sets none of these renders and behaves as before (the existing outline tests hold).

The ndf CLI (PTO-ISA/normative_language#8) now emits such an outline: folders, documents by title, and clauses under their refinement layers, with kind and modality. picorv32's is 357 rows.

Test plan

• npm run typecheck, npm run check:neutrality, all four suites
• hierarchy-outline.test.ts (+5): looking up through groups by a row's own path, a trail with no group crumb, opening down to the current view including its groups, label/detail and filtering by either, finding a node by producer id.
• Headless on the integration branch, with the real client, the NDF profile and picorv32's 10-architecture/pipeline.md as the current view:
  • The panel lists chapters, documents and the current document's layers and clauses, with colour chips and badges.
  • Clicking a clause selects it on the canvas.
  • Double-clicking it opens its refinement trace in place, and only that (see the fix on feat: links, file targets and editable fields in the property panel #100).
  • Filtering FSM-LATCH leaves its path open.
  • Clicking that clause, which is in another document, requests that document's view, with the selection to follow.
• Live in VS Code: the selection after an in-place open lands on the clause.

https://claude.ai/code/session_01E8WfqKknDNN6xpNVcJL5K8