shapeup-sdlc 3.7.12 → 3.9.0

package/skills/hill-chart/assets/dashboard.template.html

@@ -916,7 +916,7 @@
     html += '</div>';
 
     // ---- 2. hill chart (headline) ----
-    html += '<div class="section"><h3>Hill Chart</h3><div class="sub">Where each scope sits between figuring it out and getting it done — mechanical, derived only from T0/T1/seesaw evidence, never self-reported. Position is how derisked a scope has ever been; dot color is its current-round health, so a scope can sit downhill and still show red if its latest attempt regressed.</div>';
+    html += '<div class="section"><h3>Hill Chart</h3><div class="sub">Where each scope sits between figuring it out and getting it done — mechanical, derived only from T0/T1 evidence, never self-reported. Position is how derisked a scope has ever been; dot color is its current-round health, so a scope can sit downhill and still show red if its latest attempt regressed.</div>';
     html += '<div class="section-card"><div class="hill-wrap hero">';
     if (pitch.hillAvailable) {
       html += renderHillSVG(pitch.scopeStatus, 'hero');

package/skills/scope-architect/SKILL.md

@@ -77,8 +77,8 @@ the ship report's census table.
                                                                write-whitelist; wrong here =
                                                                a legitimate ESCALATE later
              shared_substrate[]                              — files ≥2 scopes both touch;
-                                                               every write there forces a full
-                                                               seesaw run at the next gate
+                                                               declaring one costs concurrency:
+                                                               they build one at a time
              affordance_manifest                             — from ux-behavior.md state
                                                                tables: every interactive
                                                                element as {test_id, role} +
@@ -93,7 +93,7 @@ the ship report's census table.
                                                                TBD and flag it, never invent
                                                                a fixture for unbuilt behavior
              hill_phase: "UPHILL_UNKNOWN"                    — ALWAYS; phase is derived from
-                                                               T0/T1/seesaw facts later,
+                                                               T0/T1 facts later,
                                                                never authored
 4 LINT     node "${CLAUDE_PLUGIN_ROOT}/kernel/harness.mjs" verify spec --slug <slug>
            → PA1 (directory alignment), PA2 (>~15 files), DISJOINT (undeclared overlap),

package/skills/tech-lead/references/gates.md

@@ -90,7 +90,7 @@ Collect (explicit — never inferred):
         attempts a single scope gets inside one round before its attempt loop trips and
         queues a hammer PROPOSAL for GATE H rather than blocking the round. Only meaningful
         when the spec folder has scope contracts; a spec with none skips the attempt loop
-        entirely and BUILD behaves exactly as in v0.2.6 (task-executor --next, no T0/seesaw).
+        entirely and BUILD behaves exactly as in v0.2.6 (task-executor --next, no T0).
         no_progress_k (v1.5): the STAGNATION term of the same inner breaker. Default 2 — the
         number of consecutive non-`kept` trials after which a scope ends early and queues the
         same GATE H proposal. attempt_budget counts ATTEMPTS and cannot see that the last two
@@ -220,10 +220,17 @@ Do NOT enter MAP SCOPES until Orient is accepted.
 
 ```
 1. PROFILE (you write it at L0 — compile-order stays pipeline-blind): SHARED project-profile.md
-   = {schema_version:1, archetype, entry_point, build_probe?, launch_probe?}. archetype ∈
-   {client-only-game|web-service|mobile|library|data-pipeline}; entry_point is the reachability
-   seam (a game's main.js is NOT a service's src/server.ts). Validate the enum — a typo must fail,
-   not silently disable the check. The two probes feed the round build gate (`harness verify
+   = {schema_version:1, archetype, entry_point, source_extensions?, build_probe?, launch_probe?}.
+   archetype ∈ {client-only-game|web-service|mobile|library|data-pipeline}; entry_point is the
+   reachability seam (a game's main.js is NOT a service's src/server.ts). Validate the enum — a
+   typo must fail, not silently disable the check. entry_point is also the root reachability walks
+   the import graph from, so pick the module the app's screens hang off, not merely the file the
+   platform starts: a framework that registers screens by name (a route map, a manifest, a
+   string-loaded page) leaves its start file importing nothing the feature touches, and the arm
+   then reports that it could not check rather than calling every engine orphaned.
+   source_extensions is optional and only needed when the project's modules end in something the
+   entry point does not (e.g. [".ets"] when the entry is a .ts file); leaving it out costs a
+   skipped arm, never a false red. The two probes feed the round build gate (`harness verify
    build`, every round before EVAL): build_probe asserts the BUILT ARTIFACT covers what the run
    wrote (a green exit code is not proof the feature compiled when the toolchain compiles only what
    an entry point reaches); launch_probe installs, starts and asserts the first screen. A `mobile`
@@ -241,7 +248,14 @@ Do NOT enter MAP SCOPES until Orient is accepted.
    requirements.md registry (atomic REQ clauses, frozen ids).
 4. trace-lint — node "${CLAUDE_PLUGIN_ROOT}/kernel/harness.mjs" verify trace --slug <slug>. ADVISORY at L1b:
    covers-closure (every covered REQ named by ≥1 AC's covers:) + reachability (every UC engine
-   reaches entry_point). Promote to --gate only once covers: is populated.
+   reaches entry_point). Promote to --gate only once covers: is populated. Reachability reports
+   checked:false with a reason rather than a verdict in two cases, both warns: an import it could
+   not follow (the graph is incomplete) and no engine reachable at all (nothing controls the walk,
+   so an orphan and a wrong root look identical). Read either as "re-declare the profile", never
+   as a clean arm. When it does run it also reports, per scope, how many of that scope's own source
+   files the app reaches, and warns (SCOPE-UNREACHABLE) on a scope it reaches none of — a scope's
+   build fixture can be green while its code never compiles, on any toolchain that compiles only
+   what the entry point reaches. Warn only: the wiring may be a later scope's job by design.
 ```
 
 ---

package/skills/tech-lead/references/protocol.md

@@ -205,7 +205,7 @@ ingest-result <result>             → board/ledger writes
                                       fails, and the run ABORTS naming the phase. Resolve it
                                       yourself and record the answer in round-ledger.md, which
                                       the NEXT attempt's fresh context reads back.
-harness verify t0                      → fixtures + DB probe + (on green) seesaw, then scores the
+harness verify t0                      → fixtures + DB probe, then scores the
                                       attempt against the baseline trial and snapshots or
                                       restores the tree. Branch on `status` from its stdout
                                       JSON — the tree action has ALREADY happened:
@@ -217,9 +217,8 @@ harness verify t0                      → fixtures + DB probe + (on green) sees
               KEEPS, because a spec-conformance fix cannot raise a score that is already at
               full marks, and reverting it would discard exactly the work a fix round exists
               to do. Tree already restored from the last kept
-              snapshot. Subsumes the retired stash-and-retry branch: a FINISHED scope's broken
-              fixture raises score.regressions and reverts through this same rule, which
-              is why seesaw runs before anything is declared green.
+              snapshot. Subsumes the retired stash-and-retry branch: an attempt that scores
+              worse than the incumbent reverts through this same rule.
               rather than the code. Tree kept, baseline reset. Not a verdict, not a failure.
   crash     a fixture command failed to spawn or timed out; tree restored. Fix the fixture,
               not the code.
@@ -446,9 +445,8 @@ Do: verify the phase's artifact by hand before trusting either diagnosis. If it
 ```
 Invoke via Bash directly — NOT an Agent, this is deterministic tooling, not a worker:
   node "${CLAUDE_PLUGIN_ROOT}/kernel/harness.mjs" verify t0 shapeup/<slug>/scopes/<scope-id>.md
