@thebassclef/lite 1.9.9 → 1.9.11

package/dist/lite/.claude/rules/last-block-marker.md

@@ -0,0 +1,79 @@
+---
+tier: lite
+title: Last-block marker
+anchor_luminaries:
+  - john-ousterhout
+  - tony-hoare
+  - michael-feathers
+  - don-norman
+  - alan-cooper
+  - steve-krug
+---
+
+# Last-block marker
+
+Every call to `blocked_banner()` or `guardrail_banner()` in `.claude/hooks/session-reflection.sh` persists a marker at `state/markers/last-block/<hook>.marker`. The marker carries the hook name, severity, timestamp, and verbatim banner text. The `/last-block` skill reads markers back.
+
+This rule is the methodology layer. The mechanical layer is `lib/last-block.sh` sourced by `session-reflection.sh`. Both required together to close Kunal Finding #10.
+
+## When this rule fires
+
+Every call to `blocked_banner()` or `guardrail_banner()` in `.claude/hooks/session-reflection.sh`. The banner helpers already call `record_last_block` from the sourced lib. Hook authors who call these helpers get the marker for free.
+
+## Marker format
+
+Plaintext layout per `lib/last-block.sh`:
+
+```
+hook: <hook-name>
+severity: blocking|advisory|info|guardrail
+fired_at: <ISO-8601 UTC>
+session: <CLAUDE_SESSION_ID or "unknown">
+---
+<verbatim banner text, truncated at 8KB with a truncation marker>
+```
+
+Grep-friendly. One marker file per hook. Overwrites on each fire. No rotation in V1.
+
+## What the rule requires
+
+For hooks that fire BLOCK via `blocked_banner()` or `guardrail_banner()`:
+
+- Pass the hook name via the `BASSCLEF_CALLING_HOOK` env var before the call. The default is `session-reflection` when unset.
+- Pass a plain severity (`blocking` / `advisory` / `info`) to `blocked_banner()` as the second arg.
+- The banner helper writes the marker on its own. No extra step.
+
+For hooks that fire BLOCK via plain `echo` to stderr (not via the shared helpers):
+
+- Follow-on retrofit per `.claude/rules/bootstrap-pair-discipline.md`. Adopt the shared helpers when the hook is next touched.
+
+## Anti-patterns
+
+**Hook writes a marker directly without using the lib.**
+INSTEAD source `lib/last-block.sh` and call `record_last_block`. The lib owns the format.
+
+**Marker format drift.**
+INSTEAD the plaintext layout stays pinned in `lib/last-block.sh`. Change the lib + Tier 0 tests + this rule in one PR.
+
+**BLOCK banner emitted directly to stderr without recording.**
+INSTEAD route through `blocked_banner()` so the marker lands with the banner. If a hook has a reason to skip the shared helper, call `record_last_block` directly after the echo.
+
+## Override
+
+`SKIP_LAST_BLOCK_RECORD=1` bypasses marker recording for one call. Logged via trace-helper. Rare — mostly for test fixtures that need to control marker writing timing.
+
+## Composes with
+
+- `.claude/rules/blocked-items.md` — sister rule; the two banner shapes live there, and this rule adds the persistence requirement
+- `.claude/rules/bootstrap-pair-discipline.md` — this rule + lib + skill + tests + settings wire ship together
+- `.claude/rules/testing-tier-config.md` — Tier 0 strict TDD on `lib/last-block.sh`
+- `.claude/rules/we-dont-break-adopters.md` — additive change; existing banner callers see no behavior change
+- `.claude/hooks/session-reflection.sh` — the hook that sources the lib + calls record_last_block from both banner helpers
+- `lib/last-block.sh` — the deep module
+- `.claude/skills/last-block/SKILL.md` — the user-invocable surface
+- @luminary john-ousterhout — deep module anchor
+- @luminary tony-hoare — pre/postcondition anchor (write path fail-soft)
+- @luminary michael-feathers — characterization anchor (Tier 0 tests pin every path)
+- @luminary don-norman — signifier (banner footer teaches the recovery path)
+- @luminary alan-cooper — goal-directed (one goal: get banner text back)
+- @luminary steve-krug — discoverability (no-args default)

