ForgeGuard v1.6.0 - Delegation Intelligence

ForgeGuard v1.6.0 - Delegation Intelligence

This release adds a portable decision layer for whether and how authorized workers should be used.

• Reuse explicit approval within the current task/scope; request renewed approval only for delegation beyond it.
• Actively evaluate independent work for time, quality, coverage, or verification benefits; avoid workers when coordination costs dominate.
• Specify objective, scope, expected output, evidence required, and constraints for every worker.
• Keep planning, integration, conflict resolution, final verification, and the final response with the primary agent.
• Resolve instruction conflicts using the host platform's hierarchy while keeping explicit user instructions above ForgeGuard skill guidelines within ForgeGuard's own guidance.
• Calibrate verification to risk and scope and avoid redundant checks without new evidence or concerns.
• Default depth is 1; workers must not spawn subagents under this policy.

The managed Codex AGENTS block activates these concise rules; full policies ship in the skill references. Existing references remain available.

Design basis

The delegation, instruction-following, and testing principles in this release are informed by OpenAI's current Model guidance for GPT-6 Astra:

https://developers.openai.com/api/docs/guides/latest-model

The source recommends making user-versus-skill priority explicit, tuning when subagents should parallelize work, and calibrating testing for smaller changes. ForgeGuard keeps those ideas separate from its own policy choices: explicit delegation authorization, bounded worker contracts, primary-agent ownership, depth = 1, and a risk-aware verification matrix.

ForgeGuard does not use that OpenAI-specific guidance to invent a universal instruction hierarchy for Codex, Claude Code, Cursor, or future clients. The host platform remains authoritative for its actual instruction precedence and scope rules.

Upgrade

Run forgeguard install --force, preserving your original client/global options, and start a new coding-agent session. No migration or new CLI flag is required.

The optional runtime preset remains gpt-5.6-luna with xhigh reasoning. Existing --subagents, --subagent-model, --subagent-reasoning, and --no-subagent-config flags are unchanged. ForgeGuard does not change the primary model, mandate delegation, automatically route models, or become a standalone multi-agent runtime.

Release validation

Run npm test and npm pack --dry-run. The existing CI matrix runs Node.js 18, 20, and 22 and checks install/status/reinstall/uninstall. Tests validate installed policy references, managed instructions, version consistency, preservation, runtime defaults, portable instruction resolution, and the documented OpenAI design basis. Policy text checks protect the shipped contract; they do not prove model compliance. Exercise the five delegation scenarios in the target client when evaluating agent behavior.

Remote CI must pass before release; local test results alone are not evidence of remote CI success.