-        --round <N> --attempt <M> --seesaw-registry .shapeup/<slug>/seesaw/registry.json
-Effect: runs the scope's e2e fixtures + DB probe, then (on green) the seesaw regression check
-        over every FINISHED scope's fixtures. Writes the verdict artifact spec-evaluator's
+        --round <N> --attempt <M>
+Effect: runs the scope's e2e fixtures and DB probe. Writes the verdict artifact spec-evaluator's
         T0-citation rule will require a citation to, appends one row to t0/trials.jsonl, and — this
         is the ratchet — scores the attempt against the last kept trial and snapshots or
         restores the working tree ITSELF. Zero LLM tokens — deterministic tooling, not a
@@ -592,7 +590,7 @@ guarantee lives in the script and, where noted, in a hook.
 | Three-level circuit breaker: attempt_budget (inner, per scope) nests inside round_budget (outer), with an opt-in wall_clock_budget_s deadline | An exhausted scope queues a GATE H hammer proposal, it never blocks the round; only round_budget hitting 0 stops the whole run; the deadline breaker (checked every round boundary in `shapeup-run.js`) routes to GATE H so a run out of clock still ships what is green instead of being killed from outside |
 | The tech lead never hand-edits a scope contract | scope-architect is its sole writer (single-writer-per-file) |
 | Substrate-disjointness + PA1/PA2 lints are re-asserted at GATE L1b (harness verify spec) even when scope-architect already checked them | A human may have hand-approved past a 🔴 at the architect's checkpoint; `shapeup-run.js` runs spec-lint itself, in code, before resolving L1b |
-| Hill phase is read from mechanical facts (T0/T1/seesaw), never declared by a worker | Closes the self-reported-confidence risk outright — facts move dots, not authors |
+| Hill phase is read from mechanical facts (T0/T1), never declared by a worker | Closes the self-reported-confidence risk outright — facts move dots, not authors |
 | GATE H is delegated to scope-hammer, never adjudicated inline by the tech lead | Keeps the orchestrator thin; census/baseline-comparison/cut-list logic has one owner |
 
 ---