squadrant 0.27.1 → 0.28.1

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "squadrant",
   "packageManager": "pnpm@10.30.3",
-  "version": "0.27.1",
+  "version": "0.28.1",
   "description": "Multi-project orchestration for your coding agents (Claude, Codex, opencode, Gemini)",
   "type": "module",
   "bin": {

package/plugin/skills/knowledge-extract/SKILL.md

@@ -34,6 +34,8 @@ Works from any agent: it is plain CLI plus a JSON file.
    `squadrant knowledge apply <kb> candidates.json`
 
    List a ref in `complete` **only** when this file covers every section of that source (no carried sections). Rules from a `complete` source that no candidate matches are marked `stale`; listing a partially-covered source would wrongly stale its rules.
+   A source marked `review: required` in `sources.yaml` never produces live rules: its new rules land in `_proposed/` and wait for the operator (a same-meaning candidate for an existing rule still merges). Extract it exactly the same way.
+   If the KB has an `errata.yaml`, candidates that hit a stale passage come back as rejected with reason `errata:<id>`. That is expected, not a failure: do not re-emit or rephrase them. An "errata <id> … quote no longer found" line means the raw file changed; tell the captain, do not edit `errata.yaml` yourself.
 5. **Report** the apply output: created / merged / proposed / rejected counts. If it says a source is flagged "conversion likely poor, try docling", tell the captain; do not retry the same conversion.
 
 ## Rules

package/plugin/skills/knowledge-review/SKILL.md

@@ -29,11 +29,16 @@ You are the **reviewer** for one knowledge base pass. Code enforces every hard r
 5. **Apply.** `squadrant knowledge review <kb> --apply decisions.json`.
 6. **Close.** `squadrant knowledge reconcile <kb> [--full] --finish` writes REPORT.md, advances the schedule and sends the captain a one-line count.
 
+## Stale rules from a removed source
+
+`squadrant knowledge sources <kb> --remove <path>` can leave rules with no source (status `stale`, empty `sources`). They appear in the packet's `stale` list like any other. Retire (`approve`) one only if its statement is still unsupported; a `reject` (keep) on a source-less rule always escalates (`no-source`), and the operator cannot keep it either: they must add a source to the rule or retire it.
+
 ## Always escalated (code enforces this, whatever your confidence)
 
 - two `company`-priority sources in conflict
 - retiring a `must` or `must-not` rule
 - anything you flag, and any code-vs-doc conflict where the code is newer
+- any proposal from a source marked `review: required` in `sources.yaml` (escalated as `review-required`, at any confidence). You may still decide and justify it; the operator makes the call.
 
 ## Rules
 

package/templates/crew.claude.md

@@ -43,6 +43,7 @@ Your captain learns you are done from an **explicit signal**, not from your CLI
 1. Commit your work.
 2. Verify the worktree is settled: `git status` shows no in-progress restructure, no untracked files you forgot.
 3. Run **`squadrant crew signal done --message "<one-line summary>"`** — this transitions your task to `done` in the squadrant daemon so the captain sees terminal state without scraping your pane.
+   If you applied any knowledge-base rules, end the message with `Rules: <id>, <id>` (leave it out when none applied). The signal records those ids as citations, and it also picks up rule ids named in your branch's commit messages.
 4. Then (and only then) exit your CLI.
 
 If you need the captain's input or a decision and you will wait for it, do NOT just ask in prose — run this BEFORE ending your turn, then wait:

package/templates/crew.generic.md

@@ -39,6 +39,7 @@ Your captain learns you are done from an **explicit signal**, not from your CLI
 1. Commit your work.
 2. Verify the worktree is settled (`git status` clean).
 3. Run **`squadrant crew signal done --message "<one-line summary>"`** — this transitions your task to `done` in the squadrant daemon so the captain sees terminal state without scraping your pane.
+   If you applied any knowledge-base rules, end the message with `Rules: <id>, <id>` (leave it out when none applied). The signal records those ids as citations, and it also picks up rule ids named in your branch's commit messages.
 4. Then (and only then) exit your CLI.
 
 If you need the captain's input or a decision and you will wait for it, do NOT just ask in prose — run `squadrant crew signal blocked --question "<the question>"` BEFORE ending your turn, then wait. Asking conversationally alone does not notify the captain; the explicit signal is what surfaces your question as CREW BLOCKED. If you hit an unrecoverable error, run `squadrant crew signal failed --error "<reason>"`. The signal verb reads `SQUADRANT_CREW_TASK_ID` and `SQUADRANT_CREW_PROJECT` from your environment — both are set automatically by your spawn.

package/templates/crew.opencode.md

@@ -39,6 +39,7 @@ Your captain learns you are done from an **explicit signal**, not from your CLI
 1. Commit your work.
 2. Verify the worktree is settled (`git status` clean).
 3. Run **`squadrant crew signal done --message "<one-line summary>"`** — this transitions your task to `done` in the squadrant daemon so the captain sees terminal state without scraping your pane.
+   If you applied any knowledge-base rules, end the message with `Rules: <id>, <id>` (leave it out when none applied). The signal records those ids as citations, and it also picks up rule ids named in your branch's commit messages.
 4. Then (and only then) exit your CLI.
 
 If you need the captain's input or a decision and you will wait for it, do NOT just ask in prose — run `squadrant crew signal blocked --question "<the question>"` BEFORE ending your turn, then wait. Asking conversationally alone does not notify the captain; the explicit signal is what surfaces your question as CREW BLOCKED. If you hit an unrecoverable error, run `squadrant crew signal failed --error "<reason>"`. The signal verb reads `SQUADRANT_CREW_TASK_ID` and `SQUADRANT_CREW_PROJECT` from your environment — both are set automatically by your spawn.