Installing and Upgrading to v6.2
What v6.2 Is, and Who Needs the v5.x Note
A Harvest Release
v6.2 folds edits that adopters made locally to shared toolkit files back into the toolkit — generalized, reviewed and tested — so you can update without losing them. It is also the first public release since v5.2, which means it carries the whole v6 shared Claude/Codex layout.
Headline changes:
- Gate: opt-in
visualleg, TIMED OUT reporting, default timeouts for build, lint, e2e and visual legs - Secret scanning: scoped source-code and type-member allowlists, shared by scanner and redactor
- Skill evolution: IDF-weighted attribution with an ambiguity band
- Memory promoter: no longer suggests the architecture skill's template scaffold as the target for constraints
- Learning intake (disabled by default), an author-neutral ghostwriting skill, and a publish preflight that refuses to copy private names or personal paths
Migration
No migration is required for v6.2 itself. If you are coming from v5.x, read docs/reference/agents/migration-v6.md: it explains the canonical-versus-native change and local release distribution. Your application's own build, test and PR gates are unchanged.
Toolkit reference docs under docs/reference/agents/ reach a project through the publish artifact; install and update do not deliver them. If the migration note is missing from your tree, get it from the published repository.
You are already on v6.1. What migration steps does v6.2 require?