feat(unic-archon-dlc): adopt wayfinder as the pre-spec planning Box

[orioltf]

Adopt Matt Pocock’s wayfinder Method (v1.1.0, skills/engineering/wayfinder) as a pre-spec planning Box.

Why

wayfinder is the headline of v1.1.0 and its author’s recommended default in place of grill-with-docs whenever the work is too big for one agent session. It charts a loose idea as a map on the issue tracker: sub-issues with blocking relationships, each scoped to the size of one agent session, typed research / grilling / prototype / task. When the map is complete it feeds to-spec.

It independently arrives at two decisions this plugin already made — ADR-0013 (the tracker is the single source of truth for "where are we") and ADR-0007 (blocked-by canonical sequencing). That convergence is a strong signal it belongs here.

It also fits the DLC’s productivity thesis precisely: a HITL orchestrator that emits AFK work. The human works the grilling and prototype tickets; the research tickets are dispatchable to an Archon run (#276). That is the on-ramp pattern of ADR-0024, pointed at the pre-spec phase instead of intake.

Design questions for the ADR

1. Container. wayfinder is human-paced, so it is a command/skill, not an Archon workflow (ADR-0017). Confirm.

2. Relationship to /explore. wayfinder + research overlap /explore’s research pipeline, and a tracker map is arguably better than findings.md. Does /explore shrink to the AFK spike + spike/<slug> preservation, or retire outright?

3. Relationship to /specs. A completed map feeds to-spec. Does the map become a recognised /specs input alongside the existing branch-on-input paths (ADR-0020)?

4. Ticket types vs the label taxonomy. wayfinder’s research / grilling / prototype / task types must map onto classification.labels rather than introducing a second vocabulary — the same single-source-of-truth binding /triage performs (ADR-0024).

   Corrected 2026-08-05 — the premise was overruled by practice. PR chore: de-dogfood unic-archon-dlc and upgrade Matt's skills to upstream main #298 admits wayfinder:* as a fifth, tool-scoped label namespace in this repo (wayfinder:map, :research, :prototype, :grilling, :task), deliberately separate from the state / type / priority / area tiers, with ADR-0032 amended rather than superseded to record it. So the open question is no longer “how do we avoid a second vocabulary” but: does the DLC bind wayfinder’s types to classification.labels, or does it adopt a tool-scoped namespace the way this repo did? A tool-scoped namespace is not the drift risk ADR-0024 guards against — that rule exists because /triage, /tickets and /build must agree on state, and a wayfinder ticket type is not a state. Grill this against the repo’s own experience once /wayfinder has actually run here.

5. Dispatch. Does the DLC auto-dispatch AFK-typed map tickets, or does the human dispatch them?

Blocked by

#281 — the box set is deliberately frozen at nine for the v1.1.0 migration.

Context

Locked in a grilling session on 2026-07-31 and deferred so the migration would not become a second redesign. See #279 for the Harness/Method design this builds on.

[orioltf]

Two inputs from PR #298, which lands /wayfinder in this repo as a driver before this issue adopts it as a Box.

Open question 4 is corrected in the body — its premise ("must map onto classification.labels") was overruled by the repo choosing a wayfinder:* tool-scoped namespace on purpose.

Grill this after /wayfinder has run here, not before. #298 hand-authors the Wayfinding operations section of docs/agents/issue-tracker.md from upstream's GitHub template and leaves the five wayfinder:* labels to be created post-merge, deliberately — label creation mutates the live repo and reverting the PR would not undo it. The first real run (map issue + a child sub-issue + a native blocked_by edge) is the experience report this issue needs, and it will answer questions 2 and 5 far more cheaply than reasoning will: whether /explore shrinks or retires, and whether the DLC auto-dispatches AFK-typed map tickets.

Method availability, corrected. wayfinder ships at v1.1.0 — it was that release's headline — so the pinned bundle tag already contains it. What it is missing from is the DLC's manifest: the 11 entries in lib/methods-manifest.mjs, which were scoped to the frozen box set. Adopting wayfinder therefore means one new manifest entry plus one more vendored directory, and no pin change is required.

Separately, the pin is aging on content: the bundle is v1.1.0 (METHODS_BUNDLE, commit d574778) while upstream is 124 commits ahead with v1.2.0 cut on 2026-08-05, and 7 of the 11 bundled Methods have changed text — including grilling, which wayfinder composes. Worth bumping before or alongside this issue so the adopted Method and its dependencies are one consistent generation.