Repository navigation
docs: plugins describe aep 0.63, ess 0.37 and worktree 0.8.2; release 0.16.0 - #43
Merged
Merged
Conversation
- aep:planning and aep:implementing read .engineering/project.yaml before
the first store write and tell the user once when the store is not
aep.project/5: /1 (or no project.yaml) migrates with
`aep plan store migrate git --verify`; /2-/4 are refused by every verb and
go through the pinned aep build, the migration and the current release.
The skills do not rely on the CLI's stderr notice.
- The model section, guardrail 1 and store-conventions describe the files
as the store: a move appends to transitions, evidence is one immutable
file per record under .engineering/evidence/, one CLI write changes one
file, and validate refuses a hand-edited status.
- aep:init, planning section 5 and the reverse engineer start new stores at
/5 with store: {git: {}}; reverse init refuses an existing plan and names
the migration. aep:upgrade carries both migration paths.
- Every reason that rested on the append-only journal (critic panel,
wave, adversary, security reviewer, scoper, rubric) now rests on one
writer at a time and the revision: conflict between branches.
- website/docs/plugins/aep.md and golden-path.md say the same.
- The four Skill version lines carry 0.16.0 from the release commit.
Checked against aep 0.63.0 runs in throwaway repositories; the aep-backlog
trial wrote an aep.project/5 store with 278 tool calls (baseline 313).
- hardening: the mutation audit ships as `ess verify conform mutate` (0.34.0) with --emit/--collect for a project's own runner (0.37.0), and the Go/TypeScript packages carry the explorer; the "not shipped, #114" text is gone. A surviving mutant is answered by making the rule observable or filing a synthesis gap, never by an authored scenario. - specifying: new references/later-formats.md covers ess/11-15 fixtures, value expressions, outcome shapes (unknown_instance, deletes, into, accepts: nothing, preconditions), presence, Json, prefix, naming.wire scope, skip_absent, case-insensitive guards, when_subject_state with its two limits, and a per-holder limit pattern. syntax.md gives the unknown-instance order, `external: <reason text>`, instance: on a create and a move, params: on a view, and the one-default rule for when: branches. SKILL.md adds requires: ess pins and says a guard over a stored count needs a view that publishes state. - retrofitting maps a command that ignores in one state and refuses in another; testing-conformance covers fixture providers and the suite versions Go/TS accept; init/upgrade cover `ess specify toolchain`. - The interview skips its questions when the request asks for a finished specification, and without an AEP store lists its decisions in the report. Every added YAML example validates, and the pattern examples synthesize with 0 refusals under ess 0.37.0. Three trial rounds (ess-new, ess-retrofit) drove the wording fixes.
- managing-worktrees: archive includes every ignored file (remove build output first), refuses unsupported entries (submodules, nested repositories, special files, newline paths), and gc --apply returns an archived dirty tree to HEAD and removes it without force; adds the archive-bundle-invalid, archive-invalid and archive-stale refusals and removal-residue-unproven for an interrupted removal. - init: `activate --install-agent-guidance`, what it writes and when to use it. - website/docs/plugins/worktree.md: retained trees are kept unless an archive holds their exact state; --acknowledge-unrecoverable and repository-missing. Every spelled command checked against worktree 0.8.2 (19).
- trials/ess-pipeline/fixture: HoldRoom's creating outcome sets band, room, starts_at and hours from its input. ess 0.37.0 refuses an outcome that creates an entity without setting a field its invariant reads (ESS-COMMAND-018), so the trial agent stopped at validate and produced 0 of 4 outputs. Now: valid, 14 scenarios, 0 refusals, 4 of 4 outputs. - trials/baseline.json re-recorded from the accepted runs of this round: ess-new 38 tool calls (was 12; it now models the per-member limit it left unmapped, unmapped 7 -> 4), ess-retrofit 36 (29; 20 scenarios and 0 refusals, was 16 and 2), ess-pipeline 11 (19), ess-full-package 53 with 20 of 20 go tests, aep-backlog 278 (313).
- verified.json pins aep 0.63.1 (was 0.60.0) and ess 0.37.0 (was 0.35.0); worktree stays 0.8.2. aep 0.63.1 changes only snapshot verification, and every one of the 141 aep commands the plugins spell exists in it. - Workspace, all ten plugin manifests and the Skill version lines move to 0.16.0; CHANGELOG gains the 0.16.0 section. task check: exit 0 (fmt, clippy, 139 tests, 17 eval cases, 5 plugins). agentplugins-check tools: exit 0 (aep 0.63.1: 141, ess 0.37.0: 35, worktree 0.8.2: 19 spelled commands; syntax example valid, 14 scenarios). ESS trial round: ess-new, ess-retrofit, ess-pipeline, ess-full-package and aep-backlog accepted. The one aep finding, an empty findings block reported as prose only, is beyond10x/aep#60.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The
aep,essandworktreeplugins now describe the newest CLI releases, andverified.jsonpins them: aep 0.63.1 (was 0.60.0), ess 0.37.0 (was 0.35.0), worktree 0.8.2.docs(aep)aep.project/5store; a store-version check inaep:planningandaep:implementingwith the exact upgrade per version; new stores at/5; journal-based reasons rewrittendocs(ess)ess verify conform mutateand the explorers iness:hardening; newspecifying/references/later-formats.mdforess/11–ess/15; syntax, retrofitting, testing-conformance and init/upgrade fixesdocs(worktree)gcon archived and interrupted trees,activate --install-agent-guidancetest(trials)ess-pipelinefixture valid under ess 0.37.0 (ESS-COMMAND-018); baselines re-recordedchore: release 0.16.0Gates run locally:
task check: exit 0 (139 tests, 17 eval cases, 5 plugins).agentplugins-check tools: exit 0; aep 0.63.1 141, ess 0.37.0 35, worktree 0.8.2 19 spelled commands; syntax example valid, 14 scenarios.ess-new(38 tool calls, was 12: it now models the per-member limit; unmapped 7 → 4),ess-retrofit(36; 20 scenarios, 0 refusals),ess-pipeline(11; 4 of 4 outputs),ess-full-package(53; 20 of 20 go tests),aep-backlog(278, was 313; wrote anaep.project/5store).One finding for aep, filed as beyond10x/aep#60: an
approvereview-result with an empty findings block is reported as prose only.