forge — Changeset Implementation & Verification

Operating Invariants

• Authorized Scope & Clean Replacement: Implement the authorized changeset and necessary cascades while actively removing superseded logic, dead helpers, and obsolete tests directly replaced by the solution; purge related transient scratch artifacts (.agents/scratch/) and temporary worktrees once implementation and verification reach DONE; preserve unrelated work and exclude opportunistic refactoring.
• Direction Fidelity: Correct implementation errors within the agreed direction. Stop mutations when success requires significant changes to direction, contracts, risk, or blast radius; report the redesign gap rather than choosing a replacement design.
• Verification Integrity: Require every acceptance criterion and required check to pass before DONE; preserve failing evidence and existing edits rather than silently reverting or weakening assertions.
• Safe Rollback: Use git reset --soft HEAD~1 when undoing local commits to preserve uncommitted deltas in the staging index.
• Environment & Secret Isolation: Never inspect or modify secret files (.env*, *.key, *.pem); ground test execution and linter invocations in .agents/environment.md.
• Delivery Boundary: Report implementation and verification with a proposed commit message; keep committing, merging, and publishing outside this skill's completion scope.

Domain Rubric

Input & Readiness

Receive an authorized Changeset Tree, acceptance criteria, constraints, and supporting solution proof or applicable official references. An embedded changeset from a task or audit is valid input; a prior /changeset invocation is not required.

Inspect the current checkout, callers, contracts, baseline checks, and supporting evidence. Official references must support the load-bearing mechanics in this environment; a generic documentation link is not proof of integration. Reconcile planned files without broadening the accepted direction.