shapeup-sdlc 1.6.3 → 3.0.0

package/skills/ba-pitch-analyzer/assets/templates/api-feasibility.tmpl.md

@@ -14,9 +14,12 @@ dependent implementation tasks can proceed.*
 
 ## Detected Third-Party Dependencies
 
-| # | Service | Capability Claimed | Status | SPIKE Task |
-|---|---------|-------------------|--------|------------|
-| API-01 | [ServiceName] | [What pitch claims this API can do] | ❓ UNVERIFIED | [[TASK-001-spike-[api]]] |
+| # | Service | Capability Claimed | Status | Spike |
+|---|---------|-------------------|--------|-------|
+| API-01 | [ServiceName] | [What pitch claims this API can do] | ❓ UNVERIFIED | ⏳ open |
+
+<!-- The Spike column records STATUS (⏳ open / ✅ done / — none), never a task id.
+     This document is committed; the board is not, and its ids renumber per machine. -->
 
 ---
 
@@ -49,10 +52,12 @@ Specifically: [quote or paraphrase relevant pitch sentence].
 | Partially supported | [Describe workaround] | +[N]h |
 | Not supported | [Describe alternative or de-scope] | [TBD with PO] |
 
-**Dependent Tasks:**
-<!-- List all tasks blocked until this investigation is complete -->
-- [[TASK-NNN]] — [reason blocked]
-- [[TASK-NNN]] — [reason blocked]
+**Blocked Use Cases:**
+<!-- What cannot be built until this investigation resolves. Name the committed UC, never
+     a task id: this doc is committed and task ids are machine-local. The tasks are found
+     by inverting use_case_refs over the LOCAL board. -->
+- [[usecases/UC-Name]] — [reason blocked]
+- [[usecases/UC-Name]] — [reason blocked]
 
 **Decision Gate:**
 - All questions answered + capability confirmed → update `contracts/[repo].contract.md`, remove ⏳ TBD fields, notify SPIKE complete

package/skills/ba-pitch-analyzer/assets/templates/contracts/third-party-api.contract.tmpl.md

@@ -5,7 +5,9 @@ feature: "[feature-slug]"
 repository: "[RepoName]"
 service: "[ServiceName]"
 feasibility_ref: "API-[NN]"
-spike_task: "[[TASK-NNN-spike-[api]]]"
+spike_status: open       # open | done — STATUS, never a task id: this contract is
+                         # committed and board ids renumber per machine. The spike is
+                         # reached through feasibility_ref above.
 status: speculative      # → confirmed after SPIKE done
 skill_version: "2.3"
 ---
@@ -14,13 +16,14 @@ skill_version: "2.3"
 
 ## Source Type: `third-party-api`
 ## Service: [ServiceName] ([REST API / SDK])
-## Feasibility: ⏳ UNVERIFIED → see [[api-feasibility#API-NN]] + [[TASK-NNN-spike-[api]]]
+## Feasibility: ⏳ UNVERIFIED → see [[api-feasibility#API-NN]]
 
 ---
 
 > ⚠️ **SPECULATIVE CONTRACT**
 > Fields marked `⏳ TBD` are derived from pitch assumptions and community references.
