@zalom/plastic 2.0.0-alpha.16 → 2.0.0-alpha.17

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@zalom/plastic",
-  "version": "2.0.0-alpha.16",
+  "version": "2.0.0-alpha.17",
   "description": "Intent-driven idea development system for AI coding agents",
   "type": "module",
   "bin": {

package/scripts/lib/report_screen.rb

@@ -577,30 +577,69 @@ module ReportScreen
     rows.compact
   end
 
-  # Intent 331b (plan.md, "The one non-additive edit"): the standalone-token
-  # rule, extracted so `action_file_for` (the plan screen's Action column)
-  # calls the exact same rule as `matching_action_heading` and the two can
-  # never drift on what counts as a match. `matching_action_heading`'s own
-  # signature, return shape and behavior are unchanged (row P16).
-  def self.heading_tokens(heading)
-    heading.to_s.sub(/\A#+\s*/, "").split(/[^A-Za-z0-9]+/)
-  end
-
-  # Rows 25-27: D19 - the label must appear as a standalone token in an action
-  # file heading (any level); the count is the matched section's table rows only.
-  def self.matching_action_heading(intent_dir, label)
+# Intent 331b (plan.md, "The one non-additive edit"): the standalone-token
+# rule, extracted so `action_file_for` (the plan screen's Action column)
+# calls the exact same rule as `matching_action_heading` and the two can
+# never drift on what counts as a match.
+def self.heading_tokens(heading)
+  heading.to_s.sub(/\A#+\s*/, "").split(/[^A-Za-z0-9]+/)
+end
+
+# Rows 25-27: D19/D1r - the label must appear as a standalone token in an
+# action file heading (any level), AND that heading must own at least one
+# matrix data row - a heading that only names the label, with no table
+# beneath it (or a table with a separator but no data row), is skipped and
+# the walk keeps going. Lexicographic path order (D8), then file order.
+#
+# Merge note (322 into alpha, 2026-09-05): 322's table-owning rule and 331b's
+# extracted `heading_tokens` are both kept. The token split now comes from the
+# shared helper so `action_file_for` cannot drift from this walk, while the
+# `table_rows(body).any?` guard stays the thing that decides the match.
+def self.matching_action_heading(intent_dir, label)
+  Dir.glob(File.join(intent_dir, "actions", "*.md")).sort.each do |path|
+    split_by_headings(File.read(path)).each do |heading, body|
+      next unless heading_tokens(heading).include?(label)
+      return [heading, body] if table_rows(body).any?
+      end
+    end
+    [nil, nil]
+  end
+
+  # D3r: the row-cell fallback, for the shape where the label never appears in
+  # a heading at all, only as the first cell of a matrix data row. Restricted
+  # to tables under a heading that names itself a matrix (/matrix/i) - never a
+  # step list or any other table - so it cannot answer for a record that has
+  # no matrix anywhere (the close-gate defeat the plan review measured).
+  # Emphasis (bold/italic/code) is stripped from the compared cell; the count
+  # sums matching rows across every matrix heading, in every action file.
+  def self.matching_matrix_rows(intent_dir, label)
+    count = 0
     Dir.glob(File.join(intent_dir, "actions", "*.md")).sort.each do |path|
       split_by_headings(File.read(path)).each do |heading, body|
-        return [heading, body] if heading_tokens(heading).include?(label)
+        next unless heading.to_s.match?(/matrix/i)
+        table_rows(body).each do |cells|
+          cell = cells[0].to_s.gsub(/[*_`]/, "").strip
+          count += 1 if cell == label
+        end
       end
     end
-    [nil, nil]
+    count
   end
 
+  # D7: a label with no letter never resolves, on either path - it is a
+  # bullet-derived Delivered number (delivered_rows), never a label anyone
+  # wrote, and would otherwise fabricate proof from a numbered heading like
+  # "## 1. What this intent is" or from a numbered matrix row-cell column.
   def self.proven_by(intent_dir, label)
+    return NOT_RECORDED unless label.to_s.match?(/[A-Za-z]/)
+
     _heading, body = matching_action_heading(intent_dir, label)
-    return NOT_RECORDED unless body
-    n = table_rows(body).length
+    if body
+      n = table_rows(body).length
+      return n.positive? ? "#{n} test#{n == 1 ? '' : 's'}" : NOT_RECORDED
+    end
+
+    n = matching_matrix_rows(intent_dir, label)
     n.positive? ? "#{n} test#{n == 1 ? '' : 's'}" : NOT_RECORDED
   end
 

package/skills/intent-ending/SKILL.md

@@ -67,9 +67,10 @@ fill `## Summary`, `## Delivered`, `## Verification`, `## Follow-ups`. `## Deliv
 `| Row | What |` table: one row per thing delivered, in plain wording a reader
 recognizes, not a method name or an implementation summary (that detail
 belongs in `## Summary`). Each row's label must appear as a standalone token
-in an action-file heading (`### S1 - ...` proves row S1); that heading's
-matrix rows become the row's Proven-by cell on `report-screen delivered`'s
-post-delivery screen. `## Needs you` is the literal None or a
+in an action-file heading that owns the matrix table (`### S1 - ...` with a
+table beneath it proves row S1; a table-less heading naming the label is
+skipped); that heading's matrix rows become the row's Proven-by cell on
+`report-screen delivered`'s post-delivery screen. `## Needs you` is the literal None or a
 `| N | What | Why |` table. On abandon, `## Summary` states the abandonment reason and the trail (see Pivot
 below). A placeholder outcome.md is backfilled from the record instead, with the
 close's disposition and the `--outcome-summary` line as its summary. Also author

package/skills/intent-executing/SKILL.md

@@ -75,7 +75,7 @@ Apply the auto skill's risk rule to the executor's return and the diff: a matrix
 
 Whenever a review verdict returns - the plan review before code, or the post-execution review above - the lead appends a `Review` line: `ruby ~/.plastic/scripts/savepoint-note <intent_dir> --kind Review --text "<verdict, what changed>"` (intent 317, D17). This is the other half of what `report-screen delay` reads.
 
-**The D19 heading convention.** An action file's `## Delivered` row (in `outcome.md`) is proven by whichever `actions/ACTION_N.md` heading carries that row's label as a standalone token - `### Row A -` proves row A, `### S1 -` proves row S1. Write action-file section headings so the label they prove is unambiguous (never a substring another label could also match, like `A` inside `AB`); `report-screen delivered`'s Proven-by column renders `not recorded` when no heading matches.
+**The D19 heading convention.** An action file's `## Delivered` row (in `outcome.md`) is proven by the first `actions/ACTION_N.md` heading that carries that row's label as a standalone token AND owns the matrix table (322 D1r) - `### Row A -` with a table beneath it proves row A, `### S1 -` proves row S1; a heading that only names the label, with no table under it, is skipped. Write action-file section headings so the label they prove is unambiguous (never a substring another label could also match, like `A` inside `AB`); `report-screen delivered`'s Proven-by column renders `not recorded` when no heading owns a matching table and no matrix row cell carries the label either.
 
 ### Step 4: Update Intent and Complete
 Capture observations in `## Insights`. When ALL checklist items are checked:

package/templates/outcome.md

@@ -10,8 +10,11 @@ disposition: delivered|abandoned
 <!-- One row per thing delivered, in plain wording a reader recognizes, not
 an implementation summary; the technical detail belongs in ## Summary. Each
 row's label must appear as a standalone token in an actions/*.md heading
-(for example "### S1 - ..." proves row S1): that heading's matrix rows become
-the row's Proven-by cell on the delivered screen (intent 317 D19, 317a). -->
+that owns the matrix table (for example "### S1 - ..." with a table beneath
+it proves row S1); that heading's matrix rows become the row's Proven-by
+cell on the delivered screen (intent 317 D19, 317a, 322 D1r). A label with no
+owning heading falls back to a matrix row cell that carries it, when one
+under a heading named "matrix" exists (322 D3r). -->
 | Row | What |
 | --- | --- |
 | S1 | ... |