@warpgogol/forge 0.28.0 → 1.0.0

package/skills/fo/ef-onboard/SKILL.md

@@ -25,7 +25,7 @@ Guide the operator through creating a new Editframe video project within a Forge
 
 ### 1. Prerequisites check
 
-- **Node.js 18+**: Run `node --version`. If missing or below 18, direct the operator to `https://nodejs.org/en/download/` or install via the system package manager.
+- **Node.js 24+**: Run `node --version`. If missing or below 24, direct the operator to `https://nodejs.org/en/download/` or install via the system package manager.
 - **FFmpeg**: Run `ffmpeg -version`. If missing, direct the operator to `https://ffmpeg.org/download.html` or install via the system package manager (`apt install ffmpeg`, `brew install ffmpeg`).
 - If either prerequisite is missing and cannot be installed automatically, stop and ask the operator to install it manually.
 

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

@@ -1,6 +1,6 @@
 ---
 name: fo-idea
-description: Analyze a user's idea, decompose if too large, and route to fo-idea-create-rfc, fo-idea-create-adr, or direct implementation. Use when the user describes a change and is unsure if it needs an RFC, ADR, or no document.
+description: Classify an idea, split it when needed, and route it to an RFC, ADR, or direct implementation. Use when the required decision artifact is unclear.
 invocation: user
 category: fo
 concerns: document-only
@@ -131,7 +131,7 @@ These patterns **look like ADRs but are RFCs**:
 These patterns **look like they need a document but are direct implementation**:
 
 - **"Fixing content data"** — correcting a hash, updating a status field, or fixing a factual error in existing content is a data correction within existing structures, not an architectural change. Direct implementation.
