You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
aep plan store migrate git on an aep.project/5 store no longer refuses it as having nothing to migrate: it drops every transition identical to the one immediately before it in its document, writes nothing else, and names each document it changed; with none it writes nothing and says so. It still refuses a dirty .engineering. --dry-run names what it would drop, and --verify reads every rewritten document back.
Fixed
aep plan artifact evidence --from <report/2> --suite <suite> records a report over an ordinary suite, the even ess-conformance/<N> major from /6 through /44 that ESS 0.56.0 and later write by default (no coverage block), as an ess_conformance_v2 record, bound to the suite by its version and original-byte digest. It was refused as MissingField at $suite.coverage. A suite is now routed by what it is: a coverage major to the coverage reader as before, and a version this build does not know is refused as UnsupportedSuiteVersion, naming it.
aep plan store migrate git wrote a move the aep.project/1 journal held twice (as a Git merge of journal.jsonl can leave it) as two identical transitions, which aep plan artifact validate then refused and no verb could remove. A move entry identical in every field to one already carried for its artifact is now carried once, and the migration (--dry-run too) prints how many it dropped. Moves that differ in any field, and repeated evidence records, are all kept.