-> All `⏳ TBD` entries MUST be confirmed and replaced during [[TASK-NNN-spike-[api]]].
+> All `⏳ TBD` entries MUST be confirmed and replaced by the spike tracked at
+> [[api-feasibility#API-NN]].
 > Implementation tasks depending on this repository are **blocked** until no `⏳ TBD` remains.
 
 ---

package/skills/ba-pitch-analyzer/assets/templates/cross-context/migration-plan.tmpl.md

@@ -13,7 +13,8 @@ status: draft
 # Migration Plan: FEATURE TITLE
 
 > Generated only when feature modifies existing production schema.
-> Each migration task maps to a TASK-M0N in tasks/_index.md.
+> Each migration step anchors to a committed use case; the tasks that carry it are found
+> by inverting `use_case_refs` over the LOCAL board, never linked from here.
 
 ---
 
@@ -31,7 +32,7 @@ status: draft
 
 ## Migration Tasks
 
-### TASK-M01 — [description, e.g. Add nullable columns]
+### STEP-1 — [description, e.g. Add nullable columns]
 
 ```sql
 -- UP
@@ -46,7 +47,7 @@ Safe to run: during deploy / after deploy / off-hours only
 
 ---
 
-### TASK-M02 — [description, e.g. Backfill existing rows]
+### STEP-2 — [description, e.g. Backfill existing rows]
 
 ```sql
 -- UP (run in batches of 1000 to avoid lock escalation)
@@ -66,7 +67,7 @@ Estimated rows: ~N | Estimated time: ~Ns | Lock: none
 
 ---
 
-### TASK-M03 — [description, e.g. Enforce NOT NULL constraint]
+### STEP-3 — [description, e.g. Enforce NOT NULL constraint]
 
 ```sql
 -- UP — only run after M02 verified

package/skills/ba-pitch-analyzer/assets/templates/cross-context/team-handoff.tmpl.md

@@ -21,19 +21,29 @@ status: draft
 
 | From Team | To Team | Artifact | Ready When | Blocker Risk |
 |-----------|---------|----------|-----------|-------------|
-| [Team A] (API) | [Team B] (Mobile) | [[contracts/[repo].contract.md]] | TASK-00N done | 🔴 blocks Mobile TASK-00N |
-| [Team B] (API) | [Team A] (API) | `EventName` schema | TASK-00N done | 🟡 blocks integration test |
-| [Team B] (Mobile) | QA | E2E test cases | TASK-00N done | 🟡 blocks QA sprint entry |
+| [Team A] (API) | [Team B] (Mobile) | [[contracts/[repo].contract.md]] | [[usecases/UC-Name]] green | 🔴 blocks Mobile [[usecases/UC-Name]] |
+| [Team B] (API) | [Team A] (API) | `EventName` schema | [[usecases/UC-Name]] green | 🟡 blocks integration test |
+| [Team B] (Mobile) | QA | E2E test cases | [[usecases/UC-Name]] green | 🟡 blocks QA sprint entry |
+
+<!-- Readiness is stated against a committed UC (or a scope_id), never a task id: this
+     register is committed and shared across teams, and board ids are per-machine. -->
 
 ---
 
 ## Blocking Dependencies
 
+<!--
+  Key every row on a USE CASE or a scope_id, never a task id. This document is committed and
+  crosses a team boundary; board ids live in the gitignored tier and each team's board numbers
+  its own, so one board id names a different piece of work on every machine that reads this.
+  spec-lint reds a board id anywhere in the committed tree (TIER-DIRECTION).
+-->
+
 ```
-[Team B] CANNOT start TASK-00N ([description])
-  until [Team A] completes TASK-00N ([description])
+[Team B] CANNOT start [UC-x] ([description])
+  until [Team A] completes [UC-y] ([description])
   Mitigation: use contract stub from [[contracts/[repo].contract.md]]
-  Stub ready: TASK-00N (unblocked — no dependency)
+  Ready now: [UC-z] (unblocked — no dependency)
 
 [Team C] CANNOT start integration tests
   until [Team A] EventName schema is stable
@@ -46,12 +56,12 @@ status: draft
 
 ```
 Wave 1 — No cross-team dependencies (start immediately):
-  [Team A]: TASK-001, TASK-002, TASK-003
-  [Team B]: TASK-004, TASK-005 (using contract stub)
+  [Team A]: [UC-a], [UC-b], [UC-c]
+  [Team B]: [UC-d], [UC-e] (using contract stub)
 
-Wave 2 — After Team A TASK-003 done:
-  [Team B]: TASK-006 (replace stub with real contract)
-  [Team C]: TASK-007 (integration tests — real contract available)
+Wave 2 — After Team A [UC-c] done:
+  [Team B]: [UC-f] (replace stub with real contract)
+  [Team C]: integration tests (real contract available)
 
 Wave 3 — After Wave 2 complete:
   QA: E2E test suite
@@ -64,7 +74,7 @@ Wave 3 — After Wave 2 complete:
 | Trigger | Owner | Notify | Channel |
 |---------|-------|--------|---------|
 | Contract changes after stub distributed | [Team A] | [Team B], QA | [channel] |
-| TASK-00N delayed > 1 day | [Team A] | [Team B] | [channel] |
+| A wave-1 use case delayed > 1 day | [Team A] | [Team B] | [channel] |
 | Schema breaking change detected | Any | All teams | [channel] |
 
 ---
@@ -72,7 +82,7 @@ Wave 3 — After Wave 2 complete:
 ## Definition of Done (Cross-Context)
 
 Feature is complete when ALL of the following are true:
-- [ ] All TASK-MNN migrations run and verified in staging
+- [ ] Every migration STEP run and verified in staging
 - [ ] All contracts have no remaining ⏳ TBD fields
 - [ ] Event choreography happy path verified end-to-end
 - [ ] All dead-letter scenarios have runbooks

package/skills/ba-pitch-analyzer/assets/templates/scope-summary.tmpl.md

@@ -35,14 +35,15 @@ audit_score: 0
 
 The longest sequential chain — minimum time to complete if parallelized optimally.
 
-```
-TASK-NNN → TASK-NNN → TASK-NNN → TASK-NNN
-  Nh          Nh          Nh          Nh
-```
-
-**Critical path estimate:** Nh total
+**Critical path estimate:** Nh total, N steps
 *(All other work can happen in parallel alongside this chain)*
 
+<!-- Record the DERIVED numbers only — total hours and step count, both from
+     `harness reduce board`. The chain's task ids belong to the LOCAL board
+     (.shapeup/<slug>/tasks/), which is gitignored and renumbers per machine; this
+     document is committed, so an id written here dangles on every other clone
+     (spec-lint TIER-DIRECTION). Read the id-level chain off the board itself. -->
+
 ---
 
 ## Package Distribution
@@ -58,12 +59,16 @@ TASK-NNN → TASK-NNN → TASK-NNN → TASK-NNN
 
 ## Parallel Opportunities
 
-Tasks with no interdependency that can run simultaneously:
+How much of the board can run simultaneously — **counts and use cases, never task ids.** This file
+is COMMITTED; the board is not, and its ids renumber per machine (spec-lint TIER-DIRECTION).
+
+| Group | Use cases | Tasks | Can start after |
+|-------|-----------|-------|-----------------|
+| Group A | UC-x, UC-y | N | nothing — no dependency |
+| Group B | UC-z | N | Group A |
 
-| Group | Tasks | Can start after |
-|-------|-------|----------------|
-| Group A | TASK-NNN, TASK-NNN | TASK-NNN completes |
-| Group B | TASK-NNN | TASK-NNN completes |
+The per-scope release order is `scope-board.md`'s, keyed on `scope_id`. Cite it rather than
+restating it here.
 
 ---
 
@@ -94,7 +99,7 @@ Carried from [[_index#Rabbit-Holes]]:
 
 ## Execution Recommendation
 
-<!-- Filled from spec-lint.mjs output -->
+<!-- Filled from harness verify spec output -->
 
 **Audit Score: N/100**
 

package/skills/ba-pitch-analyzer/assets/templates/synthesis.tmpl.md

@@ -166,50 +166,29 @@ Derived from: `_index.md` rabbit holes + `api-feasibility.md` SPIKE blocks + `in
 
 | Cut | At | Reason | Traded for (if any) |
 |-----|-----|-------|---------------------|
-| ~~[cut capability]~~ | GATE-N | appetite overflow — saved for a later bet | TASK-NNN |
+| ~~[cut capability]~~ | GATE-N | appetite overflow — saved for a later bet | [UC or scope it was traded for] |
 
 *A Cut is a healthy shaping signal, not debt. Revisit it at the betting table next cycle.*
 
 ---
 
-## S-03 — Dependency Graph
+## S-03 — Dependency Shape
 
-> Open this section when **Dependency** is 🟡 or 🔴, or when planning parallel work.
+> Open this section when **Dependency** is 🟡 or 🔴.
 
-Derived from: `depends_on` and `unlocks` in every task frontmatter + `estimated_hours`.
+Derived from: `depends_on` in every task frontmatter. **Counts and shape only — no task ids.**
+This document is COMMITTED and the board is not: ids live in the gitignored tier and renumber on
+every regeneration, so an id written here resolves on the machine that wrote it and nowhere else.
+spec-lint reds a `TASK-` id anywhere in the committed tree (TIER-DIRECTION).
 
-### Critical Path
+| Metric | Value |
+|---|---|
+| Critical path | N tasks · NN hours · NN% of total estimated hours |
+| Widest parallel wave | N tasks |
+| Tasks with no dependency | N |
+| Single points of failure (block > 2 downstream) | N |
 
-```
-Critical path: N tasks · NN hours · NN% of total estimated hours
-
-TASK-001 [SPIKE]  spike-[api]-feasibility         2h
-  └─ blocks ──► TASK-004, TASK-005, TASK-006
-TASK-002 [TASK]   shared-schema                   3h  ← parallel (no dependency on 001)
-TASK-003 [TASK]   contract-stub                   2h  ← parallel
-TASK-004 [FEAT]   implement-[repo]               ⏳ blocked by TASK-001   4h
-  └─ blocks ──► TASK-005
-TASK-005 [FEAT]   [use-case]-service             ⏳ blocked by TASK-004   6h
-  └─ blocks ──► TASK-006, TASK-007
-TASK-006 [FEAT]   [feature]-ui                   ⏳ blocked by TASK-005   8h
-TASK-007 [FEAT]   [feature]-ui-edge-cases        ⏳ blocked by TASK-005   4h
-```
-
-### Parallel Opportunities
-
-Tasks at the same dependency depth with no interdependency — can be executed in parallel:
-
-| Wave | Tasks | Total Hours | Can Parallelize |
-|------|-------|-------------|-----------------|
-| Wave 1 (no deps) | TASK-001, TASK-002, TASK-003 | Nh | ✅ yes — 3 agents |
-| Wave 2 (after 001) | TASK-004 | Nh | — single task |
-| Wave 3 (after 004) | TASK-005 | Nh | — single task |
-| Wave 4 (after 005) | TASK-006, TASK-007 | Nh | ✅ yes — 2 agents |
-
-### Single Points of Failure
-
-Tasks whose delay cascades to > 2 downstream tasks:
-
-| Task | Blocks | Cascaded Hours at Risk |
-|------|--------|----------------------|
-| TASK-NNN | TASK-NNN, TASK-NNN, TASK-NNN | Nh |
+**The per-scope build order — which scopes go in which wave, and what each waits on — lives in
+`scope-board.md`, not here.** `scope-architect` writes that board and is the only worker that knows
+the scope ids; it runs after this document, so the ordering cannot be expressed here in a key that
+survives a clone. Cite the board, never restate it.

package/skills/ba-pitch-analyzer/assets/templates/task.tmpl.md

@@ -9,6 +9,9 @@ priority: N
 depends_on: []
 unlocks: []
 use_case_refs: []
+scope_id: ""                     # optional — set ONLY when several scopes share this task's use
+                                 # case and spec-lint SCOPE-PARTITION says the UC anchor cannot
+                                 # decide who builds it. Names a committed scope_id (LOCAL→SHARED).
 entities: []
 repositories: []
 linked_docs: []

package/skills/ba-pitch-analyzer/references/contract-patterns.md

@@ -117,11 +117,15 @@ Every contracts folder must have an `_index.md` registry:
 ```markdown
 # Contract Registry — [feature-slug]
 
-| Repository | Source Type | Service / Engine | Status | SPIKE Task |
-|-----------|------------|-----------------|--------|------------|
-| [[FramerPageRepository]] | third-party-api | Framer REST API | ⚠️ speculative | [[TASK-001]] |
+| Repository | Source Type | Service / Engine | Status | Spike |
+|-----------|------------|-----------------|--------|-------|
+| [[FramerPageRepository]] | third-party-api | Framer REST API | ⚠️ speculative | ⏳ open |
 | [[PageCacheRepository]] | offline-storage | SQLite/Drizzle | ✅ confirmed | — |
 | [[UserSessionRepository]] | be-service | apps/api /auth | ✅ confirmed | — |
+
+The Spike column carries a STATUS, not a task id. The registry is committed; the board is
+not, and its ids renumber on every regeneration — so a task id recorded here resolves on
+the machine that wrote it and nowhere else (spec-lint TIER-DIRECTION).
 ```
 
 This registry is the entry point for the spec-lint structure checks.
@@ -147,6 +151,6 @@ Every implementation task that uses a repository MUST:
 
 3. If contract is still `speculative` at task-generation time:
    ```markdown
-   > ⏳ BLOCKED by [[TASK-001-spike-framer-feasibility]]
+   > ⏳ BLOCKED — spike open, see [[api-feasibility#API-01]]
    > Unblock condition: [[contracts/framer-page.contract.md]] has no remaining ⏳ TBD fields
    ```

package/skills/ba-pitch-analyzer/references/doc-schemas.md

@@ -152,7 +152,7 @@ status: draft | ready
 > tasks carry `use_case_refs` (LOCAL, per-machine board); reverse lookup is always computed
 > live (synthesis S-01, audit coverage) — never stored on the committed UC. Rule: **never
 > declare a bidirectional field across the committed/local boundary** — task IDs renumber
-> per machine (generate-board bootstrap), so a stored back-link is wrong on every machine
+> per machine (the board is regenerated locally), so a stored back-link is wrong on every machine
 > but one. Tolerate (ignore) the field on pre-v3.3 specs; do not emit or update it.
 
 Required sections: Summary (1 sentence), Preconditions, Input (TS interface), Steps
@@ -217,6 +217,8 @@ depends_on: []                   # other TASK IDs: [TASK-001, TASK-002] — the
 unlocks: []                      # DERIVED — inverse of the board's depends_on graph, recomputed
                                  # on every board write; never hand-authored (v3.3)
 use_case_refs: []                # UC IDs this task implements: [UC-CreateOrder]
+scope_id: ""                     # optional disambiguator — the scope that builds this task.
+                                 # Needed only when >1 scope shares a use case (SCOPE-PARTITION).
 entities: []
 repositories: []
 linked_docs: []                  # [[usecase]], [[domain-model#section]]

package/skills/ba-pitch-analyzer/references/task-generation.md

@@ -361,12 +361,12 @@ Slug rules:
 ## Link-Field Integrity (v3.3)
 
 **`depends_on` is the single authoritative edge; `unlocks` is derived, never hand-authored.**
-On EVERY board write — analyze, generate-board, reconcile — recompute (via
-`board-derive.mjs --write`, never by hand) the `unlocks` field of every task on the board as the
+On EVERY board write — analyze, reconcile — recompute (via
+`harness reduce board --write`, never by hand) the `unlocks` field of every task on the board as the
 exact inverse of the full board's `depends_on` graph, then write it. Adding one task that
 declares `depends_on: [TASK-007]` therefore rewrites `TASK-007.unlocks` in the same pass.
 "Write both sides when you remember" allows drift; a derived field cannot drift
-(island-escape shipped 10 asymmetric edges under the old rule). Audit L3-06 fails the board
+(the old rule shipped boards carrying ten asymmetric edges). Audit L3-06 fails the board
 on any asymmetric edge.
 
 The same discipline has a boundary: it applies only when both sides live in the SAME root
@@ -563,7 +563,7 @@ tasks). Scope (Basecamp sense) maps onto a UC; an invariant lives *inside* the U
    task-executor / the tech lead; this mode only surfaces the disagreement.
 9. Regenerate ONLY the derived files: tasks/_index.md, scope-summary.md, synthesis.md
    (+ the unlocks frontmatter recompute from step 7).
-10. Run board-derive.mjs (Appetite Guard arithmetic, below); report overflow as a discovery.
+10. Run harness reduce board (Appetite Guard arithmetic, below); report overflow as a discovery.
 ```
 
 **Appetite Guard (forcing function, not a report):**
@@ -584,12 +584,12 @@ This is scope hammering at the gate boundary — the overflow is surfaced, never
 **Naming note:** the discovery ledger's "scope" sections (above) predate the formal Scope
 Contract artifact below and name the same thing — a `discovery/ledger.md` scope heading MUST
 match an existing `scope_id` from a `scopes/<scope-id>.md` contract, or (a Keep item
-introducing new flow) become the seed for a new one via a scope-architect remap order. One concept, two touch points.
+introducing new flow) become the seed for a new one via a scope-architect `map-scopes` order. One concept, two touch points.
 
 **Import/flow slicing (PA1 countermeasure).** Build a lightweight import graph over the task
 board's touched files: for each file a task writes, note what it imports and what imports it
 (grep for `import .* from ['"](\.\.?/[^'"]+)`-class patterns is sufficient — a full AST parser
-is an optimization, not a prerequisite, per design spec R6). Two files are in the same flow if
+is an optimization, not a prerequisite). Two files are in the same flow if
 they sit on one call chain: a UI component → the API route it calls → the use case that route
 invokes → the repository that use case depends on. Group tasks by flow, not by which top-level
 directory their file lives in. A scope whose `allowed_file_substrate` is entirely `apps/web/**`
