Add a GitHub Issues backend to Pathfinder

Chart Step 1 now asks where the map should live: local files under
gitignored specs/ (the default) or a pathfinder:map issue whose decision
questions are its sub-issues, driven by gh. The pick is recorded as the
first Ground rules bullet and never re-asked; Auto-Discovery resolves
either backend, and an issue URL routes straight to github.

On github the local model maps onto the tracker's own primitives rather
than being simulated in issue bodies: sub-issues, native issue
dependencies for blocking, the assignee as the claim, one
pathfinder:<type>-<mode> label so type and mode cannot drift, and an
Answer comment plus a close reason that distinguishes a decision from a
question ruled out of scope. Both wiring calls key on the database id,
not the number. The map body therefore carries no checklist at all.

Sketches, secrets and the PLAN-DRAFT stay on local disk regardless --
plan2code-1-plan discovers its input with ls specs/ and has no notion of
a tracker. github is only offered after a five-check preflight, and the
offer names the repo's visibility, because a map on a public tracker
publishes the destination and the codebase recon. The Step 3 recon is
held until Step 6 so the no-fog off-ramp leaves no litter.

Depth lives in a seventh reference file; the orchestrator was
recompressed to absorb the new section within the 11,000 char limit by
removing duplication with its references. Adapted from the GitHub
tracker doc behind Matt Pocock's wayfinder skill (MIT).

AI Assisted

README.md

@@ -166,7 +166,9 @@ it as requirements, so planning would just invent the answers. Pathfinder finds
 destination; Step 1 then walks it.
 
 1. **Name the destination** — one or two lines fixing what this effort is finding its way to. Settled
-   first, because it fixes scope.
+   first, because it fixes scope. It also asks where the map should live: **local files** under
+   gitignored `specs/` (private, solo — the default), or **GitHub Issues** (a map issue with one
+   sub-issue per decision, native blocking, so your team can see and work the frontier in the tracker).
 2. **Chart the map** — a breadth-first grilling surfaces the open decisions. Anything you can phrase
    *sharply* becomes a question file; anything you can only sense stays listed as fog.
 3. **Clear one question per session** — resolving a question burns off the fog behind it, graduating
@@ -182,7 +184,8 @@ react to) · `legwork` (manual work that has to happen before a decision is poss
 It never answers its own questions, and it **plans, it never builds.** When the urge to just build it
 arrives, the map is done. Skip Step 0 entirely when you already know what you're building.
 
-**Out:** `specs/<feature>/pathfinder/map.md` + `questions/` → `PLAN-DRAFT-<date>.md`
+**Out:** `specs/<feature>/pathfinder/map.md` + `questions/` (or a `pathfinder:map` issue and its
+sub-issues) → `PLAN-DRAFT-<date>.md`. The draft is always a local file — that is what Step 1 reads.
 
 ### 1 · Plan 🤔