Repository navigation
AEP 0.19.1 skills say project/1 remains usable, but AEP0.68 refuses it #54
Description
Observed with installed agentplugins/AEP skills0.19.1 and AEP CLI0.68.0. planning/SKILL.md and implementing/SKILL.md say aep.project/1 stores remain usable and agents may carry on without migration. The current CLI instead refuses artifact list and lifecycle before any mutation with [unsupported_protocol_version]: the Markdown journal layout is no longer opened and migration to project/5 is required.
Reproduction: in an existing project/1 repository, run aep plan artifact list --kind story --format json or aep plan artifact lifecycle story under0.68.0. Both refuse. aep plan store migrate git --dry-run and --verify are available; a test migration here preserved14 artifacts,38 transitions and19 evidence entries.
Please align the planning/implementing/init/upgrade guidance with the supported CLI versions and migration prerequisite, and add a contract check that prevents documentation from promising continued legacy-store access after the CLI removes it. Preserve the requirement to review migration changes; do not solve this by instructing agents to silently use an older executable or hand-edit artifact state. The managed-copy migration is retained; the primary checkout was not changed.
Activity
Close #54 and #41; release 0.21.2 (#69)
b10x-bot commentedon Oct 7, 2026
Shipped in 0.21.2 through #69.
aep:planningandaep:implementingsay the newestaeprefuses anaep.project/1store with[unsupported_protocol_version]before any write, and that store work stops until the user approvesaep plan store migrate git --dry-run, then--verify, and commits the result. Neither skill tells an agent to carry on, use an olderaepor edit artifact files by hand.agentplugins-check toolsruns the newestaepagainst a generatedaep.project/1store and reports a skill row that disagrees with what that release does. Onaep0.68.0 it reports: refuses anaep.project/1store; 2 rows checked.