@warpgogol/forge 5.3.4 → 6.2.0

package/skills/fo/fo-review/SKILL.md

@@ -9,7 +9,7 @@ languagePolicy: ref(PREFERENCES.md)
 bindings:
   requires: [commands.validateRfc]
   optional: [paths.invariantsFile, paths.compassDocs]
-triggerPhrases: ["review this code diff", "check code against Forge standards", "fitness check on code changes"]
+triggerPhrases: ["проверим всё ли сделали правильно", "проверь изменения", "review this session", "review this code diff", "check code against Forge standards"]
 ---
 
 <!--
@@ -20,9 +20,24 @@ triggerPhrases: ["review this code diff", "check code against Forge standards",
 </non-goals>
 </MODULE_CONTRACT>
 <CHANGE_SUMMARY>
+  <item>RFC-1250: soft-block arbitration appends to the queue decision ledger
+  (open / stage: review) under orchestrated runs.</item>
   <item>RFC-1097: sweep — SKILL.md headers + classification fixes
 
 Sweep batch 1: add Compass v2 headers to 45 SKILL.md files (purpose derived from frontmatter description). Fix non-skill-markdown exclusion to check filename not workspace-relative path (packages/AGENTS.md escaped it). Add .coverage to ignoredDirs.</item>
+  <item>RFC-1247: triggerPhrases vocabulary sync — mined operator phrasing applied to this skill's trigger set.</item>
+  <item>RFC-1250: review wave — QUEUE-07 gates un-parked opens only, ledger binding checks, fail-closed loader
+
+REVIEW-RFC-1250-01 findings: QUEUE-07 no longer fires on parked entries
+(the park is the containment — a parked queue stays resumable and the
+decision window arbitrates it); loader fails open only on ENOENT —
+other read errors are QUEUE-01; ledger gains queue/id-stem binding
+(QUEUE-02), Q-N uniqueness (QUEUE-05), and QUEUE-08 hygiene warnings
+(missing answers, foreign doc ids); next excludes QUEUE-07-blocked
+items; top-level decision totals added. Orchestrator pre-flight treats
+QUEUE-07 as the window agenda — structural errors still stop the batch;
+maturation skips parked/deferred items; uncovered imperative ask sites
+gain collect riders (ADR code-trace, NC markers, audit-verdict guard).</item>
 </CHANGE_SUMMARY>
 -->
 
@@ -41,6 +56,25 @@ This skill reviews **code** — `.ts`, `.js`, `.tsx`, `.astro`, `.css`, `.json`,
 - For **RFCs, ADRs, architecture docs, or plans**, use `/fo-idea-audit` instead.
 - For **iterative fix-then-build-then-commit**, use `/fo-fix`.
 
+## Review modes: `inline` vs `independent`
+
+`fo-review` accepts an `independent` flag. **Default: `true` when invoked from a pipeline orchestrator (`fo-idea-i-just-want-to-see-the-result`, `fo-idea-implement`), `false` for ad-hoc in-session review.**
+
+In `independent` mode the reviewing pass executes in a **clean agent context** — a subagent dispatch where the platform provides one — carrying only artifacts:
+
+- the diff range or file list to review;
+- the rubric paths (this skill file, `_shared/fo-pipeline-conventions.md`);
+- the anchor paths (AGENTS.md files, DNA invariants file, relevant specs);
+- raw evidence (command output, failing logs, mechanical floor results).
+
+**Never pass the executor's session narrative, self-assessment, or settled conclusions** — passing them defeats the isolation the mode exists for (veil-of-ignorance contract, shared with the falsified-routes blind-spot pass). The dispatched reviewer's prompt contains artifact paths and the rubric, not the executor's story.
+
+Where the platform exposes no subagent primitive (or policy forbids dispatch), run an `isolated-inline` pass instead: re-derive conclusions only from the artifacts, deliberately ignoring the session's accumulated narrative, and record the fallback. **Never claim `subagent` isolation that did not happen** — the persisted report's `reviewer.isolation` field records the mode actually used (`subagent` | `isolated-inline` | `inline`), so independence is auditable rather than asserted.
+
+An executor that narrows the reviewer's inputs — passing a self-authored summary instead of artifact paths — commits a scope-narrowing violation, itself reportable as a `soft-block` on the review process.
+
+**Report persistence is the dispatcher's duty in `independent` mode.** A clean-context reviewer may be read-only and never writes files — it returns findings and verdict. The skill run that dispatched it performs steps 6–7 itself: it assembles the report, builds the YAML frontmatter (`reviewer.isolation` records the mode actually used), and writes the file to `docs/reviews/code/`. A persisted review report without the frontmatter block is a contract violation regardless of which side produced the prose.
+
 ## Process
 
 ### 1. Identify the diff
@@ -99,7 +133,7 @@ Read the context the diff claims to fit into:
 
 Do not read every file in the repo — only the standards relevant to the diff.
 
-### 4. Run the seven review axes
+### 4. Run the eight review axes
 
 For each axis, check every item. An item either **passes**, **fails** (specific finding with evidence), or is **not applicable** (state why). Skip N/A items silently — do not pad the report.
 
@@ -177,6 +211,15 @@ If the invariants file is absent or the optional binding is unresolvable, state
 - **Migration path**: existing apps' path to compliance is documented.
 - **Security / privacy**: if the diff touches user data, PII, or external services, it addresses GDPR/privacy and secret management. No cookies (`document.cookie`, `Set-Cookie`). Client-side persistence is `localStorage` only; server-side is `unstorage`.
 
+#### Axis H — Fracture inference
+
+Will this output collapse at the next step? Judge the diff not only for what it is, but for whether the _process that produced it_ is honest:
+
+- **Goal-closure authenticity** — claims of completion vs. verifiable evidence. A marked-done criterion whose checkable trace is absent or hand-waved is a fracture signal.
+- **Ordering-constraint compliance** — skipped preconditions: plan steps executed out of order, dependencies implemented after their dependents, gates bypassed to reach a green run.
+- **Unclosed-marking truthfulness** — deferred or open items actually declared as such; nothing silently dropped from the plan, todo list, or spec.
+- **State-transmission completeness** — would a fresh agent recover this work without the conversation? Checkpoints, persisted reports, and committed artifacts carry the state — not session memory.
+
 ### 5. Check spec compliance
 
 If an original request, spec, PRD, issue, or brief is available (from commit messages, linked issues, or session context), build a gap table:
@@ -199,7 +242,7 @@ Present the findings in this structure in `aiLanguage`. **Translate all labels,
 ```
 ## <Code Review in aiLanguage>: <diff range or file list>
 
-### Verdict: <Approved | Needs revision | Rejected>
+### Verdict: <Approved | Needs revision | Rejected> (blockLevel: <pass | warning | soft-block | hard-block>)
 
 <2-3 sentence justification grounded in the most serious findings.>
 
@@ -228,6 +271,9 @@ Present the findings in this structure in `aiLanguage`. **Translate all labels,
 ### Axis G — Blind spots
 <Findings or "No issues.">
 
+### Axis H — Fracture inference
+<Findings or "No issues.">
+
 ### Spec compliance
 
 <Gap table or "No spec available — skipped.">
@@ -239,11 +285,22 @@ Present the findings in this structure in `aiLanguage`. **Translate all labels,
 3. <Hard question.>
 ```
 
-**Verdict criteria:**
+**Verdict criteria (blocking model):**
+
+Every verdict carries a `blockLevel` — the blocking semantics downstream pipeline skills act on. `verdict` is retained and **derived** from it for backward compatibility (`fo-fix` consumes `verdict` unchanged):
+
+| `blockLevel` | `verdict` | Semantics |
+| --- | --- | --- |
+| `pass` | `approved` | Zero findings across all axes — no fracture signals |
+| `warning` | `needs-revision` | Findings recorded as tracked observations; they must be answered, and unresolved warnings at T3 escalate to `soft-block` |
+| `soft-block` | `needs-revision` + `escalation: operator` | Directional deviation or process violation — suspends the item for operator arbitration (queue mode: item parked, arbitration question appended to the decision ledger as `open`/`stage: review`/`parked: true`, batch continues) |
+| `hard-block` | `rejected` | Fundamental flaw — fix, then **full** re-review (not a delta on the flagged point) before the item may proceed to stamping |
+
+- **Approved (`pass`)** — zero findings across all eight axes. Any finding, no matter how minor or cosmetic, disqualifies Approved and forces Needs revision. The rationale: downstream agents treat Approved as a stop signal and stop reading the findings — so even a trivial finding left under Approved gets silently ignored. If there is anything to fix, the verdict must say so.
+- **Needs revision (`warning` | `soft-block`)** — one or more findings on any axis, regardless of severity. A one-line cosmetic rename is enough (`warning`). Escalate to `soft-block` when the deviation is directional or the review process itself was compromised (e.g. narrowed inputs). The agent must not downgrade to Approved based on severity — a finding is a finding.
+- **Rejected (`hard-block`)** — fundamental flaw: the diff contradicts a DNA invariant, introduces a backward compatibility layer, or bypasses the storage policy.
 
-- **Approved** — zero findings across all seven axes. Any finding, no matter how minor or cosmetic, disqualifies Approved and forces Needs revision. The rationale: downstream agents treat Approved as a stop signal and stop reading the findings — so even a trivial finding left under Approved gets silently ignored. If there is anything to fix, the verdict must say so.
-- **Needs revision** — one or more findings on any axis, regardless of severity. A one-line cosmetic rename is enough. The agent must not downgrade to Approved based on severity — a finding is a finding.
-- **Rejected** — fundamental flaw: the diff contradicts a DNA invariant, introduces a backward compatibility layer, or bypasses the storage policy.
+The `blockLevel` → pipeline semantics (full re-review on `hard-block`, queue parking on `soft-block`, warning escalation at T3) are declared in `_shared/fo-pipeline-conventions.md` §Review blocking semantics.
 
 ### 7. Persist the review
 
@@ -265,8 +322,12 @@ reviewId: REVIEW-CODE-<YYYY-MM-DD>-<NN>
 date: YYYY-MM-DD
 reviewer:
   skill: fo-review
+  isolation: <subagent | isolated-inline | inline>   # the isolation mode actually used
   model: <AI model identifier>
-verdict: <approved | needs-revision | rejected>
+blockLevel: <pass | warning | soft-block | hard-block>  # blocking semantics
+verdict: <approved | needs-revision | rejected>          # derived from blockLevel
+escalation: <none | operator>                            # set when blockLevel = soft-block
+observations: []                                          # tracked warnings carried to T3
 diffRange: <fixed-point>...HEAD
 filesReviewed:
   - <file path>

package/skills/fo/fo-session-retro/SKILL.md

@@ -9,7 +9,7 @@ languagePolicy: ref(PREFERENCES.md)
 bindings:
   requires: []
   optional: [paths.invariantsFile]
-triggerPhrases: ["session retrospective", "triage session discoveries", "Завершаем эту сессию", "End session", "/session-end"]
+triggerPhrases: ["завершаем", "протокол завершения", "Завершаем эту сессию", "session retrospective", "End session"]
 ---
 
 <!--
@@ -23,6 +23,7 @@ triggerPhrases: ["session retrospective", "triage session discoveries", "Зав
   <item>RFC-1097: sweep — SKILL.md headers + classification fixes
 
 Sweep batch 1: add Compass v2 headers to 45 SKILL.md files (purpose derived from frontmatter description). Fix non-skill-markdown exclusion to check filename not workspace-relative path (packages/AGENTS.md escaped it). Add .coverage to ignoredDirs.</item>
+  <item>RFC-1247: triggerPhrases vocabulary sync — mined operator phrasing applied to this skill's trigger set.</item>
 </CHANGE_SUMMARY>
 -->
 
@@ -85,7 +86,7 @@ The agent reconstructs the current session's conversation from its context windo
 3. Reconstruct the conversation from context — include every user message and assistant response you can recall from the current session, in chronological order. This is a best-effort reconstruction: the agent's context window is the source, not an external export tool.
 4. **Redact sensitive information** — remove API keys, passwords, PII, and secret values before writing. Replace with `<redacted>`.
 5. **Truncate very long tool outputs** — if a tool call produced thousands of lines of output, summarize it as `<tool output truncated, N lines>` in the content field. Keep the tool call name and key results.
-6. Write the file using `write_to_file` to `docs/sessions/.raw/<timestamp>-session.atif`.
+6. Write the file **atomically**: `write_to_file` to `docs/sessions/.raw/<timestamp>-session.atif.tmp`, then `mv` it to the same path without `.tmp` (rename is atomic). A parallel agent's `session.save` claims any `.atif` the moment it appears — this ordering guarantees it never sees a half-written transcript.
 
 ### 0c. Run session.save
 

package/skills/fo/fo-step-commit/SKILL.md

@@ -10,6 +10,7 @@ concerns: code-mutation
 dependsOn: ['my-preferences']
 languagePolicy: ref(PREFERENCES.md)
 triggerPhrases:
+  - "закоммитим"
   - "commit after request"
   - "auto-commit changes"
   - "step commit"
@@ -26,6 +27,7 @@ triggerPhrases:
   <item>RFC-1097: sweep — SKILL.md headers + classification fixes
 
 Sweep batch 1: add Compass v2 headers to 45 SKILL.md files (purpose derived from frontmatter description). Fix non-skill-markdown exclusion to check filename not workspace-relative path (packages/AGENTS.md escaped it). Add .coverage to ignoredDirs.</item>
+  <item>RFC-1247: triggerPhrases vocabulary sync — mined operator phrasing applied to this skill's trigger set.</item>
 </CHANGE_SUMMARY>
 -->
 

package/skills/shared/grilling/SKILL.md

@@ -22,11 +22,23 @@ knowledge:
   <item>RFC-1097: sweep — SKILL.md headers + classification fixes
 
 Sweep batch 1: add Compass v2 headers to 45 SKILL.md files (purpose derived from frontmatter description). Fix non-skill-markdown exclusion to check filename not workspace-relative path (packages/AGENTS.md escaped it). Add .coverage to ignoredDirs.</item>
+  <item>RFC-1250: two modes — interview (standalone, interactive) and emit
+  (orchestrated runs: questions land in the queue decision ledger with
+  recommended answers, no interview).</item>
 </CHANGE_SUMMARY>
 -->
 
 Before starting, read `PREFERENCES.md` at the repository root. If the file is missing or `aiLanguage` is unset, ask the operator once and create the file using the `my-preferences` skill semantics.
 
+## Modes
+
+Grilling runs in one of two modes — the caller selects:
+
+- **`interview`** (default — standalone, operator-invoked runs): the interactive behavior below, one question at a time.
+- **`emit`** (inside an orchestrator-driven queue run — `fo-idea-i-just-want-to-see-the-result` queue mode): never ask the operator. Generate the same questions you would have asked, climb the self-resolution ladder (`_shared/fo-pipeline-conventions.md` §Self-resolution ladder), and append each surviving question to the queue's decision ledger `docs/queues/<id>.decisions.yaml` as an `open` entry (`id: Q-N`, `doc`, `stage`, `question`, `resolutionPath`, `options` with `recommended: true` on your recommended answer, `status: open`). Branching questions are written conditionally ("if Q-3 resolves to X, then…"). The pipeline's decision window consumes the emitted entries.
+
+Mode trigger: `emit` activates only when the invoking skill passes a queue manifest / ledger path; otherwise `interview`.
+
 Read `learned-principles.md` (L2) at the start of each session to improve recommended answers. Apply only entries with `status: active`; skip entries with `status: stale`, `superseded`, or `archived`. Principles with `confirmations >= 3` may be applied autonomously — but re-evaluate if context changes.
 
 Interview me relentlessly about every aspect of this plan until we reach a shared understanding. Walk down each branch of the design tree, resolving dependencies between decisions one-by-one. For each question, provide your recommended answer.

package/skills/shared/writing-great-skills/GLOSSARY.md

@@ -58,6 +58,8 @@ A **user-invoked** skill whose job is to point at your other user-invoked skills
 
 _Avoid_: dispatcher, menu, registry, index, router procedure
 
+_Applied instance_: `fo-idea-i-just-want-to-see-the-result` is the forge pipeline's router skill — the operator's single front door. Its Preconditions carry an intent-routing table that maps non-pipeline intents (review, fix, session-end, commit, mission work, exploration) to their standing skills before document-id detection; pipeline intents flow through unchanged, and the escape hatches stay directly invocable.
+
 ### Granularity
 
 How finely you divide skills. Finer division spends one of the two loads: more **model-invoked** skills spend **context load** (more descriptions crowding the window and competing for attention); more **user-invoked** skills spend **cognitive load** (more for the human to remember and reach for). Two cuts guide the division. By **invocation**, split off a model-invoked skill where you have a distinct **leading word** to trigger it — a trigger word you actually use in your prompts. By **sequence**, split a run of **steps** where a step's **post-completion steps** need hiding, since isolating it in its own context clears what follows. Beware the reverse: merging sequences exposes each step's post-completion steps to what follows, inviting premature completion.

package/skills/shared/writing-great-skills/SKILL.md

@@ -19,6 +19,7 @@ languagePolicy: ref(PREFERENCES.md)
   <item>RFC-1097: sweep — SKILL.md headers + classification fixes
 
 Sweep batch 1: add Compass v2 headers to 45 SKILL.md files (purpose derived from frontmatter description). Fix non-skill-markdown exclusion to check filename not workspace-relative path (packages/AGENTS.md escaped it). Add .coverage to ignoredDirs.</item>
+  <item>RFC-1247: close RFC-1247 review r2 — CHANGE_SUMMARY items on six touched skills, fo-handoff in AGENTS enumeration, glossary applied-instance pointer, recorded per-skill phrase split</item>
 </CHANGE_SUMMARY>
 -->
 
@@ -37,7 +38,7 @@ Two choices, trading different costs:
 
 Pick model-invocation only when the agent must reach the skill on its own, or another skill must. If it only ever fires by hand, make it user-invoked and pay no context load.
 
-When user-invoked skills multiply past what you can remember, that piled-up cognitive load is cured by a **router skill**: one user-invoked skill that names the others and when to reach for each.
+When user-invoked skills multiply past what you can remember, that piled-up cognitive load is cured by a **router skill**: one user-invoked skill that names the others and when to reach for each. (Applied instance: `fo-idea-i-just-want-to-see-the-result` — see GLOSSARY.md.)
 
 ## Writing the description
 

package/src/cli-flags.ts

@@ -12,6 +12,10 @@ with `TypeError: targetId.toLowerCase is not a function`.</purpose>
 </MODULE_CONTRACT>
 <CHANGE_SUMMARY>
   <item>Standalone port of kernel argv resolution for the forge CLI (RFC-0260 lineage): strict KERNEL-FLAG-01/02/03 + KERNEL-ARG-01 diagnostics for schema-carrying commands, legacy heuristic parse (with KERNEL-ARG-01) for schema-less commands; repeated single-value string flags diagnose instead of silently promoting to an array that crashes handlers; indexOf-based inline-value split preserves values containing "=" that split("=", 2) silently truncated.</item>
+  <item>Session-retro 2026-10-08: string[] flags greedily consume consecutive
+bare tokens until the next --flag (`--files a b` → ["a","b"]), matching the
+kernel argv parser; bare positionals without a preceding string[] flag still
+emit KERNEL-ARG-01.</item>
 </CHANGE_SUMMARY>
 */
 
@@ -227,11 +231,25 @@ function resolveStrict(
       continue;
     }
 
-    const next = rawArgv[index + 1];
-    if (typeof next === "string" && !next.startsWith("--")) {
-      addFlagValue(flags, flagName, next);
-      index += 1;
-      continue;
+    // string[] flags consume every following bare token — mirrors the kernel's
+    // resolveCommandFlags: positional args are never valid (KERNEL-ARG-01),
+    // so `--files a b` unambiguously means the value list [a, b].
+    if (spec.kind === "string[]") {
+      let consumed = 0;
+      while (index + 1 < rawArgv.length && !rawArgv[index + 1]!.startsWith("--")) {
+        addFlagValue(flags, flagName, rawArgv[index + 1]!);
+        index += 1;
+        consumed += 1;
+      }
+      if (consumed > 0) continue;
+      // fall through to the missing-value diagnostic
+    } else {
+      const next = rawArgv[index + 1];
+      if (typeof next === "string" && !next.startsWith("--")) {
+        addFlagValue(flags, flagName, next);
+        index += 1;
+        continue;
+      }
     }
 
     diagnostics.push({

package/src/config/forge-config.ts

@@ -192,6 +192,8 @@ export const forgeConfigSchema = z
       packageManager: z.enum(["pnpm", "npm", "yarn", "bun", "none"]).default("pnpm"),
       // RFC-0640: optional domain field — absent means software-domain fallback
       domain: z.string().optional(),
+      /** RFC-1240: local consumer identity — absent means no consumer-aware spec filtering. */
+      consumer: z.string().optional(),
     }),
     paths: z.object({
       rfcsDir: z.string().default("docs/rfcs"),
@@ -234,6 +236,8 @@ export interface ForgeConfig {
     packageManager: "pnpm" | "npm" | "yarn" | "bun" | "none";
     /** RFC-0640: optional domain field — absent means software-domain fallback */
     domain?: string;
+    /** RFC-1240: local consumer identity — absent means no consumer-aware spec filtering */
+    consumer?: string;
   };
   paths: {
     rfcsDir: string;

package/src/onboarding/doctor.ts

@@ -8,8 +8,6 @@ Checks for forge.yaml, AGENTS.md, PREFERENCES.md, .agents/skills/, docs/rfcs/,
 </non-goals>
 </MODULE_CONTRACT>
 <CHANGE_SUMMARY>
-  <item>RFC-0704: added independent-version-packages check — validates that paths in independentVersionPackages exist and contain package.json.</item>
-  <item>RFC-0941: added pack-manifests advisory check — validates forge.plugin.yaml existence and schema for each declared skill pack.</item>
   <item>RFC-1097: step 6 — compass.migrate codemod run
 
 Mechanical v1 to v2 header migration across the workspace: 942 files rewritten — CHANGE_SUMMARY windows collapsed into history, forbidden v1 blocks stripped, KEY_DECISIONS seeded from @ai-invariant comments (5 files) or TODO placeholders (103 files), blocks reordered to canonical order.</item>
@@ -18,7 +16,8 @@ Mechanical v1 to v2 header migration across the workspace: 942 files rewritten
 Sweep batch 2: real KEY_DECISIONS on 10 files, expanded purposes (CONTRACT-02/PURPOSE-02), headers on mission/index + gen-upstreams, sanitizeItemText in summary.record (literal Compass tags corrupted history), excludedPaths for wrangler types, test-fixtures testPattern. forge+services now 0 diagnostics under --mode error.</item>
   <item>RFC-1224: preserve operator forge.yaml content on upgrade, promote adrImplementStamp binding</item>
   <item>RFC-1226: skills-unmanaged check — warn on SKILL.md-bearing dirs without .forge-managed marker</item>
-  <history>RFC-0391, RFC-0393, RFC-0524, RFC-0539, RFC-0540, RFC-0611, RFC-0640, RFC-0660, RFC-0661, RFC-0663, RFC-0664, RFC-0675, RFC-1224</history>
+  <item>RFC-1249: wire werkstatt.commands.validate into packages.check + retire CMD-OUTPUT debt</item>
+  <history>RFC-0391, RFC-0393, RFC-0524, RFC-0539, RFC-0540, RFC-0611, RFC-0640, RFC-0660, RFC-0661, RFC-0663, RFC-0664, RFC-0675, RFC-0704, RFC-0941, RFC-1224</history>
 </CHANGE_SUMMARY>
 */
 

package/src/onboarding/init.ts

@@ -461,9 +461,9 @@ export function runInit(
     }
   }
 
-  // 5. Copy neutral RFC and ADR templates into the project's docs directories.
-  // Templates are copied from the forge package so new projects can create
-  // RFCs and ADRs without falling back to the forge package's internal copy.
+  // 5. Copy neutral RFC, ADR, and plan templates into the project's docs
+  // directories. Templates are copied from the forge package so new projects
+  // can create documents without falling back to the package's internal copy.
   // Existing templates are never overwritten.
   const templatesToCopy = [
     {
@@ -476,6 +476,11 @@ export function runInit(
       destRel: `${config.paths.adrsDir}/adr-0000-template.md`,
       label: "docs/adrs/adr-0000-template.md",
     },
+    {
+      src: path.join(forgeRoot, "os", "plan", "plan-0000-template.md"),
+      destRel: `${config.paths.plansDir}/plan-0000-template.md`,
+      label: "docs/plans/plan-0000-template.md",
+    },
   ];
   for (const { src, destRel, label } of templatesToCopy) {
     const destPath = path.join(workspaceRoot, destRel);

package/src/pipeline-status.ts

@@ -19,9 +19,24 @@ os/ or kernel imports.</purpose>
   <item>RFC-1140: steps 1-4 — shared resolver, queue module, registration
 
 Extract pipeline-status derivation into packages/forge/src/pipeline-status.ts, refactor rfc.pipeline.status onto it, add os/queue module with queue.validate command, register in WORKSHOP_MODULE_MAP.forge + bin/cli.ts + package.json exports.</item>
+  <item>RFC-1250: decision-aware queue report — QueueItemReport gains kind +
+  decisions counts; `next` exclusion of parked/blocked items is computed by
+  the queue.validate caller (the resolver stays ledger-agnostic).</item>
   <item>RFC-1140: step 6 — cover shared resolver and queue.validate
 
 Add pipeline-status.test.ts (derivation matrix, order, next selection, ADR, skipped) and queue-validate.test.ts (schema errors, unknown/dup ids, id-filename mismatch, empty items, dependsOn warning, JSON shape). Fix queue derivation: pipelineStep is the stage after the last completed stage, not first incomplete — handles non-contiguous artifacts.</item>
+  <item>RFC-1250: review wave — QUEUE-07 gates un-parked opens only, ledger binding checks, fail-closed loader
+
+REVIEW-RFC-1250-01 findings: QUEUE-07 no longer fires on parked entries
+(the park is the containment — a parked queue stays resumable and the
+decision window arbitrates it); loader fails open only on ENOENT —
+other read errors are QUEUE-01; ledger gains queue/id-stem binding
+(QUEUE-02), Q-N uniqueness (QUEUE-05), and QUEUE-08 hygiene warnings
+(missing answers, foreign doc ids); next excludes QUEUE-07-blocked
+items; top-level decision totals added. Orchestrator pre-flight treats
+QUEUE-07 as the window agenda — structural errors still stop the batch;
+maturation skips parked/deferred items; uncovered imperative ask sites
+gain collect riders (ADR code-trace, NC markers, audit-verdict guard).</item>
 </CHANGE_SUMMARY>
 */
 
@@ -244,6 +259,10 @@ export interface QueueItemReport {
   status: QueueItemStatus;
   /** First incomplete pipeline stage — present only when in-progress. */
   pipelineStep?: PipelineStage;
+  /** Document kind — needed by queue.validate for QUEUE-07 (any non-terminal ADR is implementable). */
+  kind?: QueueDocumentKind;
+  /** Decision-ledger counts (RFC-1250) — present when the queue carries a sibling ledger. */
+  decisions?: { open: number; deferred: number; autoResolved: number };
 }
 
 /**
@@ -266,20 +285,20 @@ export async function deriveQueueItemStatus(
   const implementedAt = fm["implementedAt"] ? String(fm["implementedAt"]) : undefined;
 
   if (status === "implemented" || implementedAt) {
-    return { id: doc.id, status: "implemented" };
+    return { id: doc.id, status: "implemented", kind: doc.kind };
   }
   if (status === "rejected" || status === "superseded") {
-    return { id: doc.id, status: "skipped" };
+    return { id: doc.id, status: "skipped", kind: doc.kind };
   }
 
   // ADR pipeline is create → implement — no intermediate artifacts exist.
   if (doc.kind === "adr") {
-    return { id: doc.id, status: "pending" };
+    return { id: doc.id, status: "pending", kind: doc.kind };
   }
 
   // RFC accepted means the plan step is done by definition.
   if (status === "accepted") {
-    return { id: doc.id, status: "in-progress", pipelineStep: "implement" };
+    return { id: doc.id, status: "in-progress", pipelineStep: "implement", kind: doc.kind };
   }
 
   const enhancedAt = fm["enhancedAt"] ? String(fm["enhancedAt"]) : undefined;
@@ -302,13 +321,13 @@ export async function deriveQueueItemStatus(
     if (stages[i]!.done) lastDone = i;
   }
   if (lastDone === -1) {
-    return { id: doc.id, status: "pending" };
+    return { id: doc.id, status: "pending", kind: doc.kind };
   }
   const nextStage = stages[lastDone + 1];
   if (!nextStage) {
-    return { id: doc.id, status: "pending" };
+    return { id: doc.id, status: "pending", kind: doc.kind };
   }
-  return { id: doc.id, status: "in-progress", pipelineStep: nextStage.stage };
+  return { id: doc.id, status: "in-progress", pipelineStep: nextStage.stage, kind: doc.kind };
 }
 
 export interface QueueReport {
@@ -317,7 +336,12 @@ export interface QueueReport {
   next: string | null;
 }
 
-/** Derive the full queue report, preserving manifest order. */
+/**
+ * Derive the full queue report, preserving manifest order. `next` selects
+ * the first pending/in-progress item; callers that need ledger-aware
+ * exclusion (RFC-1250 parked/QUEUE-07-blocked items) re-filter the returned
+ * items — the resolver itself stays ledger-agnostic.
+ */
 export async function deriveQueueReport(
   workspaceRoot: string,
   itemIds: string[],

package/src/tests/cli-flags.test.ts

@@ -143,6 +143,26 @@ describe("resolveCliFlags — strict (schema-carrying) path", () => {
     expect(flags["files"]).toEqual(["a", "b"]);
     expect(errorRuleIds(diagnostics)).toEqual([]);
   });
+
+  test("string[] flag consumes consecutive bare tokens as a value list", () => {
+    const cmd = command({
+      files: { kind: "string[]", description: "Files." },
+      id: { kind: "string", description: "Id." },
+    });
+    const { flags, diagnostics } = resolveCliFlags(["--files", "a", "b", "c", "--id", "x"], cmd);
+    expect(flags["files"]).toEqual(["a", "b", "c"]);
+    expect(flags["id"]).toBe("x");
+    expect(errorRuleIds(diagnostics)).toEqual([]);
+  });
+
+  test("string[] flag with no value still emits KERNEL-FLAG-02", () => {
+    const cmd = command({
+      files: { kind: "string[]", description: "Files." },
+      json2: { kind: "boolean", description: "Switch." },
+    });
+    const { diagnostics } = resolveCliFlags(["--files", "--json2"], cmd);
+    expect(errorRuleIds(diagnostics)).toEqual(["KERNEL-FLAG-02"]);
+  });
 });
 
 describe("resolveCliFlags — legacy (schema-less) path", () => {

package/src/tests/cli-output.test.ts

@@ -8,6 +8,12 @@ renderNextSteps, renderIdeRecommendation, generateHelp.</purpose>
 </MODULE_CONTRACT>
 <CHANGE_SUMMARY>
   <item>RFC-0542: initial CLI output rendering tests.</item>
+  <item>RFC-1231: step 1 — rename supportsAllSites to acceptsAllFlag
+
+Mechanical sweep: the field only ever gated --all argv acceptance; fan-out
+follows the parsed selector. Guard renamed assertAllSitesAllowed ->
+assertAllFlagAccepted, message updated. 417 declaration sites + type
+surfaces (KernelCommandMetadata, ForgeCommandMetadata) in one atomic pass.</item>
 </CHANGE_SUMMARY>
 */
 
@@ -41,7 +47,7 @@ class MockRegistry implements CommandRegistry, ForgeModuleRegistry {
       provider: "workspace" as const,
       mutatesState: c.mutatesState,
       requiresNetwork: c.requiresNetwork,
-      supportsAllSites: c.supportsAllSites,
+      acceptsAllFlag: c.acceptsAllFlag,
       timeoutMs: c.timeoutMs,
       expectedDurationMs: c.expectedDurationMs,
       longRunning: c.longRunning,
@@ -112,7 +118,7 @@ describe("generateHelp", () => {
       name: "forge.init",
       description: "Deploy forge into a project.",
       scope: "workspace",
-      supportsAllSites: false,
+      acceptsAllFlag: false,
       flags: {},
       cacheable: false,
       execute: async () => ({ exitCode: 0 }),
@@ -121,7 +127,7 @@ describe("generateHelp", () => {
       name: "forge.doctor",
       description: "Diagnose forge state in an existing project.",
       scope: "workspace",
-      supportsAllSites: false,
+      acceptsAllFlag: false,
       flags: {},
       cacheable: false,
       execute: async () => ({ exitCode: 0 }),
@@ -138,7 +144,7 @@ describe("generateHelp", () => {
       name: "forge.doctor",
       description: "Diagnose forge state.",
       scope: "workspace",
-      supportsAllSites: false,
+      acceptsAllFlag: false,
       flags: {},
       cacheable: false,
       execute: async () => ({ exitCode: 0 }),
@@ -147,7 +153,7 @@ describe("generateHelp", () => {
       name: "forge.init",
       description: "Deploy forge.",
       scope: "workspace",
-      supportsAllSites: false,
+      acceptsAllFlag: false,
       flags: {},
       cacheable: false,
       execute: async () => ({ exitCode: 0 }),
@@ -167,7 +173,7 @@ describe("generateHelp", () => {
       name: "forge.init",
       description: "Deploy forge.",
       scope: "workspace",
-      supportsAllSites: false,
+      acceptsAllFlag: false,
       flags: {},
       cacheable: false,
       execute: async () => ({ exitCode: 0 }),
@@ -184,7 +190,7 @@ describe("generateHelp", () => {
       name: "forge.init",
       description: "Deploy forge.",
       scope: "workspace",
-      supportsAllSites: false,
+      acceptsAllFlag: false,
       flags: {},
       cacheable: false,
       execute: async () => ({ exitCode: 0 }),

package/src/tests/fixtures/agents-generate-business-before.txt

@@ -110,29 +110,29 @@ When the operator expresses an intent in natural language, the agent routes to t
 | "manage Compass headers", "annotate source files with Compass", "audit Compass module contracts"                                                          | `fo-compass-annotate`                   |
 | "design summit", "multi-persona review", "party mode"                                                                                                     | `fo-design-summit`                      |
 | "audit documentation sync", "update docs after code changes", "check AGENTS.md and README are in sync"                                                    | `fo-doc-audit`                          |
-| "explore this idea", "let me think about this", "what are the options for", "what if we"                                                                  | `fo-explore`                            |
+| "нам надо закрыть открытые вопросы", "explore this idea", "let me think about this", "what are the options for", "what if we"                             | `fo-explore`                            |
 | "extract DNA invariant", "discover architectural invariants", "formalize implicit architectural rules"                                                    | `fo-extract-dna`                        |
-| "fix issues from review", "apply review findings and fix", "iterative fix workflow for code"                                                              | `fo-fix`                                |
+| "исправим", "примени findings", "fix all", "fix issues from review", "apply review findings and fix"                                                      | `fo-fix`                                |
 | "create a handoff document", "compact conversation for next agent", "prepare handoff for another agent"                                                   | `fo-handoff`                            |
 | "harvest portable patterns from code", "extract reusable code pattern to forge", "port this pattern to forge"                                             | `fo-harvest`                            |
 | "I have an idea for a change", "analyze this idea and route it", "decompose this feature idea", "does this need an RFC", "should I write an ADR for this" | `fo-idea`                               |
 | "audit this RFC", "check RFC for ecosystem fit", "review RFC against DNA and forward-only rules"                                                          | `fo-idea-audit`                         |
 | "record this architectural decision", "create an ADR", "document a local technical decision"                                                              | `fo-idea-create-adr`                    |
-| "draft an RFC", "create a full RFC", "scaffold an RFC from template"                                                                                      | `fo-idea-create-rfc`                    |
+| "подготовим RFC", "draft an RFC", "create a full RFC", "scaffold an RFC from template"                                                                    | `fo-idea-create-rfc`                    |
 | "enhance this RFC", "fix audit findings in RFC", "improve RFC based on audit"                                                                             | `fo-idea-enhance`                       |
 | "I just want to see the plan", "plan this feature without implementing", "run idea to plan pipeline"                                                      | `fo-idea-i-just-want-to-see-the-plan`   |
-| "I just want to see the result", "run the full pipeline automatically", "implement this end-to-end without pauses"                                        | `fo-idea-i-just-want-to-see-the-result` |
+| "по полному пайплайну", "на результат", "реализуй RFC", "I just want to see the result", "implement this end-to-end without pauses"                       | `fo-idea-i-just-want-to-see-the-result` |
 | "implement this RFC", "execute the implementation plan", "realize this RFC end-to-end"                                                                    | `fo-idea-implement`                     |
 | "plan the implementation for this RFC", "create implementation plan", "map affected artifacts and draft steps"                                            | `fo-idea-plan`                          |
 | "show RFC and ADR status", "what is the status of this RFC", "list RFCs by status"                                                                        | `fo-idea-status`                        |
 | "distill knowledge", "compact skill knowledge", "knowledge lifecycle", "promote fix patterns"                                                             | `fo-knowledge-distill`                  |
 | "sync memory from codex", "import external agent knowledge", "recall sessions from other tools", "sync memory from claude code"                           | `fo-memory-sync`                        |
 | "I found a bug", "file a GitHub issue for this bug", "report a bug conversationally", "interactive QA session"                                            | `fo-qa`                                 |
-| "review this code diff", "check code against Forge standards", "fitness check on code changes"                                                            | `fo-review`                             |
-| "session retrospective", "triage session discoveries", "Завершаем эту сессию", "End session", "/session-end"                                              | `fo-session-retro`                      |
+| "проверим всё ли сделали правильно", "проверь изменения", "review this session", "review this code diff", "check code against Forge standards"            | `fo-review`                             |
+| "завершаем", "протокол завершения", "Завершаем эту сессию", "session retrospective", "End session"                                                        | `fo-session-retro`                      |
 | "save this session", "enhance session transcript with annotations", "save session with quality checks"                                                    | `fo-session-save`                       |
 | "ingest external specification", "vendor spec package into docs", "author spec skeleton"                                                                  | `fo-spec-ingest`                        |
-| "commit after request", "auto-commit changes", "step commit"                                                                                              | `fo-step-commit`                        |
+| "закоммитим", "commit after request", "auto-commit changes", "step commit"                                                                                | `fo-step-commit`                        |
 | "triage this issue", "categorize incoming bug report", "triage external pull request", "process feature request"                                          | `fo-triage`                             |
 
 The agent uses judgment to calibrate routing — minor edits (typo fixes, small CSS changes) do not require skill invocation, while significant changes (new features, architectural decisions) do.