Repository navigation
ForgeGuard v1.6.1 — Current-task Goal Management
This patch release fixes the boundary between Goal Intelligence and task creation.
- Goal definition and persistent goal state remain attached to the current task.
- ForgeGuard does not create a separate task, thread, chat, worktree, or delegated worker merely to define, refine, store, replace, or continue a goal.
- A goal conflict is not treated as authorization to create a separate task.
- Environments with goal-management capabilities use those capabilities according to their actual contract.
- Environments without goal-management capabilities keep the goal in current-task context or use an established in-task planning mechanism.
The managed Codex AGENTS block and the compact skill instructions include the same invariant, and contract tests protect the shipped policy text.
Upgrade
Run forgeguard install --force, preserving the client and scope options used for the existing installation, then start a new coding-agent session so updated instructions are loaded.
No CLI flags, runtime preset defaults, or public package APIs changed.
Release validation
Run npm test and npm pack --dry-run. The CI matrix validates Node.js 18, 20, and 22, CLI lifecycle behavior, version consistency, installed policy references, and the current-task Goal Intelligence contract.
Remote CI must pass before the release is considered complete.