@zalom/plastic 2.0.0-alpha.12 → 2.0.0-alpha.14

package/skills/intent-ending/SKILL.md

@@ -144,11 +144,13 @@ ruby ~/.plastic/scripts/qmd-sync reindex --store <store-root> --async
 No-op when QMD is absent. Runs in the background so it never blocks the
 turn.
 
-### Step 7. EM-to-CTO report
+### Step 7. Print `delivered`
 
-Brief the human like an engineering manager to a CTO: impact and risk first,
-in plain language, the decision left to them (merge, release, or accept).
-See `outcome.md` for the details; do not restate it verbatim.
+Print `ruby ~/.plastic/scripts/report-screen delivered <intent_dir>` as the first characters
+of the reply: nothing before it, no fence, or the hook cannot paint it. Asked, Delivered (with
+its Proven-by column), Evidence, and Needs you come straight from the record - the EM-to-CTO
+report, impact and risk first, in plain language, with the decision left to the human (merge,
+release, or accept). See `outcome.md` for the details; do not restate it verbatim.
 
 ## Abandoned is the same procedure
 

package/skills/intent-executing/SKILL.md

@@ -63,6 +63,8 @@ Dispatch ONE executor subagent and give it the whole delivery: every task's full
 
 After each commit lands (the red commit and every commit after it), append a `Commit` line to the savepoint ledger: `ruby ~/.plastic/scripts/savepoint-note <intent_dir> --kind Commit --text "<sha> <what it proves>"` (intent 317, D17). This is what feeds `report-screen delay`; a commit with no line is a gap the delay report cannot explain.
 
+Print `ruby ~/.plastic/scripts/report-screen state <intent_dir> --changed "<what just landed>"` as the first characters of the reply, nothing before it, no fence, right after the red commit and again once the suite goes green (intent 331f).
+
 Read its response by code:
 - DONE or DONE_WITH_CONCERNS → proceed to Step 3.
 - NEEDS_CONTEXT → provide the missing context, re-dispatch the executor.

package/skills/intent-speccing/SKILL.md

@@ -111,10 +111,13 @@ When the rulings are enough to build from:
    rulings say more than the record already does.
 3. **Self-verify.** Read `references/self-verify-checklist.md` before presenting; fix any
    failing check and re-verify from the top.
-4. **Present and hand off.** Present `spec.md` and the action files. Then offer the routes:
-   run it now inline when the work is small enough for direct mode; hand to `plastic-auto`
-   when the owner says auto and the checklist above passes (all decisions resolved, scope
-   bounded, dependencies named, success criteria defined); or keep thinking.
+4. **Present and hand off.** Print `ruby ~/.plastic/scripts/report-screen plan <intent_dir>` as
+   the first characters of the reply: nothing before it, no fence, or the hook cannot paint it.
+   It carries Asked, Decisions, Steps, Mode, Reviewer, then the Steps and Risks tables, filled
+   from `spec.md` and the action files just written, never restated by eye. Then offer the
+   routes: run it now inline when the work is small enough for direct mode; hand to
+   `plastic-auto` when the owner says auto and the checklist above passes (all decisions
+   resolved, scope bounded, dependencies named, success criteria defined); or keep thinking.
 
 Report, in this order: which files were written (`spec.md` new or rewritten, the action
 files), the count of acceptance criteria, which `## Insights` rulings superseded an earlier

package/skills/roadmap/SKILL.md

@@ -47,6 +47,15 @@ Read `../plastic-conventions/references/roadmaps.md` for the roadmap file format
 semantics, and the status-mirror rule that this skill's own file-format reference builds on. This
 path resolves relative to this skill's own installed directory.
 
+## Reports (intent 331f)
+
+Each verb prints its report screen as the first characters of the reply: nothing before it, no
+fence, or the hook cannot paint it.
+
+- Create prints `ruby ~/.plastic/scripts/report-screen roadmap <roadmap.md> plan`.
+- Read / consume prints `ruby ~/.plastic/scripts/report-screen roadmap <roadmap.md> state`.
+- Close / archive prints `ruby ~/.plastic/scripts/report-screen roadmap <roadmap.md> delivered`.
+
 ## Notes
 
 - File location and the four-section shape are identical across tiers; do not invent a different

package/skills/roadmap/references/file-format.md

