acstack 0.54.0 → 0.54.2

package/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "acstack",
   "description": "Agentic coding stack where planning grows only as far as needed: a map of decisions, tasks, checks, and handoffs behind a pluggable tracker.",
-  "version": "0.54.0",
+  "version": "0.54.2",
   "author": {
     "name": "ac8318740"
   },

package/agents/codex/frontend-verifier.toml

@@ -363,17 +363,21 @@ Do NOT kill the browser if you connected to an existing one. In `remote` mode th
 
 Use the fewest clear words that preserve all necessary information.
 
-## Answer the reader's question
-
-- Lead with the answer, recommendation, or result the reader needs
-- Give enough context for the reader to understand and act
-    - A short reply can be a direct sentence or a few bullets
-    - Add context, a problem statement, or a solution section only when the reader needs it
-- Match detail to the audience
-    - A human needs the facts that change a decision or next action
-    - An agent handoff needs every constraint required to continue correctly
-    - A durable document must make sense to someone outside the original conversation
-- Preserve necessary qualifications, evidence, errors, security warnings, accessibility requirements, and destructive-action confirmations
+## Fit the answer to the audience
+
+- Start with what the reader knows, what they do not know, and what they need from this answer
+    - Lead with the answer, recommendation, or result they need
+    - Include only the context needed to understand it and act; repeat known information only when necessary to connect the new information
+    - Omit a detail only when it does not affect the reader's understanding, decision, or next action
+    - If unsure whether a detail matters, include its essential point briefly rather than relying on the reader to ask
+- When reporting information to the user, be extremely concise and sacrifice grammar for sake of concision
+    - A headline or three-word answer is enough when it fully answers the question
+    - Use fragments freely; skip introductions, recaps, and supporting detail the user does not need
+    - Shorten wording, not meaning; keep conditions and ownership clear
+- Match completeness to the audience, not a length target
+    - An agent handoff needs every detail required to continue correctly, without padding
+    - A durable document needs enough context and precise wording to stand alone for its intended reader; chat's grammar shortcuts do not apply
+- Preserve necessary qualifications, evidence, errors, security warnings, accessibility requirements, and destructive-action confirmations; concision never overrides required disclosures
 - Separate the current answer from decision history
     - State what applies now before explaining how the decision changed
 
@@ -405,7 +409,7 @@ Use the fewest clear words that preserve all necessary information.
 
 ## Write in plain language
 
-- Prefer common, concrete words and natural word order
+- Prefer common, concrete words; use natural word order when it helps understanding
     - Keep necessary technical terms and define unfamiliar abbreviations
     - Cut grand claims, filler, repeated points, and metaphors the reader must decode
     - Use examples when they explain a point faster than an abstract description
@@ -417,20 +421,24 @@ Use the fewest clear words that preserve all necessary information.
     - Prefer active voice, present-tense descriptions, and direct instructions
     - Keep passive voice when the actor is unknown or irrelevant
 - State claims at the strength supported by evidence
-    - Name sources, checks run, results, and remaining uncertainty
+    - Include sources, checks run, results, and uncertainty when the reader needs them to judge the claim or act
+    - Keep verification rigorous even when its supporting detail stays out of the report
     - Explain an important distinction, including what something does not do, when the reader needs it
 - Use sentence-case headings and restrained emphasis
-- Use straight quotes, the Oxford comma, and three periods for an ellipsis
-- Use a period, parentheses, or a spaced en dash instead of an em dash
+- Use straight quotes and three periods for an ellipsis; use the Oxford comma in durable prose
+- Prefer parentheses over spaced en dashes for asides; use a period for a separate thought, never an em dash
+    - Use short parenthetical clarifications or examples (e.g., a concrete input) when they make something complex or ambiguous easier to understand
 - Carry meaning in words, not emoji or color alone
 - Format Markdown so the reader sees the intended grouping
     - Indent nested bullets four spaces per level and leave a blank line before a list
-    - Use parallel grammar and consistent punctuation within a list
+    - Keep list items parallel in meaning; in durable prose, also use parallel grammar and consistent punctuation
     - Short bullet fragments need no final period
 
 ## Before you send
 
