@tgoodington/intuition 11.9.0 → 11.9.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@tgoodington/intuition",
-  "version": "11.9.0",
+  "version": "11.9.1",
   "description": "Domain-adaptive workflow system for Claude Code. Includes the Enuncia pipeline (discovery, compose, design, execute, verify) and the classic pipeline (prompt, outline, assemble, detail, build, test, implement).",
   "keywords": [
     "claude-code",

package/skills/intuition-enuncia-compose/SKILL.md

@@ -283,7 +283,7 @@ Before moving to approval, verify the outline against the discovery brief. This
 
 **Who**: Does every stakeholder from the brief have at least one experience slice addressing their journey? If a stakeholder was named in the brief but has no slice, either add one or explain why their experience doesn't require anything to be built.
 
-**Where**: Do the tasks collectively produce something deliverable through the mechanism the brief specifies? If the brief says "district-hosted app" but no task covers deployment or hosting, there's a gap.
+**Where**: Do the tasks collectively produce something deliverable through the mechanism the brief specifies — *including the thing that serves or runs it*? A networked deliverable (web page, API, hosted app) needs a task that produces its serving/runtime surface, not just the markup and the logic. If the only tasks are UI and business logic with nothing that hosts or serves them, that's a gap — add a task, or fold serving explicitly into an existing task AND reflect it in the map so no `## Component Reference` entry lacks a producing task. If the brief says "district-hosted app" but no task covers deployment or hosting, there's a gap.
 
 **What**: Walk through every goal, requirement, and constraint in the brief:
 - Each **goal** should map to one or more experience slices

package/skills/intuition-enuncia-discovery/SKILL.md

@@ -31,6 +31,7 @@ You help users figure out what they're building. You do this through focused con
 13. You MUST run the Exit Protocol after writing the brief and updating the map. Route to `/intuition-enuncia-compose`.
 14. You MUST NOT launch research agents proactively. Research fires ONLY when the user asks something you cannot confidently answer (see REACTIVE RESEARCH).
 15. You MUST read `track` from the active context and, when `track == "express"`, compress the conversation per EXPRESS MODE. A missing `track` defaults to `"full"`.
+16. At activation, after reading state, you MUST set `workflow.discovery.started = true` on the active context and write state back — before any dialogue. This closes the TRIAGE gate so a re-run of `start` mid-discovery does not re-fire triage and re-ask the scope question.
 
 ## THE FOUR DIMENSIONS
 
@@ -386,7 +387,7 @@ After writing the brief and updating the project map:
 - IF `active_context == "trunk"`: update `state.trunk`
 - ELSE: update `state.branches[active_context]`
 
-Set on target: `status` -> `"outline"`, `workflow.discovery.completed` -> `true`, `workflow.discovery.completed_at` -> current ISO timestamp, `workflow.compose.started` -> `true`. Set on root: `last_handoff` -> current ISO timestamp, `last_handoff_transition` -> `"discovery_to_compose"`. Write the updated state back.
+Set on target: `status` -> `"compose"`, `workflow.discovery.completed` -> `true`, `workflow.discovery.completed_at` -> current ISO timestamp, `workflow.compose.started` -> `true`. Set on root: `last_handoff` -> current ISO timestamp, `last_handoff_transition` -> `"discovery_to_compose"`. Write the updated state back.
 
 **2. Route:** Tell the user:
 

package/skills/intuition-enuncia-verify/SKILL.md

@@ -429,6 +429,12 @@ Correct the map in place. If reconciliation reveals real architectural drift the
 
 **Run the GOAL ALIGNMENT → Alignment Check** against the three loaded goals. Any failures must be fixed or explicitly flagged in the final results.
 
+**Append a Verify row to `docs/project_notes/map_history.md`** (create from template if missing). On a branch, Step 11 appends the consolidation row instead — do NOT double-log; skip this append on branches. On trunk:
+
+| Date | Phase | Branch | Change | Reason |
+|------|-------|--------|--------|--------|
+| [today ISO date] | Verify | trunk | Verified live; map reconciled | [one sentence — what was verified] |
+
 ### STEP 11: CONSOLIDATE INTO TRUNK ARCHITECTURE (branch mode only)
 
 Skip this step on trunk — there's nothing to consolidate.