Clear agent roles and safer upgrades
First upgrade from legacy names
Use the source-checkout upgrade procedure for this migration. Do not start it with an old installed updater: downloading new code does not replace the functions already running. The release announcement supplies the reviewed commit SHA. The new installer preserves edited or unverified legacy agents and installs the updater used for later releases.
A full source install can replace customized current managed files. Preview it and keep an independent copy of customizations you want to merge. Restart the host after installation. A byte-identical reinstall preserves the migration recovery snapshot; a later changed install replaces that single snapshot.
Names and output
- Smith becomes Builder; Warden becomes Guardian; Lumen becomes Designer; Atlas becomes Coordinator; Arbiter becomes Architect; Compass becomes Product Lead; Aegis becomes Verifier.
- CLI and dashboard messages identify the role and explicit task context. Context persists through replay and export without inferring new context for old messages.
- Agent prompts apply Orwell's six writing rules. Generated debate roles now distinguish judging and answer-key validation.
- Legacy identity aliases remain accepted at supported boundaries. Historical evidence bytes and stable v1 envelope keys remain unchanged.
Migration and runtime fixes
- Historical learning IDs stay stable so retired advice remains retired. Mixed legacy/canonical reviewer histories share report thresholds.
- Rebuilt context packs select active packets from their manifest while preserving old packet files.
- Automatic stock-legacy cleanup does not reinstall customized replacements. Repeated unchanged source installs retain the recovery snapshot.
- Lifecycle requests validate the complete upstream message limit before acknowledging the request. Partial hook installs retain unrelated telemetry and explain how to repair explicit verdict recording.
- Profile registration has a bounded timeout. Current service docs, schema examples and presentation labels match the new names.
Validation
The local regression suite covers the real pre-migration updater as a negative control, both-host source installation, custom-file preservation, recovery, historical identity, context contracts, transport and generated prompts. The release announcement records final test results. GitHub Actions remains disabled; no hosted model run or live host restart is claimed.