-- Can the reader find the answer without reading every detail?
+- Does this give the reader exactly what they need, given what they already know?
+- Can a headline alone answer the question? If so, stop there.
+- Have you removed unnecessary detail without hiding anything that could change the reader's understanding, decision, or next action?
 - Does every level summarize the detail below it?
 - Do siblings answer the same question at the same level?
 - Can the reader follow the same names from overview to detail?

package/agents/codex/task-checker.toml

@@ -81,17 +81,21 @@ Never present a focused PASS as completion of the whole effort.
 
 Use the fewest clear words that preserve all necessary information.
 
-## Answer the reader's question
-
-- Lead with the answer, recommendation, or result the reader needs
-- Give enough context for the reader to understand and act
-    - A short reply can be a direct sentence or a few bullets
-    - Add context, a problem statement, or a solution section only when the reader needs it
-- Match detail to the audience
-    - A human needs the facts that change a decision or next action
-    - An agent handoff needs every constraint required to continue correctly
-    - A durable document must make sense to someone outside the original conversation
-- Preserve necessary qualifications, evidence, errors, security warnings, accessibility requirements, and destructive-action confirmations
+## Fit the answer to the audience
+
+- Start with what the reader knows, what they do not know, and what they need from this answer
+    - Lead with the answer, recommendation, or result they need
+    - Include only the context needed to understand it and act; repeat known information only when necessary to connect the new information
+    - Omit a detail only when it does not affect the reader's understanding, decision, or next action
+    - If unsure whether a detail matters, include its essential point briefly rather than relying on the reader to ask
+- When reporting information to the user, be extremely concise and sacrifice grammar for sake of concision
+    - A headline or three-word answer is enough when it fully answers the question
+    - Use fragments freely; skip introductions, recaps, and supporting detail the user does not need
+    - Shorten wording, not meaning; keep conditions and ownership clear
+- Match completeness to the audience, not a length target
+    - An agent handoff needs every detail required to continue correctly, without padding
+    - A durable document needs enough context and precise wording to stand alone for its intended reader; chat's grammar shortcuts do not apply
+- Preserve necessary qualifications, evidence, errors, security warnings, accessibility requirements, and destructive-action confirmations; concision never overrides required disclosures
 - Separate the current answer from decision history
     - State what applies now before explaining how the decision changed
 
@@ -123,7 +127,7 @@ Use the fewest clear words that preserve all necessary information.
 
 ## Write in plain language
 
-- Prefer common, concrete words and natural word order
+- Prefer common, concrete words; use natural word order when it helps understanding
     - Keep necessary technical terms and define unfamiliar abbreviations
     - Cut grand claims, filler, repeated points, and metaphors the reader must decode
     - Use examples when they explain a point faster than an abstract description
@@ -135,20 +139,24 @@ Use the fewest clear words that preserve all necessary information.
     - Prefer active voice, present-tense descriptions, and direct instructions
     - Keep passive voice when the actor is unknown or irrelevant
 - State claims at the strength supported by evidence
-    - Name sources, checks run, results, and remaining uncertainty
+    - Include sources, checks run, results, and uncertainty when the reader needs them to judge the claim or act
+    - Keep verification rigorous even when its supporting detail stays out of the report
     - Explain an important distinction, including what something does not do, when the reader needs it
 - Use sentence-case headings and restrained emphasis
-- Use straight quotes, the Oxford comma, and three periods for an ellipsis
-- Use a period, parentheses, or a spaced en dash instead of an em dash
+- Use straight quotes and three periods for an ellipsis; use the Oxford comma in durable prose
+- Prefer parentheses over spaced en dashes for asides; use a period for a separate thought, never an em dash
+    - Use short parenthetical clarifications or examples (e.g., a concrete input) when they make something complex or ambiguous easier to understand
 - Carry meaning in words, not emoji or color alone
 - Format Markdown so the reader sees the intended grouping
     - Indent nested bullets four spaces per level and leave a blank line before a list
-    - Use parallel grammar and consistent punctuation within a list
+    - Keep list items parallel in meaning; in durable prose, also use parallel grammar and consistent punctuation
     - Short bullet fragments need no final period
 
 ## Before you send
 
-- Can the reader find the answer without reading every detail?
+- Does this give the reader exactly what they need, given what they already know?
+- Can a headline alone answer the question? If so, stop there.
+- Have you removed unnecessary detail without hiding anything that could change the reader's understanding, decision, or next action?
 - Does every level summarize the detail below it?
 - Do siblings answer the same question at the same level?
 - Can the reader follow the same names from overview to detail?