package/dist/lite/.claude/skills/autonomous/SKILL.md

@@ -15,15 +15,19 @@ requires:
 
 # Autonomous Development
 
-Entry point for autonomous and semi-autonomous development sessions.
-Invoke at any point in any repo that inherits bassclef.
+<!-- FKGL-EXEMPT: cli#331 cure — orientation block names skill scope + tier split. Short SVO loses the tier contract. -->
+Entry point for autonomous SDLC sessions. Use in any repo inheriting bassclef.
 
-This file is a thin dispatcher. Deep procedural detail lives in:
+**Lite adopters:** this file is self-contained. The `## Lite procedure` block below has the minimum steps to run `/autonomous start`. No `strategy/` file is needed at lite tier.
 
-- `strategy/autonomous-dry-run.md` — read-only boot-sequence preview
-- `strategy/autonomous-boot-sequence.md` — `/autonomous start` scaffold +
-  activate, including Step 0–9, Construction automation A–E, pre-build
-  gates, branch stacking, context management, transition hierarchy
+**Standard and ultra adopters:** deeper procedure lives in these standard-tier files:
+
+- `strategy/autonomous-dry-run.md` — read-only boot preview
+- `strategy/autonomous-boot-sequence.md` — full `/autonomous start` steps 0-9 + Construction automation A-E
+- `strategy/agent-choreography.md` — multi-agent operational guide
+
+Per cli#331 — closes the "lite skill points at files lite doesn't ship" gap.
+<!-- /FKGL-EXEMPT -->
 
 ## Usage
 
@@ -263,6 +267,48 @@ silently proceed with defaults.
 
 ---
 