-- **"Restoring broken behavior"** — a bug fix that restores the intended behavior within existing contracts is direct implementation, not an RFC. (See ADR-0008 for the precedent: "this is a bug fix restoring the intended behavior, not an architectural change.")
+- **"Restoring broken behavior"** — a bug fix that restores the intended behavior within existing contracts is direct implementation, not an architectural change.
 - **"Cosmetic cleanup"** — formatting, indentation, import ordering, or local variable renaming with no semantic impact is direct implementation.
 
 If the classification is ambiguous (e.g. the operator's description is too vague), ask a clarifying question using `ask_user_question` with the recommended classification first.

package/skills/fo/fo-idea-implement/SKILL.md

@@ -434,7 +434,7 @@ Before stamping `implemented`, verify that the ADR is mentioned in the codebase
 
 #### 4.10. Stamp implemented
 
-After all checks pass and documentation is updated, transition the ADR to `implemented` using `adr.implement.stamp` (RFC-0727). Direct edits to ADR `status`, `implementedAt`, and `updatedAt` are prohibited — use the stamp command instead.
+After all checks pass and documentation is updated, transition the ADR to `implemented` using `adr.implement.stamp` as required by the ADR lifecycle contract. Direct edits to ADR `status`, `implementedAt`, and `updatedAt` are prohibited — use the stamp command instead.
 
 1. Identify the implementation commit SHA — use the first `implement:` commit for this ADR.
 2. Run the stamp command:

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

@@ -30,12 +30,13 @@ Commit file changes after every standalone operator request that produces file c
 
 After every standalone operator request that produces file changes, perform the following:
 
-1. **Detect changed files.** Run `git status --short` in the monorepo root. If the working tree is clean (no modifications), skip — no commit.
-2. **Verify diff before staging.** Run `git diff` (not just `git diff --cached`) on every file the agent touched in this request. Confirm the changes are the agent's own work and not foreign changes from another session. If foreign changes are found, exclude them from staging.
+1. **Detect changed files in ALL trees.** Run `bash scripts/check-clean-trees.sh` from the repo root. This checks the werkstatt monorepo, all active mission workpieces, and all Sternsystem cache clones. If all trees are clean, skip — no commit. If any tree is dirty, proceed to commit each dirty tree.
+2. **Verify diff before staging.** Run `git diff` (not just `git diff --cached`) on every file the agent touched in this request, in each dirty tree. Confirm the changes are the agent's own work and not foreign changes from another session. If foreign changes are found, exclude them from staging.
 3. **Stage only agent-changed files.** Stage only the files the agent modified in this request. Never use `git add -A` or `git add .` — another agent or session may have unrelated changes in the working tree. Stage files by explicit path: `git add <path1> <path2> ...`.
 4. **Form commit message.** Write a conventional commit message (`fix:`, `feat:`, `refactor:`, `docs:`, `chore:`) based on the work performed in this request. The agent determines the type and description from the context of the request.
-5. **Commit in monorepo.** `git commit -m "<message>"` with the staged files.
-6. **Commit in mission workpiece (if applicable).** If the agent changed files in the active mission workpiece, commit there via the kernel's mission git commit command with the same message.
+5. **Commit in monorepo.** Use `pnpm exec werkstatt run ecosystem.commit --message="<message>"` (NOT raw `git commit`) as required by the canonical commit-discipline contract. Stage files with `git add <paths>` first, then run ecosystem.commit.
+6. **Commit in mission workpiece (if applicable).** If the agent changed files in the active mission workpiece, commit there via `pnpm exec werkstatt run mission.git.commit --mission=<missionId> --message="<message>"` as required by the canonical commit-discipline contract.
+7. **Verify clean trees.** After all commits, run `bash scripts/check-clean-trees.sh` again. If any tree is still dirty, report to the operator.
 
 ## What this skill does NOT do
 
@@ -50,6 +51,7 @@ The operator can skip the auto-commit for a specific request by saying "не к
 
 ## Failure modes
 
-- **No changes**: skill detects clean working tree and skips — no error, no commit.
+- **No changes**: skill detects clean working tree (via check-clean-trees.sh) and skips — no error, no commit.
 - **Workpiece not found**: if no active mission workpiece exists, skip workpiece commit. Monorepo commit still proceeds.
 - **Workpiece commit fails**: if the workpiece commit fails (e.g. dirty tree from another agent), the skill does not block the monorepo commit. The agent reports the failure to the operator.
+- **Post-commit verification**: after committing, re-run `check-clean-trees.sh`. If trees are still dirty, the agent MUST report the remaining dirty files to the operator before sending its response.

package/skills/shared/grilling/learned-principles.archive.md

@@ -0,0 +1,212 @@
+<!-- knowledge-layer: L2 -->
+# learned-principles.md (archive)
+
+Archived entries from learned-principles.md. Generated by forge.skill.knowledge.compact (RFC-0662).
+### K-0001: Extend infrastructure before feature logic
+
+```knowledge-entry
+id: K-0001
+layer: L2
+created: 2026-08-03
+lastConfirmedAt: 2026-08-03
+confirmations: 1
+promotedTo: shared/K-0003
+status: superseded
+```
+
+Promoted to shared layer as shared/K-0003.
+### K-0002: Unknown is not green
+
+```knowledge-entry
+id: K-0002
+layer: L2
+created: 2026-08-14
+lastConfirmedAt: 2026-08-14
+confirmations: 1
+promotedTo: shared/K-0001
+status: superseded
+```
+
+Promoted to shared layer as shared/K-0001.
+### K-0003: Quality claims bind to immutable identity
+
+```knowledge-entry
+id: K-0003
+layer: L2
+created: 2026-08-14
+lastConfirmedAt: 2026-08-14
+confirmations: 1
+promotedTo: shared/K-0001
+status: superseded
+```
+
+Promoted to shared layer as shared/K-0001.
+### K-0004: Evaluation must not mutate its subject
+
+```knowledge-entry
+id: K-0004
+layer: L2
+created: 2026-08-14
+lastConfirmedAt: 2026-08-14
+confirmations: 1
+promotedTo: shared/K-0004
+status: superseded
+```
+
+Promoted to shared layer as shared/K-0004.
+### K-0005: Immutable history and current health are separate
+
+```knowledge-entry
+id: K-0005
+layer: L2
+created: 2026-08-14
+lastConfirmedAt: 2026-08-14
+confirmations: 1
+promotedTo: shared/K-0001
+status: superseded
+```
+
+Promoted to shared layer as shared/K-0001.
+### K-0006: Migration complexity follows the real estate
+
+```knowledge-entry
+id: K-0006
+layer: L2
+created: 2026-08-14
+lastConfirmedAt: 2026-08-14
+confirmations: 1
+promotedTo: shared/K-0003
+status: superseded
+```
+
+Promoted to shared layer as shared/K-0003.
+### K-0007: Integrity requires an independent authority
+
+```knowledge-entry
+id: K-0007
+layer: L2
+created: 2026-08-14
+lastConfirmedAt: 2026-08-14
+confirmations: 1
+promotedTo: shared/K-0002
+status: superseded
+```
+
+Promoted to shared layer as shared/K-0002.
+### K-0008: Historical verification preserves policy bytes
+
+```knowledge-entry
+id: K-0008
+layer: L2
+created: 2026-08-14
+lastConfirmedAt: 2026-08-14
+confirmations: 1
+promotedTo: shared/K-0001
+status: superseded
+```
+
+Promoted to shared layer as shared/K-0001.
+### K-0009: Distributed evidence uses authority order and immutable cuts
+
+```knowledge-entry
+id: K-0009
+layer: L2
+created: 2026-08-14
+lastConfirmedAt: 2026-08-14
+confirmations: 1
+promotedTo: shared/K-0002
+status: superseded
+```
+
+Promoted to shared layer as shared/K-0002.
+### K-0010: Bootstrap safety does not create legacy authority
+
+```knowledge-entry
+id: K-0010
+layer: L2
+created: 2026-08-14
+lastConfirmedAt: 2026-08-14
+confirmations: 1
+promotedTo: shared/K-0003
+status: superseded
+```
+
+Promoted to shared layer as shared/K-0003.
+### K-0011: Documents are execution boundaries
+
+```knowledge-entry
+id: K-0011
+layer: L2
+created: 2026-08-14
+lastConfirmedAt: 2026-08-14
+confirmations: 1
+promotedTo: shared/K-0005
+status: superseded
+```
+
+Promoted to shared layer as shared/K-0005.
+### K-0012: Supersede decision authority, preserve useful mechanisms deliberately
+
+```knowledge-entry
+id: K-0012
+layer: L2
+created: 2026-08-14
+lastConfirmedAt: 2026-08-14
+confirmations: 1
+promotedTo: shared/K-0003
+status: superseded
+```
+
+Promoted to shared layer as shared/K-0003.
+### K-0013: Deterministic aggregators need scale contracts
+
+```knowledge-entry
+id: K-0013
+layer: L2
+created: 2026-08-14
+lastConfirmedAt: 2026-08-14
+confirmations: 1
+promotedTo: shared/K-0006
+status: superseded
+```
+
+Promoted to shared layer as shared/K-0006.
+### K-0014: Canonical identities require a closed snapshot boundary
+
+```knowledge-entry
+id: K-0014
+layer: L2
+created: 2026-08-14
+lastConfirmedAt: 2026-08-14
+confirmations: 1
+promotedTo: shared/K-0007
+status: superseded
+```
+
+Promoted to shared layer as shared/K-0007.
+### K-0015: Permanent formats profile standards instead of imitating them
+
+```knowledge-entry
+id: K-0015
+layer: L2
+created: 2026-08-14
+lastConfirmedAt: 2026-08-14
+confirmations: 1
+promotedTo: shared/K-0007
+status: superseded
+```
+
+Promoted to shared layer as shared/K-0007.
+### K-0016: Cutover enforcement starts after executor bootstrap
+
+```knowledge-entry
+id: K-0016
+layer: L2
+created: 2026-08-14
+lastConfirmedAt: 2026-08-14
+confirmations: 1
+promotedTo: shared/K-0003
+status: superseded
+```
+
+Promoted to shared layer as shared/K-0003.

package/skills/shared/grilling/learned-principles.md

@@ -11,16 +11,3 @@ Concrete principles distilled from past grilling sessions. Each principle has a
 - **Added:** <date>
 -->
 
-### K-0001: Extend infrastructure before feature logic
-
-```knowledge-entry
-id: K-0001
-layer: L2
-created: 2026-08-03
-lastConfirmedAt: 2026-08-03
-confirmations: 1
-status: active
-```
-
-- **Condition:** Plan grilling reveals that a feature depends on a schema field, serializer entry, or validation path that doesn't exist in the underlying module yet.
-- **Recommended answer:** Add a separate plan step to extend the infrastructure (schema, serializer, validator) before any step that creates or reads the new field/path. Zod safeParse silently strips unknown fields; fixed-order serializers skip unknown fields. Without the extension step, data is silently lost.