Skip to content

ForgeFlow 4.6.0: Clear agent roles and safer upgrades

Choose a tag to compare

View all tags
@BrandedTamarasu-glitch BrandedTamarasu-glitch released this 11 Sep 17:41
· 51 commits to main since this release
v4.6.0
7fda3c5

Upgrade from 4.5.0 or earlier

Use the installer from this release checkout for the first upgrade from legacy agent names. Do not run the old installed /update-forgeflow or $update-forgeflow for this migration. An old updater can remove customized legacy agents before its new code takes effect. If that already happened, use its rollback before another install replaces the backup.

Release commit: 7fda3c5bbb75fd5111ec6ae950e87a7e31733708.

In Bash:

FORGEFLOW_MIGRATION_DIR=$(mktemp -d)
git clone https://github.com/BrandedTamarasu-glitch/ForgeFlow.git "$FORGEFLOW_MIGRATION_DIR/source" || exit 1
cd "$FORGEFLOW_MIGRATION_DIR/source" || exit 1
git checkout --detach 7fda3c5bbb75fd5111ec6ae950e87a7e31733708 || exit 1

Then choose your host and preview before installing:

# Claude Code
node scripts/forgeflow/install-template.js --target claude --dry-run --json
node scripts/forgeflow/install-template.js --target claude

# Codex (honors CODEX_HOME)
node scripts/forgeflow/install-template.js --target codex --dry-run --json
node scripts/forgeflow/install-template.js --target codex

Use only your host's pair, or both if you use both hosts. The installer preserves edited or unverified legacy agents and reports them as preserved_legacy. Merge those instructions deliberately into the new roles. A full install can replace customized current managed files, so keep an independent copy of changes you want to merge. Restart your host to load the new names.

Future upgrades use the new updater installed by this step. An unchanged reinstall preserves the recovery snapshot; a later changed install or repair replaces that single snapshot. See the upgrade and rollback guide for custom homes and recovery.

Changes

  • Clear role names: Smith → Builder, Warden → Guardian, Lumen → Designer, Atlas → Coordinator, Arbiter → Architect, Compass → Product Lead, Aegis → Verifier.
  • Explicit task context in CLI and dashboard messages, retained through replay and export. Historical evidence stays intact.
  • Orwell's six writing rules in agent prompts for clean CLI output; specialized debate judging and answer-key validation instructions.
  • Stable historical learning IDs, correct mixed-name report totals, and context rebuilds that preserve old packets without validating them as current output.
  • Narrow automatic legacy cleanup, preserved no-op rollback snapshots, complete lifecycle message limits, missing-catalog hook recovery, and bounded profile registration.
  • Current service contracts, schema examples, role guides and presentation labels.

Validation and limits

On release commit 7fda3c5, the full local Node 24 suite passed 202/202 test commands, including service tests and TypeScript. All 28 browser checks passed against an isolated dashboard. A fresh npm ci --ignore-scripts completed, and version, plugin-manifest and documentation-link checks passed. Runtime code matches the independently reviewed audit fixes; release-only changes synchronize version manifests and public documentation. GitHub Actions remains disabled.

No live host restart, hosted model run, or measured model-performance improvement is claimed. The first-upgrade route above is required; publishing this release cannot change an already-running old updater.

Full changelog

Assets 2
Loading