Add the French-report goal to /discover (5-node report.* chain)

[enricopiovesan]

Depends on traverse-framework/registry#426 — specifically the 5 deterministic capabilities
report.collect-fragments / report.enrich-insights / report.summarize / report.translate-fr /
report.format at @1.0.0, all pure_read / deterministic on the live catalog.

What

Add a 4th /discover goal that plans and executes a real 5-node governed chain — the deepest
example on the page (current goals are a 2-node doc-approval chain + two single-capability goals).

• src/scripts/discover.js — new GOALS entry:
  • label: "Assemble a French project report"
  • target: { capability_id: 'report.format', capability_version: '1.0.0' }
  • candidate_refs: all 5 report.* caps at 1.0.0
  • starting_facts: { fragments: [ 3 UMA-style browser/edge/cloud strings ], project_name: 'UMA Runtime Atlas' }
• Structural chain the planner should derive:
  collect-fragments -> enrich-insights -> summarize -> translate-fr -> format

DoD

• CHECK_REGISTRY=1 npm test — 5-node plan derived; review gate clears mapping_unconfirmed;
  executeBrowserComposedWorkflow -> terminal_state: "succeeded", all 5 node_outcomes succeeded
• new tests/e2e/discover.spec.mjs spec — goal plans a 5-node chain, executes, trace shows all
  five report.*@1.0.0 ids, terminal: succeeded
• tests/discover-truthfulness.test.mjs unchanged and green (no model/NL strings introduced)
• G6 graph renders 5 nodes (existing renderPlanGraph handles arbitrary counts)
• npm run build clean

Not in scope

• report.summarize-semantic (registry#432) — added later as an alternate candidate on this goal
  only if it ships determinism_class: deterministic
• no change to the 3 existing goals

---

This should be tracked as an "App Reference" (Project 2) ticket — Status: Blocked (blocked-by
registry#426), Agent: Unassigned until the registry side is merged.

[enricopiovesan]

Blocked on traverse-framework/registry#441, not just #426. The 5 deterministic report.* capabilities are published but the chain does not compose in browserLocalPlan — every node past report.enrich-insights needs inputs from two upstream nodes, and the browser-local planner only builds single-parent chains. #441 reshapes the chain (linear pass-through, new 1.1.0 versions) so it plans end to end. Verified today: report.collect-fragments → report.enrich-insights plans + executes; + report.summarize returns 0 proposals.