@@ -614,8 +614,8 @@ or entirely `apps/api/**` with no cross-layer flow is the PA1 failure mode — r
 }
 ```
 `hill_phase` is always written `UPHILL_UNKNOWN` at generation time — it is derived later from
-mechanical T0/T1/seesaw facts, never declared by `ba` (design spec DD-10). `superseded_by` stays
-`null` until a scope-architect split-scope order retires this contract in favor of its replacements.
+mechanical T0/T1/seesaw facts, never declared by `ba`. `superseded_by` stays
+`null` until a scope-architect `map-scopes` order retires this contract in favor of its replacements.
 
 **PA2 size lint:** a scope whose `allowed_file_substrate` glob set resolves to more than ~15
 files gets a ⚠️ from spec-lint PA2 (hard-cap configurable via pitch frontmatter `scope_size_cap`, default

package/skills/ba-pitch-analyzer/references/test-surface.md

@@ -7,7 +7,7 @@ source row below, it does not belong here (it belongs to exploratory QA, post-bu
 **Why it exists.** `spec-conformance` grades the AC that were written; it cannot expand
 them. The Test Surface is the systematic expansion — boundary values, negative cases,
 error-code coverage — done once at spec time so the evaluator (`test-surface-conformance`
-dimension) can probe it. Division of labor settled at the QA meeting (2026-06-11):
+dimension) can probe it. Division of labor, a settled design decision:
 derivable tests = BA + Evaluator (this file); exploratory edges = `/qa-edge-hunter`,
 post-PASS, on the running app.
 

package/skills/coach/SKILL.md

@@ -41,8 +41,8 @@ they are the **complete** set of categories the gate may offer:
 
 | Category | File | The worker reads it at | Good for |
 |----------|------|------------------------|----------|
-| `task-executor`     | `shapeup/knowledge-base/task-executor.md`     | Phase 1 (Context Load) | implementation discipline, code style, surgical-change habits, recurring over/under-engineering |
-| `ba-pitch-analyzer` | `shapeup/knowledge-base/ba-pitch-analyzer.md` | Phase 1 (Ingest & Scan) | scoping, task decomposition, DDD/spec habits, missed test-surface patterns |
+| `task-executor`     | `shapeup/knowledge-base/task-executor.md`     | PLAN (context load) | implementation discipline, code style, surgical-change habits, recurring over/under-engineering |
+| `ba-pitch-analyzer` | `shapeup/knowledge-base/ba-pitch-analyzer.md` | Phase 1 (INGEST) | scoping, task decomposition, DDD/spec habits, missed test-surface patterns |
 | `qa-edge-hunter`    | `shapeup/knowledge-base/qa-edge-hunter.md`    | Phase Q1 (Charter Map) | recurring edge classes, lenses that keep finding bugs, areas worth probing |
 
 **Not coachable.** `spec-evaluator` is deliberately excluded — the harness has a **single-judge**
@@ -54,7 +54,7 @@ say so plainly — do **not** force-fit it into a coachable category.
 **Harness defect ≠ worker steering.** When the feedback's root cause is the *mechanism itself* —
 a hook that fail-opens, a gate that reads the wrong file, two skill contracts that contradict
 each other — no amount of steering a worker fixes it, and filing it as a KB rule misdiagnoses a
-defect as a habit (island-escape's KB-BA-002 filed an orchestration/hook defect as BA guidance,
+defect as a habit (a real case: an orchestration/hook defect filed as BA guidance,
 on a premise the skill contracts contradict). That is what the `harness-defect` category below is
 for: the coach records it in the committed defect register as a drafted **raw idea** for the
 Betting Table — the debt-free path ("remaining findings + new feedback → new raw idea") — and it

package/skills/orient/SKILL.md

@@ -42,7 +42,8 @@ from `tech-lead`; it never reads or writes a shared run-state file.
 ## Input contract (pure worker)
 
 Orchestrated, you are invoked as `--order <path>` (a WorkOrder): `payload.pitch` (the
-kicked-off pitch path), `payload.stack` (sweep hint), and `substrate.allowed` naming your one
+kicked-off pitch path), `payload.stack` (sweep hint), `payload.spec_folder` (the SHARED spec
+deliverable dir) and `payload.feature` (the run slug), plus `substrate.allowed` naming your one
 write surface — the orient output dir. Anything absent = unknown: confirm at GATE O-A
 (standalone) or report it in the result's `deviations`, never guess. Standalone, the
 `--pitch/--spec/--stack` flags below carry the same fields; the output dir derives from the

package/skills/qa-edge-hunter/SKILL.md

@@ -18,7 +18,7 @@ tech-lead: ... GATE L2 → EVAL → GATE L3 PASS ──► QA EDGE HUNT (you)
             GATE L3 FAIL → fix round (never reaches you — conformance first, edges after)
 ```
 