+## Lite procedure — self-contained minimum (cli#331)
+
+<!-- FKGL-EXEMPT: cli#331 cure — procedure block for lite adopters. Short SVO loses step contract. -->
+Lite adopters run `/autonomous start` with this block only. No `strategy/` file needed.
+
+**Step 0 — validate args.** Accept `operator-gated` or `orchestrator-gated` for gating. Accept `sequential` or `parallel` for mode. Reject anything else with a helpful error.
+
+**Step 1 — ask the operator two choices.** Gating (default: operator-gated). Mode (default: sequential). Use AskUserQuestion.
+
+**Step 2 — check readiness.** Run through this checklist. Scaffold missing items as you go:
+- `substrate.config.md` present → if missing, dispatch `/onboard-repo` first
+- `docs/whereami.md` present → if missing, dispatch `/onboard-repo` first
+- Current iteration goal doc at `docs/iteration-bets/<slug>.md` → if missing, ask operator for the goal; create a minimal doc
+- Session lock free → if active and >30 min old, clear with announcement
+- Chronicle fresh (last 24h) → if stale, note "will write at session-end"
+
+**Step 3 — risk register (optional on lite).** `docs/risk-register.md` is optional at lite tier. Create one only when operator asks or when mode is orchestrator-gated. Skip the check otherwise.
+
+**Step 4 — budget ceiling (optional on lite).** Ask the operator "how many turns are you OK spending on this session?" Default to "proceed until operator says stop" when operator skips. Record whatever they say in session memory.
+
+**Step 5 — confirm scope.** Echo the goal, the two choices, and the ceiling (or "no ceiling"). Ask: "Ready to start?" Wait for yes.
+
+**Step 6 — execute the SDLC chain.** Fire the agents in order per gating choice:
+- **operator-gated:** pause between each agent for operator approval. Agents: Shaper → PM → Architect → Designer → Builder → Reviewer → Deployer → Closer. Operator picks which fire.
+- **orchestrator-gated:** chain the agents without pausing. Each writes a handoff doc. Builder commits code. Reviewer runs `/verify`. PRs open for operator merge (or admin-merge within scope).
+
+**Step 7 — handle Construction.** For code work:
+- Parse scope into GitHub issues (one issue per discrete change)
+- Write stack manifest at `docs/stacks/<slug>.md` if more than one branch
+- Create branches with issue numbers in name (not placeholder — per bassclef#295)
+- Dispatch Builder per branch; fire `/temperance` + `/diagnose` + `/verify` per branch
+- Open PR per branch; squash merge after Reviewer PASS
+
+**Step 8 — close the session.** Dispatch `/session-end` which handles chronicle write, whereami bump, journal entry.
+
+Lite adopters at any point can escalate to operator-gated mode mid-session. Say "pause for me to review" and the next agent handoff waits.
+
+**Deep procedure for standard+ adopters.** Standard+ and ultra adopters have the strategy/ files above. Those cover Construction automation A-E, pre-build gates, branch stacking, context management, transition hierarchy, and the full choreography rules. Read them for the complete design.
+<!-- /FKGL-EXEMPT -->
+
+---
+
 ## Rules
 
 - Never start work without operator confirmation

package/dist/lite/.claude/skills/build/SKILL.md

@@ -255,7 +255,7 @@ FLOOR_PATTERN='src/lib/auth/|src/middleware\.ts|prisma/schema\.prisma|prisma/mig
 ACCEPTANCE_CONTENT=$(awk '
   /^```/{in_code = !in_code; next}
   in_code{next}
-  /^### WU-/{in_wu=1; next}
+  /^### (Step|WU)-/{in_wu=1; next}
   /^## /{in_wu=0}
   in_wu && /^- \[ \]/ {print}
 ' "docs/specs/${SPEC_PATH}.md" "docs/decompositions/${DECOMP_PATH}.md" 2>/dev/null)
@@ -273,8 +273,8 @@ fi
 ```
 
 **Why this is precise (per bassclef#366):** the scan only looks at
-step acceptance criteria (lines starting `- [ ]` under `### WU-N`
-headings, outside code blocks) plus file-path-shaped references in
+step acceptance criteria (lines starting `- [ ]` under `### Step-N`
+or `### WU-N` headings, outside code blocks) plus file-path-shaped references in
 the goal's frontmatter. Prose paragraphs that DESCRIBE the floor (like
 this section) don't trigger refusal. Code blocks that document the
 floor don't trigger refusal. Only structured ACTIONS the agent would
@@ -371,7 +371,13 @@ fi
 
 ### Phase 2b — Adopter-mode framing (bassclef#943)
 
-Two paths — adopter-mode and operator-mode. Default is adopter when the parent /launch used `--local` (cold-adopter context); operator-mode otherwise. Mode detection reads `docs/preview-state/<slug>.yml`: when `local_url` is present, /launch shipped via the adopter path, so /build follows.
+Two paths — adopter-mode and operator-mode. Default is adopter after a `/launch --local` run. Operator-mode is the default otherwise.
+
+Mode detection reads the goal doc's `preview_state:` frontmatter field. /launch writes that field. Open the file it names. When `local_url` is present, /build picks adopter-mode. Default to operator-mode when the field is absent.
+
+<!-- FKGL-EXEMPT: ticket reference -->
+Per sunj-labs/bassclef-cli#326.
+<!-- /FKGL-EXEMPT -->
 
 #### Adopter-mode pre-dispatch surface
 
@@ -590,7 +596,26 @@ already open. Operator merges inline.
 
 ### Phase 7 — ApprovalGateLink (LIVE — STUBBED)
 
-Tonight emits literal:
+<!-- FKGL-EXEMPT: cli#332 cure — Phase 7 branches on hosting_platform value. Three code-shape outputs. Technical stub-shape dispatch pattern. -->
+
+Phase 7 branches on `hosting_platform` read from `substrate.config.md`:
+
+**When `hosting_platform: none`** (lite adopters, operator-only tools, local-first apps) — emit:
+
+```
+TODO: live execution — built, not deployed. hosting_platform=none in
+substrate.config.md. The code is reviewed and committed. Running it is
+your choice.
+
+To add hosting later:
+  - Edit substrate.config.md: set hosting_platform to one of
+    github-pages | netlify | cloudflare-pages | vercel | amplify
+  - Run /onboard-repo --with-deploy-host to wire the host
+  - Then /build Phase 7 will dispatch /deploy-prod via GitHub Environment
+    + required-reviewer rail per manual-prod-approval.md.
+```
+
+**When `hosting_platform` is set to a known value** — emit:
 
 ```
 TODO: live execution — when all steps merged + CI green, would dispatch
@@ -599,6 +624,17 @@ required-reviewer rail per manual-prod-approval.md. Operator approves
 prod deploy via GitHub UI from phone. /build NEVER bypasses this rail.
 ```
 
+**When `hosting_platform` is unset or unrecognized** — emit:
+
+```
+TODO: live execution — hosting_platform not set in substrate.config.md.
+Can't deploy without a target. Set hosting_platform to one of none |
+github-pages | netlify | cloudflare-pages | vercel | amplify, then re-run.
+```
+
+Per cli#332 — closes the "lite promises deployed app without a deploy path" honesty gap.
+<!-- /FKGL-EXEMPT -->
+
 <!-- FKGL-EXEMPT: Phase 7.5 references paths + skip criteria per architect-review SKILL; technical dispatch stub matches sibling STUB pattern -->
 ### Phase 7.5 — /architect-review auto-dispatch (LIVE — STUBBED, per #1437 Step 2 wiring)
 

package/dist/lite/.claude/skills/deploy-prod/SKILL.md

@@ -17,8 +17,18 @@ requires:
 
 # Deploy to Production
 
+<!-- FKGL-EXEMPT: cli#332 cure — tier contract block names scope + override path. Short SVO loses host-override contract. -->
 Standard deployment procedure. Run after code is reviewed and ready to ship.
 
+**Tier contract (per cli#332):**
+
+- This skill ships at `tier: lite` as a generic 5-step template: test → build → push → CI → verify.
+- The template body is host-agnostic. Host-specific commands (AWS, Vercel, Netlify, Fly, Railway, GitHub Pages) are not shipped here.
+- When `substrate.config.md` sets `hosting_platform` to a known value, standard-tier adopters add a host-specific wrapper that calls this skill AND runs the host commands. Lite adopters without `hosting_platform` run the template steps + stop.
+- `/build` Phase 7 dispatches this skill only when `hosting_platform` is set to a known value — see /build Phase 7 branching logic per cli#332.
+- `manual-prod-approval.md` applies in all tiers: GitHub Environment `prod` with required reviewer MUST be configured before any prod deploy fires.
+<!-- /FKGL-EXEMPT -->
+
 ## Procedure
 
 ### Step 1: Pre-flight

package/dist/lite/.claude/skills/ia-model/SKILL.md

@@ -62,6 +62,14 @@ Derive nav from the screen map. Apply Peter Morville's IA framework:
 - **C**ategory: by type or classification
 - **H**ierarchy: by importance or score
 
+## Output file
+
+Write to `docs/ia-models/<slug>.md`. Use the active goal or sprint slug. `/launch` Phase 6 reads from this path. `/build` Phase 0.5 reads from the same path.
+
+<!-- FKGL-EXEMPT: ticket reference -->
+Per sunj-labs/bassclef-cli#317.
+<!-- /FKGL-EXEMPT -->
+
 ## Output Format
 
 ```markdown

package/dist/lite/.claude/skills/interaction-design/SKILL.md

@@ -68,6 +68,14 @@ BACKSTAGE (system does):    Score → Index → Enrich → Notify
 SUPPORT PROCESSES:          Ingest → Classify → Deduplicate
 ```
 
+## Output file
+
+Write to `docs/interaction-designs/<slug>.md`. Use the active goal or sprint slug. `/build` Phase 0.5 reads from this path. `/launch` Phase 7 reads from the same path.
+
+<!-- FKGL-EXEMPT: ticket reference -->
+Per sunj-labs/bassclef-cli#317.
+<!-- /FKGL-EXEMPT -->
+
 ## Output Format
 
 For each interaction flow:

package/dist/lite/.claude/skills/jtbd-tasks/SKILL.md

@@ -188,9 +188,17 @@ For each JTBD, produce:
 | 1.1 ... | [job] | [screen or component implied] |
 ```
 
+## Output file
+
+Write to `docs/jtbd/<slug>.md`. Use the active goal or sprint slug. `/build` Phase 0.5 reads from this path. See the ticket noted at the end of this skill body.
+
+<!-- FKGL-EXEMPT: ticket reference -->
+Per sunj-labs/bassclef-cli#317.
+<!-- /FKGL-EXEMPT -->
+
 ## Next Step
 
-Output feeds into `/task-scenarios` (user stories) or directly into `/ia-model` (entity-driven IA).
+The output feeds `/task-scenarios` for user stories. Or it feeds `/ia-model` to drive IA.
 
 ## References
 

package/dist/lite/.claude/skills/last-block/SKILL.md

@@ -0,0 +1,99 @@
+---
+name: last-block
+description: Print the exact text of a BLOCK or guardrail banner you saw this session or prior. No args shows the newest. One hook name shows that hook. --list enumerates every stored banner newest first.
+tier: lite
+user_invocable: true
+disable_model_invocation: false
+authoring_luminaries:
+  primary: john-ousterhout
+  supporting:
+    - tony-hoare
+    - michael-feathers
+composes_with: []
+---
+
+# /last-block
+
+## What you get
+
+An adopter who sees a BLOCK banner can retrieve the exact text later. No scrolling through the terminal. No grep over trace logs. Type `/last-block`. The banner prints.
+
+## When to use it
+
+Three cases.
+
+- You saw a BLOCK banner, scrolled past it, and want to re-read the recipe or override instruction.
+- You want to file a ticket and need the exact BLOCK text as evidence.
+- You want to see which hooks fired BLOCK during the prior session.
+
+## Usage
+
+```
+/last-block                 # print the newest stored banner
+/last-block <hook-name>     # print the banner stored under <hook-name>
+/last-block --list          # list every stored banner newest first
+```
+
+## How it works
+
+Every BLOCK banner printed by `blocked_banner()` or `guardrail_banner()` persists a marker at `state/markers/last-block/<hook>.marker`. Per-hook markers overwrite on each fire. The lib `lib/last-block.sh` reads them back.
+
+Marker format is plaintext:
+
+```
+hook: <hook-name>
+severity: blocking|advisory|info|guardrail
+fired_at: <ISO-8601 UTC>
+session: <session-id or unknown>
+---
+<verbatim banner text, truncated at 8KB>
+```
+
+## Procedure
+
+1. Source `lib/last-block.sh`.
+2. If `--list` arg, call `list_last_blocks` and print to stdout.
+3. If a hook-name arg, call `read_last_block <hook>` and print.
+4. Else call `read_last_block` and print the newest.
+5. Exit 0 on hit, 1 on miss.
+
+## Example
+
+```
+$ /last-block
+hook: pre-commit-gate
+severity: blocking
+fired_at: 2026-10-04T15:21:08Z
+session: 2026-10-04-slot-6
+---
+🛑 BLOCKED: path contains operator identifier /Users/<name>/...
+Override: SKIP_OPERATOR_PATHS=1 git commit ...
+```
+
+## FAQ
+
+### What hooks persist markers?
+
+Any hook that calls `blocked_banner()` or `guardrail_banner()` from `session-reflection.sh`. ~27 call sites today. Hooks that fire BLOCK via plain `echo` to stderr are a follow-on retrofit.
+
+### Does the marker persist across machines?
+
+No. Markers live in `state/markers/last-block/` which bassclef-upstream gitignores. The marker survives the session that wrote it; it does not sync to teammates.
+
+### Can I clear markers?
+
+Yes — delete `state/markers/last-block/<hook>.marker` or the whole directory. Next BLOCK fire re-populates.
+
+### What if the lib is missing?
+
+The banner helpers detect missing lib and skip the record call. Banners still print. The marker is just not written. `/last-block` reports "no block recorded".
+
+## Refs
+
+- Ticket: bassclef-upstream#2036 Finding #10
+- UC: `docs/use-cases/UC-skill-last-block.md`
+- Rule: `.claude/rules/last-block-marker.md`
+- Lib: `lib/last-block.sh`
+- Sister rule: `.claude/rules/blocked-items.md`
+- Luminary: `.claude/luminaries/john-ousterhout.md` (deep module)
+- /rfc outside lenses: `.claude/luminaries/don-norman.md` + `.claude/luminaries/steve-krug.md` + `.claude/luminaries/alan-cooper.md`

package/dist/lite/.claude/skills/launch/SKILL.md

@@ -309,9 +309,35 @@ Per `standards/voice-input-pattern.md` + Phase V Hey-Alexa MVD goal (`docs/itera
 - Existing text-mode + brownfield-mode behavior unchanged when flag absent
 - Composes with `--brownfield` (rare; voice-driven brownfield refactor is plausible but not the MVD path)
 
+### Phase 0b — hosting_platform ask (per cli#332)
+
+<!-- FKGL-EXEMPT: cli#332 cure — hosting_platform ask step. Short SVO loses the config-key contract. -->
+Read `substrate.config.md` for the `hosting_platform` key. If unset or missing, ask the operator once:
+
+```
+Where should this run?
+  a. local only (default — develop + preview on your machine)
+  b. a static host (GitHub Pages / Netlify / Cloudflare Pages / Vercel)
+  c. a server host (Amplify / Fly.io / Railway)
+  d. I'll deploy myself — just build the plan
+```
+
+Write the answer to `substrate.config.md` `hosting_platform`:
+- `a` → `hosting_platform: none`
+- `b` → prompt for which static host; write that value (`github-pages` / `netlify` / `cloudflare-pages` / `vercel`)
+- `c` → prompt for which server host; write that value (`amplify` / `fly` / `railway`)
+- `d` → `hosting_platform: operator-managed`
+
+If already set, skip the question. The answer flows to /build Phase 7 which branches on this value per cli#332.
+
+Per cli#332 — closes "Nothing asks where the app will run" at the earliest surface in the chain.
+<!-- /FKGL-EXEMPT -->
+
 ### Phase 1 — `/interpret-input`
 
+<!-- FKGL-EXEMPT: pre-existing text-mode + brownfield-mode description — technical dispatch contract per bassclef#459 sub-goal 1. -->
 Dispatches `/interpret-input` with the type detected by Phase 0. Text mode preserves the existing text-mode behavior; brownfield mode invokes the Phase C extractor (LR2 WU-1, bassclef#459 sub-goal 1) which walks the repo and populates structural hints (entities, actors, routes, README excerpt).
+<!-- /FKGL-EXEMPT -->
 
 ```bash
 # Generate sprint slug + InputArtifact path
@@ -353,7 +379,7 @@ Produces `InputArtifact` at `docs/input-artifacts/<sprint-slug>-input.json`. Dow
 ### Phase 2 — `/objectory-decompose` (full BCE matrix)
 
 Same as `/stage` Phase 2 — Jacobson method via `/objectory-decompose`.
-Output: `docs/decompositions/<slug>-domain.md` with entity inventory
+Output: `docs/decompositions/<sprint-slug>-input-domain.md` with entity inventory
 + actor list + verb-goal pairs + BCE matrix.
 
 **Distinction from `/stage`**: medium + full consume the FULL BCE
@@ -474,7 +500,7 @@ map derived from BCE entities.
 /interaction-design    # consumes /ia-model + /use-case
 ```
 
-Output: state diagrams + sequence diagrams in `docs/interaction-design/<slug>/`.
+Output: state diagrams + sequence diagrams in `docs/interaction-designs/<slug>.md` (per sunj-labs/bassclef-cli#317).
 
 ### Phase 8 — `/decompose` (GRASP responsibility assignment)
 
@@ -526,12 +552,18 @@ to produce reviews per perspective. Reviews surface in PR body.
 /ux-migration <chosen-variant-slug>   # if base= provided, use that; else operator chooses post-gallery
 ```
 
-Output: `docs/specs/ux-migration-<slug>.md` — token extraction +
-prototype-HTML→React mapping table + work packages with dependency-aware
-build order.
+<!-- FKGL-EXEMPT: cli#324 cure — technical precision required naming paired SKILL steps + file paths -->
+
+Output: `docs/specs/ux-migration-<slug>.md` carries token extraction, prototype-to-React mapping, and work packages.
+
+**When to run full `/ux-migration` vs partial (cli#324):**
+
+- **Existing UI (redesign).** Run the full skill. The `/ux-migration` SKILL names this a MUST for redesigns.
+- **Greenfield (no existing UI).** Run only Step 3b and Step 3c. Step 3b extracts design tokens. Step 3c maps prototype HTML to React components. The `/ux-migration` SKILL says skip the full migration for greenfield.
+
+Pick by project state. Does `src/app/` carry a shipping UI? Yes means redesign. No means greenfield. When unsure, default to greenfield partial. The full gate's output is a component diff. A component diff has no value on an empty tree.
 
-This is the `/ux-migration` MUST gate per existing prototype-variants
-SKILL.md §"Step 7 — Selection → pipeline to Construction".
+<!-- /FKGL-EXEMPT -->
 
 ### Phase 12 — Deploy or local-serve (mode-gated)
 
@@ -595,9 +627,9 @@ status != build-ready.
 ### Phase 14 — Scaffold Construction iteration-goal draft
 
 ```yaml
-# docs/iteration-bets/<YYYY-MM-DD>-<sprint-slug>-construction.md (DRAFT)
+# docs/iteration-bets/<sprint-slug>-construction.md (DRAFT)   # cli#326
 ---
-slug: <YYYY-MM-DD>-<sprint-slug>-construction
+slug: <sprint-slug>-construction
 phase: Construction
 status: draft   # operator must change to "active" before /build-iteration runs
 parent_roadmap: docs/roadmaps/<roadmap-slug>.md  # if known
@@ -611,8 +643,8 @@ references:
   - {type: spec, id: <sprint-slug>}
   - {type: decomposition, id: <sprint-slug>-grasp}
   - {type: input-artifact, id: <sprint-slug>-input}
-appetite:
-  mode: scope-bounded
+time_budget:
+  mode: fixed-scope
   estimated_turns: <derived from /spec step enumeration>
   stopping_criteria:
     - All step PRs filed (count from spec)
@@ -651,7 +683,7 @@ appetite:
 **Viability signal**:
 (derived from /spec acceptance criteria; operator confirms)
 
-**Appetite**:
+**Time budget**:
 (derived from spec step enumeration; operator finalizes)
 ```
 

package/dist/lite/.claude/skills/objectory-decompose/SKILL.md

@@ -57,12 +57,6 @@ source lib/state.sh
 INPUT=$(state_reference_get input-artifact "<slug>")
 ```
 
-Or via wrapper:
-
-```bash
-INPUT=$(bash scripts/state.sh get reference input-artifact "<slug>")
-```
-
 **Required fields** (extract via `jq`):
 - `extracted_text` — the load-bearing input for analysis
 - `type` — guides extraction (text vs. URL vs. image have different signals)
@@ -164,18 +158,12 @@ phase: jacobson  # marks Phase B MVP scope; cockburn is follow-up
 
 ### 4. Validate output
 
-After writing, the state-validate.sh hook validates the frontmatter
-against `decomposition.schema.json`. If invalid, the write BLOCKs;
-fix frontmatter and retry.
-
-Or invoke explicitly:
-
-```bash
-bash scripts/state.sh validate docs/decompositions/<slug>-domain.md
-```
+The state-validate.sh hook runs on write. It checks the frontmatter
+against `decomposition.schema.json`. A failed check BLOCKs the write.
+Fix the frontmatter and retry.
 
-Exit 0 = clean; exit 3 = schema violation (BLOCK message names the
-field).
+Exit 0 = clean. Exit 3 = schema violation. The BLOCK message names
+the field.
 
 ### 5. Surface to next step
 

package/dist/lite/.claude/skills/onboard-repo/SKILL.md

@@ -433,25 +433,25 @@ Idempotent API calls against the target repo via `gh`.
 # Read from git remote — don't infer from cwd basename (cwd can be renamed)
 REPO=$(gh repo view --json nameWithOwner -q .nameWithOwner)
 
-declare -A LABELS=(
-  [bassclef-evolution]="A6E0F2:Candidate for promotion to bassclef"
-  [agent-user-proposed]="D4A5F5:Proposed by agent in an app repo"
-  [bassclef-sync]="8FD4A4:Related to bassclef substrate syncing"
-  [review-required]="F5B94A:Blocks — human review required"
-  [bug]="E4443A:Defect"
-  [enhancement]="A2EEEF:New or improved functionality"
-  [security]="FF0000:Security-relevant"
-  [infra]="C9D1D9:Infrastructure / workflows / tooling"
-  [priority-high]="E4443A:High priority"
-  [priority-medium]="F5B94A:Medium priority"
-  [question]="D876E3:Needs operator input or design discussion"
-)
-
-for NAME in "${!LABELS[@]}"; do
-  COLOR="${LABELS[$NAME]%%:*}"
-  DESC="${LABELS[$NAME]#*:}"
+# Per cli#306 — use while-read loop over pipe-delimited heredoc instead
+# of `declare -A`. macOS ships bash 3.2 which has no associative arrays.
+# Format per line: NAME|COLOR|DESCRIPTION
+while IFS='|' read -r NAME COLOR DESC; do
+  [ -z "$NAME" ] && continue
   gh label create "$NAME" --repo "$REPO" --color "$COLOR" --description "$DESC" --force >/dev/null
-done
+done <<'EOF'
+bassclef-evolution|A6E0F2|Candidate for promotion to bassclef
+agent-user-proposed|D4A5F5|Proposed by agent in an app repo
+bassclef-sync|8FD4A4|Related to bassclef substrate syncing
+review-required|F5B94A|Blocks — human review required
+bug|E4443A|Defect
+enhancement|A2EEEF|New or improved functionality
+security|FF0000|Security-relevant
+infra|C9D1D9|Infrastructure / workflows / tooling
+priority-high|E4443A|High priority
+priority-medium|F5B94A|Medium priority
+question|D876E3|Needs operator input or design discussion
+EOF
 ```
 
 Uses `--force` so the call is idempotent (updates existing label or

package/dist/lite/.claude/skills/personas/SKILL.md

@@ -87,7 +87,7 @@ When no persona files exist in the repo, auto-populate a minimal persona file fo
 
 - `CLAUDE.md` — read the "What this repo is" / "Active initiative" sections for goal context
 - `substrate.config.md` — read `agents:` and `deploy_targets:` for role context
-- If a git `user.email` exists, use it to derive a rough slug (`operator-[local-part]`), otherwise `operator`
+- Default slug: `operator`. Do not derive it from `user.email`. GitHub no-reply addresses carry the account ID and handle. The slug then leaks into committed docs (cli#320). Ask for a display name in-turn if the operator wants one.
 
 Emit the operator default to the conversation (not to disk — operator decides whether to persist it):
 

package/dist/lite/.claude/skills/use-case/SKILL.md

@@ -101,10 +101,11 @@ if a required input is missing:
 1. **Personas** — `docs/personas/*.md` (preferred) or
    `docs/design/personas/*.md` (legacy). Use-case's **primary
    actor** MUST be a persona slug, not "user."
-2. **JTBDs** — `docs/design/personas/[persona]/jtbds.md` or
-   equivalent. Each use case has a single **goal** that traces to
-   a JTBD outcome. Halt if no JTBDs for the scope in question
-   (warn the operator; offer to run `/jtbd-tasks` first).
+2. **JTBDs** — `docs/jtbd/*.md` (preferred, per cli#317) or
+   `docs/design/personas/[persona]/jtbds.md` (legacy fallback).
+   Each use case has a single **goal** that traces to a JTBD
+   outcome. Halt if no JTBDs for the scope in question (warn the
+   operator; offer to run `/jtbd-tasks` first).
 3. **Value Prop Canvas** (optional) — `docs/value-prop-canvas/*.md`.
    When present, Pain-Relievers + Gain-Creators ground the "why
    this goal matters" framing in the stakeholders+interests block.

package/dist/lite/bassclef-version.json

@@ -1,7 +1,7 @@
 {
-  "version": "v1.6.6",
-  "marker_tag": "release-2026-10-03-89ceaa15",
-  "release_date": "2026-10-03T10:51:10Z",
-  "release_sha": "89ceaa15",
-  "release_tag": "release-2026-10-03-89ceaa15"
+  "version": "v1.8.0",
+  "marker_tag": "release-2026-10-06-a874c748",
+  "release_date": "2026-10-06T20:56:57Z",
+  "release_sha": "a874c748",
+  "release_tag": "v1.8.0"
 }