package/agents/codex/task-executor.toml

@@ -94,17 +94,21 @@ Say what stopped you.
 
 Use the fewest clear words that preserve all necessary information.
 
-## Answer the reader's question
-
-- Lead with the answer, recommendation, or result the reader needs
-- Give enough context for the reader to understand and act
-    - A short reply can be a direct sentence or a few bullets
-    - Add context, a problem statement, or a solution section only when the reader needs it
-- Match detail to the audience
-    - A human needs the facts that change a decision or next action
-    - An agent handoff needs every constraint required to continue correctly
-    - A durable document must make sense to someone outside the original conversation
-- Preserve necessary qualifications, evidence, errors, security warnings, accessibility requirements, and destructive-action confirmations
+## Fit the answer to the audience
+
+- Start with what the reader knows, what they do not know, and what they need from this answer
+    - Lead with the answer, recommendation, or result they need
+    - Include only the context needed to understand it and act; repeat known information only when necessary to connect the new information
+    - Omit a detail only when it does not affect the reader's understanding, decision, or next action
+    - If unsure whether a detail matters, include its essential point briefly rather than relying on the reader to ask
+- When reporting information to the user, be extremely concise and sacrifice grammar for sake of concision
+    - A headline or three-word answer is enough when it fully answers the question
+    - Use fragments freely; skip introductions, recaps, and supporting detail the user does not need
+    - Shorten wording, not meaning; keep conditions and ownership clear
+- Match completeness to the audience, not a length target
+    - An agent handoff needs every detail required to continue correctly, without padding
+    - A durable document needs enough context and precise wording to stand alone for its intended reader; chat's grammar shortcuts do not apply
+- Preserve necessary qualifications, evidence, errors, security warnings, accessibility requirements, and destructive-action confirmations; concision never overrides required disclosures
 - Separate the current answer from decision history
     - State what applies now before explaining how the decision changed
 
@@ -136,7 +140,7 @@ Use the fewest clear words that preserve all necessary information.
 
 ## Write in plain language
 
-- Prefer common, concrete words and natural word order
+- Prefer common, concrete words; use natural word order when it helps understanding
     - Keep necessary technical terms and define unfamiliar abbreviations
     - Cut grand claims, filler, repeated points, and metaphors the reader must decode
     - Use examples when they explain a point faster than an abstract description
@@ -148,20 +152,24 @@ Use the fewest clear words that preserve all necessary information.
     - Prefer active voice, present-tense descriptions, and direct instructions
     - Keep passive voice when the actor is unknown or irrelevant
 - State claims at the strength supported by evidence
-    - Name sources, checks run, results, and remaining uncertainty
+    - Include sources, checks run, results, and uncertainty when the reader needs them to judge the claim or act
+    - Keep verification rigorous even when its supporting detail stays out of the report
     - Explain an important distinction, including what something does not do, when the reader needs it
 - Use sentence-case headings and restrained emphasis
-- Use straight quotes, the Oxford comma, and three periods for an ellipsis
-- Use a period, parentheses, or a spaced en dash instead of an em dash
+- Use straight quotes and three periods for an ellipsis; use the Oxford comma in durable prose
+- Prefer parentheses over spaced en dashes for asides; use a period for a separate thought, never an em dash
+    - Use short parenthetical clarifications or examples (e.g., a concrete input) when they make something complex or ambiguous easier to understand
 - Carry meaning in words, not emoji or color alone
 - Format Markdown so the reader sees the intended grouping
     - Indent nested bullets four spaces per level and leave a blank line before a list
-    - Use parallel grammar and consistent punctuation within a list
+    - Keep list items parallel in meaning; in durable prose, also use parallel grammar and consistent punctuation
     - Short bullet fragments need no final period
 
 ## Before you send
 
-- Can the reader find the answer without reading every detail?
+- Does this give the reader exactly what they need, given what they already know?
+- Can a headline alone answer the question? If so, stop there.
+- Have you removed unnecessary detail without hiding anything that could change the reader's understanding, decision, or next action?
 - Does every level summarize the detail below it?
 - Do siblings answer the same question at the same level?
 - Can the reader follow the same names from overview to detail?

package/agents/codex/test-writer.toml

@@ -144,17 +144,21 @@ When complete, report:
 
 Use the fewest clear words that preserve all necessary information.
 