-**Division of labor (settled at the QA meeting, 2026-06-11):**
+**Division of labor (a settled design decision, not a convention):**
 
 | Tier | Owner | When |
 |---|---|---|
@@ -33,14 +33,17 @@ tech-lead: ... GATE L2 → EVAL → GATE L3 PASS ──► QA EDGE HUNT (you)
 |------|----------|
 | Read EVAL-*.md to map covered territory — then hunt OUTSIDE it | Re-probe anything the evaluator already graded |
 | Charter edges via six fixed lenses, minus covered territory | Author or extend `## Test Surface` (that is the planner's retrofit-surface operation) |
-| Execute charters on the **running app** (session-based exploratory) | Read-only speculate from code ("this looks racy") — every finding needs a live repro |
+| Execute charters against the **running deliverable** (session-based exploratory) | Read-only speculate from code ("this looks racy") — every finding needs a live repro |
 | Return each finding in the WorkResult's `discoveries[]`, **always `~`** | Promote `~` → must-have (PO/TL at SHIP S.0; severity-hint is advice, not a decision) |
 | Emit `qa/hunt-report.md` — charters run/cut, findings by lens | Render a verdict, score, or PASS/FAIL of any kind |
-| `--recheck`: re-probe ONLY items promoted+fixed after triage | Run a second full hunt in the same cycle; fix code; touch task files; keep run-state |
 
 Pure worker (harness rule: stateless workers, one stateful orchestrator). Its WorkOrder
 carries `payload.feature`, `payload.spec_folder`, `payload.eval_report`, `payload.app_url`,
-`payload.kb_rules_path` (+ read-only ledger path for covered-territory context); its write surface is
+`payload.kb_rules_path`, and `payload.ledger` (the discovery ledger, READ-ONLY — covered-territory
+context so a hunt does not re-report what is already known). **`app_url` is null when the
+deliverable is not served over HTTP** — a CLI, a library, a batch job. That is a normal order, not a
+malformed one: drive the built entry point instead, exactly as the Test Surface's process rows do.
+Do not refuse the hunt, and do not invent a URL. Its write surface is
 `.shapeup/<feature>/qa/**` only. The Hunter never touches the discovery ledger itself —
 ingest appends its `discoveries[]` under a `## Discovered` section, preserving single-writer
 mechanically.
@@ -50,7 +53,8 @@ mechanically.
 ## Workflow
 
 ```
-⏸ GATE Q0 │ Preflight ────► hard: app running? EVAL verdict PASS? ledger exists?
+⏸ GATE Q0 │ Preflight ────► hard: deliverable reachable (one real request at `app_url`, or one
+          │                 real invocation of the entry point when it is null)? EVAL PASS? ledger?
           │                 soft: Test Surface present? absent → DEGRADED MODE offer
 Phase Q1  │ Charter Map ──► 6 lenses × UC tree − covered territory (EVAL-probed rows/AC)
 ⏸ GATE Q1 │ Charter Review► PO/TL hammer the charter list (QA's own appetite is fixed too)
@@ -272,7 +276,6 @@ an order, the WorkResult envelope `.shapeup/<feature>/results/<order-suffix>.jso
 
 ```markdown
 # Hunt Report — [feature] (round [r], [date])
-mode: [full | degraded | recheck]
 charters: [run]/[approved] · session units spent: [n]
 out of bounds (excluded): […]
 hammered out at GATE Q1 (not hunted): […]
@@ -282,7 +285,8 @@ hammered out at GATE Q1 (not hunted): […]
 |---|---|---|---|
 | ① Boundary | C-01, C-05 | 2 | 0 |
 | … | | | |
-→ details live in .shapeup/<feature>/discovery/ledger.md ## QA Edge Findings (round [r])
+→ details live in .shapeup/<feature>/discovery/ledger.md under the `## Discovered` section
+  ingest appends for this hunt's order
 
 ## Shaping-quality signal (advisory, for the PO — next cycle's input)
 - lens ⑤ findings ≈ No-gos written loosely (breach routes left open)
@@ -298,48 +302,18 @@ No verdict line exists in this file by design. The Hunter's last words:
 
 ---
 
-## `--recheck` mode (after triage promoted + fixed items)
-
-```
-Input: the promoted finding ids (from tech-lead) + the fix round's PASS EVAL report.
-Q0   : hard checks only (app up, new EVAL PASS); no soft check, no charter map.
-Hunt : re-run EXACTLY the recorded repro of each promoted finding — nothing else.
-        fixed   → discoveries[] entry `{ "marker": "~", "line": "[QA-NNN] ✦ fixed r[N], verified" }`
-                  (ingest annotates the ledger — annotate, never delete; the ledger is history)
-        not fixed → `{ "marker": "~", "line": "[QA-NNN] ✦ NOT fixed r[N]", "repro": "<fresh evidence>" }`
-                  back to triage.
-Report: append a `## Recheck (round [r])` section to .shapeup/<feature>/qa/hunt-report.md.
-NEVER a second full hunt in the same cycle — new edges found while rechecking are
-recorded `~` like any finding and wait for triage; they don't restart the loop.
-```
-
----
-
 ## Invocation
 
 ```bash
-# Orchestrated (how tech-lead calls it after first PASS) — the canonical form:
-#   compile-order --operation hunt --slug checkout-vnpay --worker qa-edge-hunter \
-#     --payload '{"eval_report": "…/EVAL-FEATURE-checkout-vnpay.md", "app_url": "http://localhost:3000"}'
-/qa-edge-hunter --order .shapeup/checkout-vnpay/orders/hunt.json
-
-# Standalone flags (the preamble shim compiles the same envelope)
-/qa-edge-hunter --feature checkout-vnpay --spec shapeup/checkout-vnpay/spec/ \
-    --eval .shapeup/checkout-vnpay/evaluation/EVAL-FEATURE-checkout-vnpay.md \
-    --ledger .shapeup/checkout-vnpay/discovery/ledger.md --app http://localhost:3000
-
-# Standalone (same arguments, human-invoked)
 /qa-edge-hunter --feature checkout-vnpay --spec shapeup/checkout-vnpay/spec/ --app http://localhost:3000
 # (--eval/--ledger default to the conventional paths under the LOCAL root .shapeup/<feature>/)
 
-# Recheck after triage promoted + fixed findings
-/qa-edge-hunter --recheck QA-001,QA-004 --feature checkout-vnpay --spec ... --app ...
-
-# Escape hatches
+# Escape hatch
 --auto            # skip GATE Q1 pause (charter list logged, not reviewed) — Q0 hard
                   # checks and the out-of-bounds question are NEVER skipped
---lenses-note     # there is deliberately NO --lenses flag: the 6 lenses are fixed;
-                  # narrow by cutting charters at GATE Q1 (or --auto + report)
+
+# There is deliberately NO --lenses flag: the 6 lenses are fixed; narrow by cutting
+# charters at GATE Q1 (or --auto + report).
 ```
 
 ### Progress Markers