[endrix]

Summary

The property panel shows a node's text, but nothing in it led anywhere: a webview doesn't navigate, so a link in a rendered body or a producer's fact did nothing, and a file the text named had to be found by hand. This lets a producer make its panel the place a reader works from:

• Links lead somewhere. One click listener sits on the panel.
  • #<id> selects that element and centres it. The id can be the diagram's own or the producer's, now kept on every node as wf:graphNodeId, since the diagram names a node after its label.
  • When the diagram doesn't draw the element, a file reference in the link's title ([X](#id "/abs/doc.md#L12")) opens instead.
  • http(s): and mailto: go to the browser.
  • Anything else goes to the host as a reference to resolve (open-reference.ts), tried in this order:
    1. an absolute path or file: URI;
    2. a path relative to the node's own file, then each folder above it up to its workspace folder;
    3. the workspace's files ending with that path, closest first, with a quick pick when several match.
  • #L12, #L12-L20 and :12-20 select lines; ::Name.member and #name land on the symbol's definition, else its first mention.
• meta.open: { file, line? } (wf:open): the file a node stands for, such as the code a specification clause names.
  • A double-click opens it at its line, ahead of a drill-down, the node's views or its definition.
  • The viewer listener stands back, so the file opens once rather than beside the definition.
  • Basic Info shows it as an Opens link.
• Producer-editable fields in any profile. A meta.parameters entry marked editable: true gets a Fields section, committed through the existing updateNodeParameter as typed (unquoted).
  • choices gives a select; suggestions gives an input with a list.
  • Until now the panel edited parameters only for a network runtime (networkPropertySections), as source expressions with an add row. That editor is unchanged.
• clientBehavior.propertySections: { ports?, annotations?, parameters?, entityType? }: false hides the port lists, the raw definition annotations, the definition-parameters section, or Basic Info's task/workflow Type row and its change-type button.

All neutral: the platform reads link syntax, a file target and field metadata; the product says what they are.

A double-click opens one thing (a later commit): on a node that isn't a network instance, the network navigation listener opens its first view (or, with doubleClickOpensSource, its definition), and the viewer listener also opened its definition as a preview. A specification clause opened its refinement trace and its heading at once. The viewer listener now steps aside whenever the other one opens something; a node nothing else opens still gets its definition (double-click-opens-one-thing.test.ts, 3 tests).

Merging with #92 (Facts): the two conflict where each adds a section under Basic Info. I'd resolve it as Basic Info, then Fields, then Facts (the integration branch does), so the values a person edits sit above facts that end with a long body.

Test plan

• npm run typecheck, npm run check:neutrality, all four suites
• New tests:
  • open-target.test.ts (7): the open target from a node or its ancestors; a real, non-preview open at the 0-based line; link classification (element, element with a file fallback in its title, URL, reference, script refused); the reference action's flags and base.
  • producer-fields.test.ts (3).
  • node-open-target.test.ts (4): the server maps meta.open, keeps wf:graphNodeId, and passes editable parameters through.
  • open-reference.test.ts (9): parsing every form, the folder walk, trailing-path search ranking, symbol lines.
• Headless, on the integration branch with the real client and a picorv32 NDF document:
  • The panel shows Basic Info, Fields (5) and Facts.
  • A link to a clause the diagram draws selects it; one it doesn't draw sends the open-reference action for its file at the heading line.
  • picorv32.v:1202-1210 sends the open-reference action with the clause's document as base.
  • A double-click on a source clause sends exactly one navigate action, to gen/membus/memif.py at the def hold_take line.
• Live in VS Code: the host resolving and opening those references (the quick pick for picorv32.v, which several files match), and a field edit round trip through ndf-sidecar.

https://claude.ai/code/session_01E8WfqKknDNN6xpNVcJL5K8