-## Answer the reader's question
-
-- Lead with the answer, recommendation, or result the reader needs
-- Give enough context for the reader to understand and act
-    - A short reply can be a direct sentence or a few bullets
-    - Add context, a problem statement, or a solution section only when the reader needs it
-- Match detail to the audience
-    - A human needs the facts that change a decision or next action
-    - An agent handoff needs every constraint required to continue correctly
-    - A durable document must make sense to someone outside the original conversation
-- Preserve necessary qualifications, evidence, errors, security warnings, accessibility requirements, and destructive-action confirmations
+## Fit the answer to the audience
+
+- Start with what the reader knows, what they do not know, and what they need from this answer
+    - Lead with the answer, recommendation, or result they need
+    - Include only the context needed to understand it and act; repeat known information only when necessary to connect the new information
+    - Omit a detail only when it does not affect the reader's understanding, decision, or next action
+    - If unsure whether a detail matters, include its essential point briefly rather than relying on the reader to ask
+- When reporting information to the user, be extremely concise and sacrifice grammar for sake of concision
+    - A headline or three-word answer is enough when it fully answers the question
+    - Use fragments freely; skip introductions, recaps, and supporting detail the user does not need
+    - Shorten wording, not meaning; keep conditions and ownership clear
+- Match completeness to the audience, not a length target
+    - An agent handoff needs every detail required to continue correctly, without padding
+    - A durable document needs enough context and precise wording to stand alone for its intended reader; chat's grammar shortcuts do not apply
+- Preserve necessary qualifications, evidence, errors, security warnings, accessibility requirements, and destructive-action confirmations; concision never overrides required disclosures
 - Separate the current answer from decision history
     - State what applies now before explaining how the decision changed
 
@@ -186,7 +190,7 @@ Use the fewest clear words that preserve all necessary information.
 
 ## Write in plain language
 
-- Prefer common, concrete words and natural word order
+- Prefer common, concrete words; use natural word order when it helps understanding
     - Keep necessary technical terms and define unfamiliar abbreviations
     - Cut grand claims, filler, repeated points, and metaphors the reader must decode
     - Use examples when they explain a point faster than an abstract description
@@ -198,20 +202,24 @@ Use the fewest clear words that preserve all necessary information.
     - Prefer active voice, present-tense descriptions, and direct instructions
     - Keep passive voice when the actor is unknown or irrelevant
 - State claims at the strength supported by evidence
-    - Name sources, checks run, results, and remaining uncertainty
+    - Include sources, checks run, results, and uncertainty when the reader needs them to judge the claim or act
+    - Keep verification rigorous even when its supporting detail stays out of the report
     - Explain an important distinction, including what something does not do, when the reader needs it
 - Use sentence-case headings and restrained emphasis
-- Use straight quotes, the Oxford comma, and three periods for an ellipsis
-- Use a period, parentheses, or a spaced en dash instead of an em dash
+- Use straight quotes and three periods for an ellipsis; use the Oxford comma in durable prose
+- Prefer parentheses over spaced en dashes for asides; use a period for a separate thought, never an em dash
+    - Use short parenthetical clarifications or examples (e.g., a concrete input) when they make something complex or ambiguous easier to understand
 - Carry meaning in words, not emoji or color alone
 - Format Markdown so the reader sees the intended grouping
     - Indent nested bullets four spaces per level and leave a blank line before a list
-    - Use parallel grammar and consistent punctuation within a list
+    - Keep list items parallel in meaning; in durable prose, also use parallel grammar and consistent punctuation
     - Short bullet fragments need no final period
 
 ## Before you send
 
-- Can the reader find the answer without reading every detail?
+- Does this give the reader exactly what they need, given what they already know?
+- Can a headline alone answer the question? If so, stop there.
+- Have you removed unnecessary detail without hiding anything that could change the reader's understanding, decision, or next action?
 - Does every level summarize the detail below it?
 - Do siblings answer the same question at the same level?
 - Can the reader follow the same names from overview to detail?

package/cli/dist/index.js

