@fro.bot/systematic 3.14.1 → 3.14.3

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@fro.bot/systematic",
-  "version": "3.14.1",
+  "version": "3.14.3",
   "description": "Compound-engineering loops for OpenCode, Pi, and Claude Code",
   "type": "module",
   "homepage": "https://fro.bot/systematic",
@@ -95,8 +95,8 @@
   "devDependencies": {
     "@biomejs/biome": "2.5.9",
     "@earendil-works/pi-coding-agent": "0.83.0",
-    "@opencode-ai/plugin": "1.18.18",
-    "@opencode-ai/sdk": "1.18.18",
+    "@opencode-ai/plugin": "1.18.21",
+    "@opencode-ai/sdk": "1.18.21",
     "@semantic-release/exec": "7.1.0",
     "@tintinweb/pi-subagents": "0.14.3",
     "@types/bun": "latest",

package/skills/ce-plan/SKILL.md

@@ -514,7 +514,7 @@ title: [Plan Title]
 type: [feat|fix|refactor]
 status: active
 date: YYYY-MM-DD
-origin: docs/brainstorms/YYYY-MM-DD-<topic>-requirements.md  # include when planning from a requirements doc
+origin: docs/brainstorms/YYYY-MM-DD-<topic>-requirements.md  # include when planning from a requirements doc; see Sources if the path is untracked
 deepened: YYYY-MM-DD  # optional, set when the confidence check substantively strengthens the plan
 ---
 
@@ -680,6 +680,9 @@ Omit `scopes_considered` unless the verdict is `unscoped`, and omit `acceptance`
 ## Sources & References
 
 - **Origin document:** [docs/brainstorms/YYYY-MM-DD-<topic>-requirements.md](path)
+  <!-- If the origin path is untracked in this repository, say so on this line. A
+       reader cloning the repo will not find it, and a bare link cannot tell them
+       whether they are missing context or whether it was always local. -->
 - Related code: [path or symbol]
 - Related PRs/issues: #[number]
 - External docs: [url]

package/skills/ce-plan/references/plan-sections.md

@@ -106,6 +106,14 @@ semantics so downstream tooling can rely on them:
   doc (e.g., `docs/brainstorms/2026-05-12-pagination-requirements.md`).
   Set when planning from an upstream brainstorm; carried for traceability
   and re-resolved when `ce:plan` re-deepens.
+
+  A repository may deliberately not track its brainstorm directory, treating
+  requirements docs as local planning input that the plan supersedes. The
+  field still carries real provenance for whoever wrote the plan, so keep it
+  — but a reader working from a clone will find nothing at that path. Say so
+  in Sources & References rather than leaving a bare link, because a link
+  that resolves to nothing cannot tell a reader whether they are missing
+  context or whether none was ever shared.
 - **`deepened`** — ISO 8601 date marking the first time the confidence
   check substantively strengthened the plan. Presence affects Phase 0.1
   resume fast-path logic (see `references/deepening-workflow.md`).

package/skills/deepen-plan/SKILL.md

@@ -57,6 +57,7 @@ Read the plan file completely.
 If the plan frontmatter includes an `origin:` path:
 - Read the origin document too
 - Use it to check whether the plan still reflects the product intent, scope boundaries, and success criteria
+- If the path does not resolve, continue from the plan alone rather than treating it as a defect. A repository may deliberately not track its brainstorm directory, in which case the origin exists only for whoever wrote the plan. Note that the check could not run instead of reporting a missing file.
 
 #### 0.2 Classify Plan Depth and Topic Risk