Repository navigation
ess:hardening findings block; track the releases of 2026-10-08; release 0.22.3 - #75
Merged
Merged
Conversation
…026-10-08 releases - story:hardening-findings-block: ess:hardening's report closes with a findings block. - story:coordinator-returns-blockless-report (draft): the coordinator returns a block-less report to its author in a store that sets findings_required_since; waits for that aep release. - task:follow-releases-2026-10-08: aep 0.70.0, worktree 0.14.0, connectors v0.37.0, metaharness 0.9.3. - decision-blocker:approve-wave-2026-10-09, cleared: both units in one wave, one pull request, patch release 0.22.3.
- Reporting now requires a closing findings block, the same YAML list the AEP adversary and security reviewer end with (file, line, category, severity, verdict, origin, message), so a coordinator records it verbatim and aep plan artifact findings compares two hardening passes by signature. - One example block, a field table and a category table: spec-gap, missing-scenario, ess-limit, equivalent, false-positive. Overlapping wording follows adversary.md. - An implementation defect keeps a home: the suite was green, so it is either declared and unpinned (missing-scenario) or undeclared (spec-gap), with file and line on the implementation. - An empty pass is []; every finding in the prose appears in the block and nothing else does.
- ess:hardening § Reporting closes with a findings block that aep plan artifact findings parses.
…table row - A hardening report has no findings table; its message field is not a second wording of the prose finding.
- verified.json names aep 0.70.0, worktree 0.14.0, connectors v0.37.0 and metaharness 0.9.3 (ess stays 0.56.0); agentplugins-check tools passes against them, connectors also against a v0.37.0 binary built from its tag. - eval.yml moves Metaharness to 0.9.3, connectors to v0.37.0 and worktree to 0.14.0, and keeps AEP 0.68.0, the revision Metaharness 0.9.3 links. - managing-worktrees gains the worktree prune-archives paragraph of worktree 0.14.0's own skill; the website worktree page says the same. - The connectors skills follow v0.34.0 to v0.37.0: timeout at stage dispatch, outcome_unknown, revalidate_connection after a configuration revision change, the recorded create_connection refusal, and the HTTP host's v1alpha2 invoke; release links and the Rust note name v0.37.0. - aep:planning says how reverse init and store migrate git choose planning_scope and that --planning-scope sets it (aep 0.70.0). - The planning protocols pin moves to aep 0.70.0 (91a8251). - The shared gates pin moves to gates main 1a5ede1; the called common.yml is unchanged between the two commits and still downloads gates 0.1.8. - The Docs System dependency moves to 0.8.0 (6169592) with its lockfile; task site-build passes.
- verified.json, eval.yml, planning protocols, shared gates and Docs System pins follow the releases of 2026-10-08; worktree, connectors and aep:planning skill text follow them.
- CHANGELOG: ess:hardening findings block; AEP 0.70.0, Worktree 0.14.0, Connectors v0.37.0 and Metaharness 0.9.3 tracked - workspace, Cargo.lock, every carried plugin manifest and every Skill version line: 0.22.2 -> 0.22.3
- story:hardening-findings-block and task:follow-releases-2026-10-08 move to implemented on their test_result: task check (174 passed, agentplugins-check valid) and task site-build, exit 0, on dd2f96a.
- The release is cut on 2026-10-08 UTC; the changelog heading said the local date.
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.
One wave, two units, and release 0.22.3.
ess:hardening closes its report with a findings block (story:hardening-findings-block)
plugins/ess/skills/hardening/SKILL.md§ Reporting ends with the```findingsblock the AEPadversary and security reviewer already require: one example, a field table, the
[]rule.spec-gap,missing-scenario,ess-limit,equivalent,false-positive. Animplementation defect found on a green suite is one of the first two, with
file/lineat thecode.
[]block, recorded asreview-results in a scratchstore, are parsed by
aep plan artifact findingsof aep 0.69.1 and 0.70.0 without a refusal.Follow the releases of 2026-10-08 (task:follow-releases-2026-10-08)
verified.json: aep 0.70.0, worktree 0.14.0, connectors v0.37.0, metaharness 0.9.3; ess 0.56.0is still the newest.
agentplugins-check toolspasses (aep, ess, worktree, metaharness executedfrom release binaries; connectors against its source contract at v0.37.0 and a binary built from
its tag).
(
crates/metaharness-aep/Cargo.tomlrev 6d7a44d, the 0.68.0 tag); connectors v0.37.0,worktree 0.14.0.
worktree:managing-worktreesteachesworktree prune-archives(from 0.14.0'sworktree skill).connectors:integrating:timeoutatstage = dispatchversusadmission,outcome_unknown,revalidate_connectionafter a configuration revision change, the HTTP host's v1alpha2 invoke.aep:planning: howplanning_scopeis chosen;--planning-scope.protocolspin to aep 0.70.0 (91a8251); shared gates workflow pin to gates 1a5ede1,whose
common.ymlis unchanged; website Docs System 0.8.0 with its lockfile.worse.
Gates on the head commit
task check: exit 0.task site-build: exit 0.