@@ -20275,12 +20275,12 @@ function openDesignLifecycle(root, entry, reviewFile) {
     const staleRendered = doc.sourceRevision !== rendered.sourceRevision;
     const inputs = designMapInputs(root, doc, entry);
     const feedbackPath = reviewFile ? resolve6(reviewFile) : review.reviewPath;
-    const latestReceipts = new Map(saved.lifecycle?.reconciliations.map((receipt) => [resolve6(root, receipt.reviewPath), receipt]));
+    const latestReceipts = new Map(saved.lifecycle?.reconciliations.map((receipt) => [historyPath(root, receipt.reviewPath), receipt]));
     const histories = readDesignReviewHistories(root, doc.id);
     histories.set(review.reviewPath, saved);
     const obligations = /* @__PURE__ */ new Set();
     for (const [path, snapshot] of histories) {
-      const receipts = new Map(snapshot.lifecycle?.reconciliations.map((receipt) => [resolve6(root, receipt.reviewPath), receipt]));
+      const receipts = new Map(snapshot.lifecycle?.reconciliations.map((receipt) => [historyPath(root, receipt.reviewPath), receipt]));
       for (const [selected, receipt] of receipts) {
         if (selected !== path || snapshot.annotations.length || receipt.decisions.some((decision) => decision.outcome === "needs-human")) obligations.add(selected);
       }
@@ -20293,24 +20293,21 @@ function openDesignLifecycle(root, entry, reviewFile) {
       return { path, snapshot, receipt, fresh };
     });
     const feedback = scopes.find((scope) => scope.path === feedbackPath).snapshot;
-    const tuple = {
-      sourceRevision: doc.sourceRevision,
-      reviewRevision: feedback.revision,
-      mapInputsDigest: inputs.mapInputsDigest,
-      commentsDigest: digest(scopes.map(({ path, snapshot }) => ({
-        path: relative4(root, path).split(sep).join("/"),
-        packVersion: snapshot.packVersion,
-        revision: snapshot.revision,
-        annotations: snapshot.annotations
-      })))
-    };
+    const commentsDigest = (prefix) => digest(scopes.map(({ path, snapshot }) => ({
+      path: prefix + relative4(root, path).split(sep).join("/"),
+      packVersion: snapshot.packVersion,
+      revision: snapshot.revision,
+      annotations: snapshot.annotations
+    })));
+    const tuple = { sourceRevision: doc.sourceRevision, reviewRevision: feedback.revision, mapInputsDigest: inputs.mapInputsDigest, commentsDigest: commentsDigest("") };
+    const legacyTuple = { ...tuple, commentsDigest: commentsDigest(LEGACY_PREFIX) };
     const unsettled = scopes.find((scope) => (obligations.has(scope.path) || scope.receipt || scope.snapshot.annotations.length) && (!scope.fresh || scope.receipt?.decisions.some((decision) => decision.outcome === "needs-human")));
     let reason;
     if (staleRendered) reason = "Authored source changed. Reopen this revision before reviewing.";
     else if (inputs.blockingQuestions.length) reason = "Unresolved design decisions";
     else if (unsettled) reason = unsettled.fresh ? "Reconciliation needs a human decision" : "Feedback and contributions need explicit reconciliation";
     else if (inputs.contributions.length && !scopes.some((scope) => scope.fresh)) reason = "Feedback and contributions need explicit reconciliation";
-    const approved = saved.lifecycle?.approvals.some((item) => sameTuple(item, tuple)) ?? false;
+    const approved = saved.lifecycle?.approvals.some((item) => sameTuple(item, tuple) || sameTuple(item, legacyTuple)) ?? false;
     return {
       ...tuple,
       planning: doc.planning ?? null,
@@ -20381,9 +20378,13 @@ function openDesignLifecycle(root, entry, reviewFile) {
     })
   };
 }
+function historyPath(root, reviewPath) {
+  return resolve6(root, reviewPath.startsWith(LEGACY_PREFIX) ? reviewPath.slice(LEGACY_PREFIX.length) : reviewPath);
+}
 function sameTuple(a, b) {
   return a.sourceRevision === b.sourceRevision && a.reviewRevision === b.reviewRevision && a.commentsDigest === b.commentsDigest && a.mapInputsDigest === b.mapInputsDigest;
 }
+var LEGACY_PREFIX;
 var init_design_lifecycle = __esm({
   "src/lib/design-lifecycle.ts"() {
     "use strict";
@@ -20392,6 +20393,7 @@ var init_design_lifecycle = __esm({
     init_design_map();
     init_design_review();
     init_review_server();
+    LEGACY_PREFIX = ".acstack/";
   }
 });