@@ -96,6 +96,16 @@ The ledger is derived and rebuildable (`ruby ~/.plastic/scripts/roadmap-savepoin
 roadmaps/{slug}.md`, reconstructing it from `## Log`), never a status source: `INDEX.md` stays the
 single writer of intent status, exactly as for the roadmap file itself.
 
+## Screens read this format (intent 331c)
+
+`report-screen roadmap <roadmap.md> plan|state|delivered` reads exactly the shapes above and
+nothing else: `## Goal`'s first sentence, the `## Batches` (or legacy `## Waves`) grouping and its
+entries (through `RoadmapQueue`'s own reconciled reader - INDEX still wins), and the events from
+the savepoint ledger, falling back to `## Log` classified through the same keyword vocabulary when
+no ledger file exists (an archived roadmap moved before intent 134 shipped, `manual-first.md`
+among them). A screen never invents a status, a time, or a merge sha the file, `INDEX.md`, or the
+ledger did not already carry - the same `not recorded` floor the intent screens use.
+
 ## Worked example
 
 ```

package/templates/dashboard-screen.md

@@ -0,0 +1,22 @@
+## ▶ {{scope}} · dashboard
+
+| | | |
+| --- | --- | --- |
+| **Active**      | {{active}} | intents |
+| **In delivery** | {{in_delivery}} | with a fresh lock |
+| **Delivered**   | {{delivered}} | in the last 7 days |
+| **Roadmap**     | {{roadmap}} | frontier batch |
+| **Sessions**    | {{sessions}} | alive |
+| **Changed**     | {{changed}} | newest savepoint |
+
+**Where we are**
+
+| Graph ID | Intent | Stage | Progress | Lead |
+| --- | --- | --- | --- | --- |
+{{where_we_are.rows}}
+
+**Where we go next**
+
+| Rank | Graph ID | Intent | Reason |
+| --- | --- | --- | --- |
+{{where_we_go_next.rows}}

package/templates/display-fixture.md

@@ -0,0 +1,21 @@
+<!-- Doctor's display self-test fixture (intent 331e). Replayed through the
+     installed MessageDisplay hook by `display_hook_paints` to prove painting
+     still works; this is NOT a report-screen scaffold (no {{...}} mustache
+     placeholders) and ships no data of its own. -->
+
+## ▶ 331e · Doctor display check
+
+| | | |
+| --- | --- | --- |
+| **Store**     | project:plastic                | the plastic project store |
+| **Status**    | Active                          | listed under ## Active in INDEX.md |
+| **Stage**     | Exec                            | What, Why, How, Exec delivered; the work is open |
+| **Progress**  | ██████████░░░░░░░░░░ 3 / 6      | 3 steps open |
+
+**Steps**
+
+| Step | Status | What |
+| --- | --- | --- |
+| S1 | done | Tests red |
+| S2 | done | check_display_registration in doctor_core.rb |
+| S3 | open | The three full-run checks in doctor.rb |

package/templates/intent-screen.md

@@ -12,6 +12,6 @@
 
 **Steps**
 
-| Step | Status | What |
+| Step | Status | Detail |
 | --- | --- | --- |
 {{steps.rows}}

package/templates/report-plan.md

@@ -0,0 +1,15 @@
+## ▶ {{id}} · {{name}} · plan
+
+| | | |
+| --- | --- | --- |
+{{fields.rows}}
+
+**Steps**
+
+| Step | Action | Detail |
+| --- | --- | --- |
+{{steps.rows}}
+
+**Risks**
+
+{{risks.block}}

package/templates/report-roadmap-delivered.md

@@ -0,0 +1,10 @@
+## ✔ {{slug}} · roadmap · delivered
+{{meta}}
+
+**Delivered**
+
+{{delivered.table}}
+
+**Log**
+
+{{log.table}}

package/templates/report-roadmap-plan.md

@@ -0,0 +1,9 @@
+## ▶ {{slug}} · roadmap · plan
+
+| | | |
+| --- | --- | --- |
+{{fields.rows}}
+
+**Batches**
+
+{{entries.table}}

package/templates/report-roadmap-state.md

@@ -0,0 +1,9 @@
+## ▶ {{slug}} · roadmap
+
+| | | |
+| --- | --- | --- |
+{{fields.rows}}
+
+**Batches**
+
+{{entries.table}}

package/templates/report-state.md

@@ -6,6 +6,6 @@
 
 **Steps**
 
-| Step | Status | What |
+| Step | Status | Detail |
 | --- | --- | --- |
 {{steps.rows}}