distill: Collapse the component-invoked TypeScript capabilities into verbs on one named executable

[sameera]

Distillation: Collapse the component-invoked TypeScript capabilities into verbs on one named executable

Drained queue entry: .nexus/queue/epic-247/ (provenance: #247)

The why comes from the epic's decision record (#277, hash-verified against the stamp in close-record.md) plus the epic issue's close comment — quoted there since close-record.md is added-then-deleted within this branch and won't show in the diff below.

verb-reachability — create

• What changed: New page capturing the declarative verb-registry pattern: a capability becomes reachable by name — a verb on one shared executable — exactly when a Nexus component invokes it. Covers the eager static registry, hoisting the process boundary out of every capability into one dispatcher, the two parity axes (durable source-vs-build, temporary legacy-vs-verb), and hermetic effect parity for capabilities driving external programs.
• Why (Decision Log entry): "Ten more component-invoked capabilities become verbs on one shared, eagerly-dispatched registry" — a measured 410 KB build with negligible startup cost made lazy dispatch unnecessary; a probe build proved the import-time self-execution hazard is real (two capabilities fired on import and exited before the dispatcher ever ran); the migration axis, extended to already-migrated capabilities, caught a live stdout/stderr divergence in the workspace-status read-out.
• Provenance: Collapse the component-invoked TypeScript capabilities into verbs on one named executable #247 (Collapse the component-invoked TypeScript capabilities into verbs on one named executable #247)
• Reciprocal edits: portable-tooling, nexus-setup-cli, pr-worktree, close-entry-migration, record-digest, distiller, issue-sourced-planning

portable-tooling — update

• What changed: How It Works notes the ten new verbs now dispatching from the shared registry alongside the five distiller tools' own standalone builds. New Decision Log entry covers the distributable's growth, the two-axis parity, the broadened five-facet effect comparison, and the payload boundary's move to a structural composition check (no vendored file may import a workspace package) with a shrink-only waiver register — plus the acceptance harness relocating outside the vendored tree and losing its agent-invocable skill form.
• Why: Same decision record; the payload-boundary and harness-relocation rationale specifically.
• Provenance: Collapse the component-invoked TypeScript capabilities into verbs on one named executable #247
• Reciprocal edits: verb-reachability

nexus-setup-cli — update

• What changed: New Decision Log entry: this CLI's own verbs now dispatch from the same shared registry as the newly reachable capabilities, and the workspace-status read-out's failure diagnostic is now standard error in both its script and verb forms (a real divergence the migration-axis parity caught).
• Why: Same decision record, migration-axis-parity finding.
• Provenance: Collapse the component-invoked TypeScript capabilities into verbs on one named executable #247
• Reciprocal edits: verb-reachability

pr-worktree, close-entry-migration, record-digest, distiller, issue-sourced-planning — update

• What changed: Each gains one mechanical reciprocal Integration Points bullet + Decision Log entry ("Reciprocal link from verb-reachability"), recording that the capability each page documents is now also reachable as a verb on the shared executable, held to the same byte-identical parity as its script form.
• Provenance: Collapse the component-invoked TypeScript capabilities into verbs on one named executable #247

Anchors refreshed (derived, never hand-edited)

• .nexus/anchors/verb-reachability.md @ ca05536 (new)
• .nexus/anchors/portable-tooling.md, nexus-setup-cli.md, pr-worktree.md, close-entry-migration.md, record-digest.md, distiller.md, issue-sourced-planning.md @ ca05536

Atlas regenerated (derived)

• docs/concepts.md (54 concepts)

Consumed queue entries (removed by this PR)

This PR already removes the drained entry on the branch, so the merge deletes it from main atomically with the page writes — no manual post-merge step:

• .nexus/queue/epic-247/ (recoverable via git history)