Skip to content

release: 0.10.0 — the coverage skill, and specify corrected by a real adoption - #9

Merged
b10x-bot[bot] merged 60 commits into
mainfrom
release/0.10.0
Sep 26, 2026
Merged

b10x-bot[bot] merged 60 commits into
mainfrom
release/0.10.0

Conversation

@timofriedlberlin

Copy link
Copy Markdown

A new skill is a new capability, so this is a minor.

ess-specify:specify, corrected by a real adoption

An adopter specified a 46k-line Rust service with this skill and held it to a conformance suite. Six
defects cost measurable time, and one caused the rest.

The skill wrote format: ess/1 in its example and pinned its sample output to a named ESS release.
The language has four majors. Following the instructions produced a whole specification at ess/1
and a thirteen-item list of things "ESS cannot say" — of which three were already solved and a
fourth was solved on re-baselining. It now opens by asking what the binary speaks, and asserts no
release number anywhere.

The other five:

  • The predicate grammar was never described. kind == WebCrawl or kind == ZendeskHc parses as
    one fact path, and its undeclared reference refusal reads as proof that disjunction does not
    exist. Compounds are structured; the worked example is an implication.
  • Authored scenarios never appeared. A quarter of that adopter's suite reported no information
    until one established a row directly. The flag that selects them is now named, along with the
    reason they are needed: synthesis arranges a subject by replaying commands and reads no entity
    relations.
  • run was described as holding "a built-in reference implementation". One of those targets
    says in its own source that it executes no part of the model; pointed at an adopter's
    specification it returns every scenario unsupported, which prints like a result.
  • aep plan reverse openapi was oversold as the first move. On a fifty-operation contract it
    yielded 197 types, zero entities and 132 UNMAPPED markers. It is now described by what it
    gives you, with identity and lifecycle read from the implementation.
  • Two of seven sections addressed the wrong audience. ## Adapter contract and
    ## Format changes are about importers, projectors and minting a major — work done on ESS.
    Both are gone.

New rule: a refusal is real when a handler performs it. Auditing one specification against its
service found a refusal nothing performs, two idempotent operations modelled as conflicts, and an
entity that was a request extractor rather than a stored row.

ess-specify:coverage

Gains the skip block that is neither a missing construct nor an undriven plane — a precondition the
model cannot state — and the runner that refuses a newer-vocabulary suite until it is admitted.

Release mechanics

Workspace version, twelve plugin manifests, three Skill version lines, README.md,
website/docs/install.md and website/docs/plugins/connectors.md move together to 0.10.0;
Cargo.lock follows. ## [Unreleased] becomes ## [0.10.0] — 2026-09-18.

task check green: valid: 9 eval case(s), 1 recorded transcript(s) replayed,
valid: marketplace beyond10x, 6 focused plugin(s). Planning store: story:specify-corrected-by-a-real-adoption
(implemented, with a test_result record) and task:release-0-10-0-specify-corrections.

Tag after merge, not before.

… adoption

A new skill is a new capability, so this is a minor.

`ess-specify:specify` asks what the binary speaks before writing a `format:` line and asserts no
release number anywhere. The two it pinned are what went stale: an adopter following them specified
a 46k-line service entirely at `ess/1` and produced a thirteen-item list of things ESS cannot say,
of which three were already solved and a fourth was solved on re-baselining.

It also gains the predicate grammar (an infix `or` parses as one fact path, and its refusal reads
as proof that disjunction does not exist), authored scenarios and the flag that selects them, the
fact that a built-in target proves nothing about an adopter's implementation, and the rule that a
refusal is real when a handler performs it. `## Adapter contract` and `## Format changes` are
gone; both addressed someone working on ESS rather than someone using it.

`ess-specify:coverage` gains the skip block that is neither a missing construct nor an undriven
plane — a precondition the model cannot state — and the runner that refuses a newer-vocabulary
suite until it is admitted.
b10x-bot Bot added 27 commits September 18, 2026 22:45
- Add plugins/aep-drive/agents/security-reviewer.md, an independent
  verification role with the same mechanics as the adversary reviewer:
  a failing conformance test per unenforced invariant, the same
  CONFIRMED / NEEDS-CHANGE / INFEASIBLE verdicts, the same origin axis,
  the same findings block and report shape, so a coordinator can
  dispatch it wherever it dispatches a review.
- It states the work as defensive verification of a change's own
  invariants, without combative language, so a review of privileged,
  integrity- or boundary-sensitive code is not misread as an exploit by
  a platform safety classifier and killed before it runs.
- The existing adversary agent is unchanged; this is additive.
- Bump the workspace version and all six plugin manifests, in both the
  Claude and Codex manifest sets, to 0.9.3, with Cargo.lock and the
  three version-stamped skills (planning, story-migration, wave).
- Changelog: close the Unreleased section as 0.9.3, covering the new
  ess-specify:coverage skill already on main and the new aep-drive
  security-reviewer agent.
- Pin the passive documentation bundle action at Docs System 339b4b8,
  the revision Website consumes.
- Add the generated read-only Documentation source check workflow,
  which runs the publisher's per-source checks on pull requests and
  main pushes without credentials.
- Regenerated by `atlas docs reconcile`; the AGENTS.md operations block
  describes the new workflow.
Advance the shared documentation runtime and add the source check
…in (#11)

- Remove plugins/ess-specify, its marketplace entries, website page and
  eval case; ESS ships its own ess plugin from beyond10x/ess at the
  binary version, and `ess skill` prints the same skills.
- agentplugins-check expects five plugins and refuses the retired name;
  the sweep skips a linked worktree .git file.
- Front door, resource map and aep-plan planning skill point at
  ess:specify; docs drop the ESS install.
- Release 0.10.0: workspace, manifests, stamped skills and install pins.

Refs: story:retire-ess-specify
…workspace-hygiene

- Both marketplace formats declare identity `b10x`; every install line
  reads `<plugin>@b10x`. The changelog says how to drop a registration made
  under the earlier name.
- Remove plugins/workspace-hygiene and its website page. Worktree now ships
  its plugin from beyond10x/worktree plugins/worktree at the binary's
  version (Worktree 0.6.0). The copy here had drifted: workspace-hygiene
  0.10.0 lacked the patch-equivalent recovery-proof guidance that Worktree
  0.5.0 generates.
- The Claude Code marketplace lists `worktree` as a git-subdir entry at tag
  0.6.0, commit 3d4954b7f0cde907a5b8a27a6c3d095368d4a1cf. Codex marketplaces
  take local paths only here, so Codex reads worktree@worktree from the
  worktree repository.
- agentplugins-check: new remote module. The offline gate refuses an entry
  that is not a pinned git-subdir at the declared repository and path, or
  that declares its own version. `agentplugins-check remote` (network)
  refuses a sha that is not the tag's commit, manifests at that commit with
  another version, and a tag that is not the newest release; verified
  against 0.6.0 and refused with the 0.5.1 merge commit substituted.
  remote-plugins.yml runs it on pull requests, main pushes and daily.
- workspace-hygiene joins the retired names; routing skill, wave skill,
  resources, README, install guide, intro, sidebar, home page and social
  card point at worktree; eval coverage prose reads 4 of 7 skills; eval
  tests that used workspace-hygiene as a fixture use connectors.
- AGENTS.md invariants: identity b10x, and the pin-not-copy rule for
  product plugins.

Refs: story:worktree-plugin-by-pin
- Workspace, Cargo.lock, every plugin manifest, the three version-stamped
  skills and every install pin move from 0.10.0 to 0.11.0.
- Changelog: close the Unreleased section as 0.11.0. The minor bump marks
  the breaking marketplace rename to b10x and the retirement of
  workspace-hygiene in favour of the pinned worktree plugin.

Refs: story:worktree-plugin-by-pin
refactor!: b10x marketplace; worktree by pin; release 0.11.0
- New crate crates/b10x (clap): `b10x setup plan` reads both hosts
  (claude/codex plugin and marketplace lists as JSON, ~/.codex/config.toml),
  every catalog binary on PATH and the plugin entries in known projects'
  settings, and prints findings and exact argv actions; `setup apply`
  refuses a stale plan, snapshots every file it changes, runs the actions
  and re-plans to prove convergence; `setup undo` restores the snapshot;
  `check` is the offline session-start drift check; `install` installs a
  catalog binary from its checksummed archive or `cargo install --tag`.
- Planning is a pure function of recorded host output; 21 tests on
  fixtures recorded from a clean HOME with a legacy install on both hosts
  (home paths replaced with /opt/b10x-home).
- End to end in a clean HOME seeded with agentplugins 0.10.0 under the old
  marketplace name on both hosts, a local-scope legacy install, an orphan
  project entry and ess 0.29.0: plan listed 32 actions, apply ran 32/32,
  the second plan changed nothing, and undo restored all 8 files.
- catalog.json lists products, plugins, binaries, how each binary's version
  is bound (to its plugin, or the newest release) and retired names; it
  names no version. Versions resolve at run time.
- Front door `beyond10x` becomes `b10x`: skills setup (new), guide (was
  beyond10x:beyond10x), plugin-creator, and a SessionStart hook running
  `b10x check`; in a live session it reported this machine's worktree
  0.4.1 under plugin 0.6.0 and a leftover legacy install.
- Remote entries are version-free: ess and worktree are git-subdir with
  repository and path only, in both marketplace files (Codex accepts
  git-subdir; 0.11.0's statement otherwise was wrong). The checker refuses
  ref/sha/version on them and a catalog that disagrees with the
  marketplaces; `agentplugins-check remote` refuses a default branch that
  serves an unreleased plugin version.
- SETUP.md and b10x-<target>.tar.gz archives for four targets become
  release assets; README, AGENTS.md invariants and the website describe
  the one-sentence route.

- The planning story (story:one-sentence-onboarding) is not in this commit:
  any journal write trips the whole-file personal-paths scan on three
  journal lines from 2026-09-07/09. Its patch is kept for replay once
  Gates ships the appended-tail scan.
- Workspace, Cargo.lock (agentplugins-check, b10x), every plugin manifest
  this repository carries, and the three version-stamped skills move from
  0.11.0 to 0.12.0.
- Changelog: close the Unreleased section as 0.12.0. The minor bump marks
  the breaking rename of the front door to b10x and the version-free
  remote entries.
- task check passes: 37 + 2 + 21 tests, 8 eval cases, marketplace b10x
  with 4 carried and 2 remote plugins.
feat!: one-sentence onboarding through b10x setup; release 0.12.0
- website/docs/structure.md states the plugin concept as eight rules:
  one marketplace; one plugin per product, named after its CLI; skills
  are activities in -ing form; every agent owned by exactly one skill,
  which lists it under `## Agents`; every <plugin>:<name> reference
  resolves; one README row, plugin page and sidebar entry per plugin.
- New crates/agentplugins-check/src/concept.rs enforces R2-R4, R7 and
  R8 in `task check` (R1, R5, R6 were already checked). Against the
  0.12.0 tree it reported 19 violations; a planted `aep:bogus` reference
  and a dropped README row both fail it. `agentplugins-check remote`
  lists the R3 renames ess and worktree still owe without failing.
- aep-plan and aep-drive merge into plugins/aep: skills planning,
  migrating (was story-migration) and implementing (wave and drive as
  two modes; their bodies moved unchanged to references/), and eleven
  agents. Catalog product aep is one plugin; setup replaces any aep-plan
  or aep-drive install with one aep install per scope (new test).
- Skills renamed to activities: b10x:installing/routing/
  authoring-plugins (were setup/guide/plugin-creator) and
  connectors:integrating. Old ids join the retired names; references in
  skills, agents, hook text, eval subjects and docs follow.
- README is one paragraph plus a table of plugins with the install
  command per host; the b10x reference moved to its plugin page, eval
  costs and CI to evals/README.md, repository rules to AGENTS.md.
- b10x setup undo refreshes both hosts' marketplaces after restoring
  (Codex could not list plugins until it did); a host whose plugin
  commands fail is reported with its error and repair command.
- Verified: task check exit 0 (42 + 2 + 22 tests); site build exit 0;
  claude plugin validate passes for the marketplace and all three
  carried plugins; a live Claude session with plugins/aep and
  plugins/b10x lists exactly aep:planning, aep:migrating,
  aep:implementing, b10x:installing, b10x:routing,
  b10x:authoring-plugins and the eleven aep agents; the sandbox migration
  from 0.10.0 converged with one plugin per product on both hosts.
- Workspace, Cargo.lock (agentplugins-check, b10x), every carried plugin
  manifest and the three version-stamped aep skills move from 0.12.0 to
  0.13.0.
- Changelog: close the Unreleased section as 0.13.0. The minor bump marks
  the breaking plugin merge (aep) and the skill renames.
- task check passes: marketplace b10x with 3 carried and 2 remote
  plugins, 8 eval cases, the concept check green.
feat!: one aep plugin, activity-named skills, concept enforced; release 0.13.0
- New `b10x skill <plugin>` lists an installed plugin's skills and agents
  and `b10x skill <plugin>:<skill>` prints one, from Claude Code's
  recorded install path or Codex's plugin cache (newest version). Two
  tests on fixture homes.
- `b10x setup apply` ends by naming it, and SETUP.md gains step 3, "use
  what you installed".
- The installing skill plans with `--host claude` or `--host codex` for
  the host it runs in, adds the other only on request, and writes the
  plan with `--out` alone instead of `--json --out`.
- From a trial: an agent given only the repository link specified a todo
  service with ess and reached `todo v1 — 3 file(s), valid`; it searched
  ~/.claude/plugins/cache because the new plugin could not load
  mid-session, installed into Codex for a Claude-only task, and received
  the whole plan JSON on stdout.
- task check passes: 42 + 2 + 24 tests.
- Workspace, Cargo.lock (agentplugins-check, b10x), every carried plugin
  manifest and the three version-stamped aep skills move from 0.13.0 to
  0.13.1; the changelog section is dated.
- Patch bump: a new b10x subcommand and instruction changes; no plugin,
  skill or catalog name changes.
feat(b10x): read installed skills before a restart; release 0.13.1
…prebuilt

- plugins/ess and plugins/worktree join b10x, aep and connectors: the text
  comes from ess 0.30.0 and worktree 0.6.0 and is owned here from now on.
  Both marketplace files list all five from ./plugins; the checker refuses
  any other source (structure R1).
- R3 amended: every plugin carries `init` and `upgrade`; every other skill
  is an activity. New skills: b10x:init (guided onboarding: what do you
  want to do, how to install the CLIs) and b10x:upgrade; init/upgrade for
  aep, ess, worktree, connectors. Renames: b10x:installing -> init,
  ess:ess -> init, ess:specify/retrofit/coverage -> specifying/
  retrofitting/testing-conformance, worktree:worktree ->
  managing-worktrees. Old ids join the retired names.
- b10x: `init <products>` and `upgrade [<products>]` plan only those
  products; `--method cargo|prebuilt` (default cargo when on PATH, else
  prebuilt; a release without archives falls back to cargo); every CLI is
  bound to its newest release; catalog format b10x.catalog/2 with both
  methods and intent phrases; plans end with Next hints; `check` reports
  a CLI older than the newest release last seen, a check older than seven
  days, and nothing set up yet. 28 b10x tests, 3 new.
- ess:specifying gains references/syntax.md, a todo service in three
  files that `ess specify validate` accepts (checked with 0.30.0), and
  ess:testing-conformance explains an all-unsupported suite for a new
  domain: the two gaps trial 1's agent hit.
- agentplugins-check `tools` replaces `remote`: downloads the newest aep,
  ess and worktree archives (checksums verified), runs every command the
  skills spell with --help (156 checked: aep 0.58.0 128, ess 0.30.0 14,
  worktree 0.7.0 14) and validates the syntax example. Its first run found
  drive.md spelling `aep drive watch`, which aep does not have; reworded.
  The concept check refuses a CLI version quoted in plugin text; nine were
  removed.
- Sandbox (fresh HOME, B10X_MARKETPLACE on this tree): `b10x init ess
  --method prebuilt` planned 4 actions, apply ran 4/4 and converged, `b10x
  skill ess` listed the five skills and three agents, `b10x check` was
  silent; after seeding ess 0.29.0 it printed the drift line and `b10x
  upgrade ess` planned the one upgrade.
- Docs: structure.md, install, plugin pages, SETUP.md steps 2-3, AGENTS.md
  map and gate.
- Workspace, Cargo.lock (agentplugins-check, b10x), all five plugin
  manifests and the version-stamped aep skills move from 0.13.1 to
  0.14.0; the changelog section is dated.
- Minor bump: breaking skill renames, ess and worktree moving here, and
  new b10x commands.
- task check passes: marketplace b10x with 5 plugins, 8 eval cases.
feat!: every plugin here; init and upgrade on each; CLIs by cargo or prebuilt; release 0.14.0
- The 0.14.0 release workflow grepped `b10x setup guide` for
  `name: installing`, which the rename to b10x:init retired; all four
  package jobs failed and 0.14.0 published no release or archives. The
  smoke test now looks for `name: init` (checked against a local release
  build).
- Workspace, Cargo.lock, all five plugin manifests and the
  version-stamped aep skills move to 0.14.1; the changelog says why.
- task check passes.
fix(release): smoke-test the init skill; release 0.14.1
- SETUP.md creates ~/.cache before mktemp in it (a fresh home has none).
- b10x:init plan example uses placeholders for products and method.
- A product init skips installing when its CLI already answers.
- ess:specifying syntax example becomes a lending library (a todo task
  copied the todo example), shows terminal: [] and validates with ess
  0.30.0 (library v1 — 3 file(s), valid).
- b10x upgrade updates only what is installed and leaves a host with
  nothing Beyond10x alone; upgrade skills pass --host. New test.
- Plan output lists the marketplace refresh apply runs.
- Release 0.14.2: workspace, lockfile, manifests, skill stamps, changelog.
- task check exit 0 (b10x 29 tests); tools green against aep 0.59.0, ess
  0.30.0, worktree 0.7.0.
fix: trial 2 findings; release 0.14.2
- ess-specify was retired in 0.10.0 (PR #11, 514ef9e); the 0.10.0 release gate run 35920939084 is recorded as test_result.
- The body records that the routing target moved: ess#68 removed the ESS repository plugin and it now ships from here as plugins/ess (0.14.1).
plan: record retire-ess-specify as implemented
Six fresh agents on the local 0.14.3 checkout, headless and isolated
(three ESS, AEP planning, worktree, upgrade from a seeded 0.12.0),
after trial 3 on 0.14.2 found where the skills made agents guess.

- ess:specifying: UpperCamel state names; ess-inputs.yaml documented;
  generate --out subdirectories; invariants need a view holding every
  state, and the syntax example gains one (3 synthesis refusals -> 0).
  The syntax reference covers stored-state rules, no double booking,
  and ordering a time range by an Integer length.
- ess:retrofitting: the importer reads OpenAPI 3.1 only; aep reverse
  openapi reads 3.0. Stale skill names in its description.
- ess:testing-conformance: what the built-in targets are and how to hold
  a real implementation to a suite (synthesize --target go|typescript).
- aep:planning / aep:migrating: --protocols and --profile values; store
  creation in every case; domain before stories; scratch files in the
  repository; empty findings fence recorded as []. The design and
  parallel-safety critics name the same two remedies for a shared file.
- worktree:init / managing-worktrees: profile source, profiles=0, remote
  needed for cleanup, branch before the first commit.
- b10x: upgrade installs the replacement of a legacy plugin it removes;
  local legacy installs are not reinstalled when user scope covers them;
  plans name Beyond10x on hosts they do not cover; check no longer says
  nothing is set up when a legacy plugin is present.
- agentplugins-check: clap; trial-isolation; tools synthesizes and
  generates the ESS example; README plugin tree kept exact (R8); the
  retired sweep covers `ess skill`.
- Trial tooling: task trial:sandbox / trial:run under /var/tmp, and the
  repository skill improving-by-trial.
b10x-bot Bot added 28 commits September 25, 2026 10:25
docs: tidy the 0.14.x changelog; release notes from CHANGELOG.md
- The bot App has issues: write since 2026-09-25, so it labels issues
  at creation; before that GitHub dropped the label and returned 403
  on label, comment and close.
- improving-by-trial and AGENTS.md name the label as the ledger, with
  one search for open findings and one for fixed ones whose release
  still has to be checked. A workaround goes when the fix is released,
  not when the issue closes.
docs: the trial-finding label is the issue ledger again
From the round-4 trials on 0.14.4 (ESS retrofit of a stock-reservation
service, worktree onboarding). Skills checked against ess 0.31.0.

- ess:retrofitting: a command the code silently ignores in a state
  gets no wrong_state outcome and no error; ESS-SYNTH-012 is expected
  there and the scenario still requires that nothing happened
  (verified with ess 0.31.0). The invariant view is structural.
- worktree:init: curl --create-dirs instead of a separate mkdir; any
  local file works as the profile; a headless run picks the directory
  holding the repository as workspace root and says so.
- worktree:managing-worktrees: always pass --id to gc.
fix: round-4 trial findings; release 0.14.5
The fixes for the trial findings (aep #31/#32, ess #72-#75) are
released; each change was checked against the released binaries.

- ess:retrofitting: OpenAPI 3.0 imports; nullable fields are coverage
  gaps carried as UNMAPPED markers; objects must be closed with
  additionalProperties: false.
- Syntax reference: compare two fields through one struct
  (window.ends_at > window.starts_at); the flat form is refused. The
  stored-value case links ESS's design note for #75.
- ess:specifying: drop the "legacy" help note.
- aep:planning: point at the store's refusal, which now says to write
  [] in an empty findings fence.
fix: skills follow aep 0.59.3 and ess 0.32.0; release 0.14.6
- story:one-sentence-onboarding, created with `aep plan artifact new`,
  describes onboarding as it now ships: SETUP.md asks before installing
  b10x, /b10x:init asks what the user wants and how to install CLIs
  (prebuilt by default), and plans and applies only after confirmation.
- Its acceptance is the isolated trial that upgrades a seeded 0.12.0
  install, plus a fresh agent reaching a validated ESS specification
  from the link alone.
- Rebuilt because the 2026-09-24 draft no longer applies to the store.
The operator's decision, asked for by a team adopting ESS: with Rust
installed, every CLI used to be built from source.

- b10x picks the release's checksummed prebuilt archive by default and
  cargo only on --method cargo or when a release has no archive
  (plan.rs method(); its test now expects prebuilt with cargo on PATH).
- b10x:init offers prebuilt first; the product init skills say which
  method is planned and offer the other; SETUP.md, the install page,
  the plugin pages and the --method help say the same.
feat: prebuilt is the default install method; release 0.14.7
- catalog.json: b10x-harness is an optional binary of aep (archive and
  cargo from beyond10x/harness). A new `platforms` field limits it to
  Linux; b10x does not plan it elsewhere.
- resolve.rs reads the targets each newest release's SHA256SUMS lists
  (install::listed_targets); plan.rs chooses prebuilt only when this
  machine's target is among them, else cargo, else a warning naming
  the target. The per-repository yes/no flag is gone.
- b10x install <cli> uses the same default; since 0.14.7 it still chose
  cargo whenever cargo was on PATH.
- aep:init: metaharness is optional and installed with b10x install.
- Docs name b10x-harness; tests cover target selection, SHA256SUMS
  parsing and the platform rule. task check: 89 tests passed.
- Checked: b10x install b10x-harness / metaharness on x86_64 Linux
  install 0.13.2 and 0.8.0 from their prebuilt archives.
feat: b10x-harness in the catalog, prebuilt by target; release 0.14.8
…; release 0.14.9

- trials/<name>/trial.yaml: prompt, fixture, setup, measures and
  expected outputs for seven trials; `task trial:run TRIAL=<name>`
  prepares the sandbox and runs one; the gate checks the definitions
  (agentplugins-check trials.rs, trial-prepare).
- ess-full-package: every ESS output, an in-memory Go implementation
  and `go test` against the generated suite; sandboxes get go.
- agentplugins-check trial-report (report.rs): tool calls, validate,
  synthesis, UNMAPPED markers from disk, outputs present, go test
  counts; exits 1 against trials/baseline.json when a measure gets
  worse. trial:run calls it after trial-isolation.
- improving-by-trial and AGENTS.md describe the definitions, TRIAL= and
  the baseline. task check: 101 tests passed.
feat: trial definitions, full-package ESS trial and measured baseline; release 0.14.9
Round 5, the first measured round: seven trials on 0.14.9, all
isolated. ess-full-package produced every ESS output and ran go test
against the synthesized suite: 13 passed, 0 failed, 0 skipped.

- trial-report recognises every spelling of go test, only in command
  position; it reported the full-package run as "not run".
- b10x setup plan keeps installed optional products when nothing is
  selected; it proposed uninstalling an installed connectors.
- ess:specifying: all generate kinds, one --out per kind side by side
  (nested outputs are refused), which kinds add a folder; OpenAPI and
  AsyncAPI need a component or write 0 artifacts silently (ess#102).
- ess:testing-conformance: suite inside the implementation's module;
  payload numbers as float64 (ess#101).
- Trials allow cargo; aep, worktree and upgrade prompts say nobody
  will answer questions.
- trials/baseline.json: first baseline from six round-5 runs
  (upgrade-seeded left out: its agent stopped to ask).
- task check: 103 tests passed.
fix: round-5 trial findings and first baseline; release 0.14.10
…ase 0.14.11

- b10x check refreshes the newest releases at most once a day
  (check::refresh, resolve::latest_tags, 3 s timeouts, parallel) and
  names /b10x:upgrade when plugins or a CLI are older.
- make_plan plans from the remote release when the local marketplace
  clone is older (resolve::stale); upgrade reported 0.14.7 as current.
- verified.json: releases the skills were verified against; the daily
  tools check fails on a newer aep, ess or worktree release.
- b10x pin / unpin and b10x.toml (pins.rs): exact or minor-line pins,
  honoured by init, upgrade, setup plan and install; check warns on a
  mismatch and when skills describe a newer release.
- task check: 115 tests passed.
feat: daily freshness check, verified releases and tooling pins; release 0.14.11
- ess:init first validates an existing specification and runs the
  repository's own conformance command, reports the counts, and
  recommends ess:testing-conformance when the suite is green.
- Every b10x init or upgrade command a plugin prints names --host, with
  the wording of b10x:init; agentplugins-check refuses one that does not.
- ess:testing-conformance shows a TypeScript refusal recorder beside the
  Go one.
- The ESS syntax reference lists the structured predicate forms when,
  invariants and filter accept, stops telling authors to split "A or B"
  into two views, and names the forms synthesize still refuses
  (beyond10x/ess#92, expectation 2).

Refs: #32, beyond10x/ess#92
- When another host holds Beyond10x installs, init and upgrade compute
  that host's plan read-only and report its action count and kinds
  (legacy installs, missing plugins, marketplace changes), or say in one
  line that it is current.
- "Nothing to change." is qualified to the planned host while the other
  host's plan has changes; the setup-plan/1 document is unchanged.

Refs: #33
- One unit of the agentplugins wave for #32 and #33.
- One unit of the agentplugins wave for #32 and #33.
- CHANGELOG section for #32, #33 and the ESS syntax correction for
  beyond10x/ess#92.
- Workspace, Cargo.lock and all ten plugin manifests move to 0.14.12.
- task check: 66 + 2 + 52 tests passed; agentplugins-check valid.

Refs: #32, #33
Release 0.14.12: ESS skills start from an existing spec; plans name the other host (#32, #33)
- New skill ess:hardening: eight techniques for after a conformance
  suite is green, cheapest first with the design review early, and the
  rule that a check nobody has seen fail is not evidence.
- References: a procedure and a defect to plant per technique, the
  reference-model pattern (to ship as ess features, beyond10x/ess#114),
  a design-review brief and spec-diff classification guidance.
- ess:conformance offers the catalogue on a green suite, and
  ess:testing-conformance links it from its mutation section; the
  checker, README and site list the new skill.

Refs: #35
- CHANGELOG section for #35.
- Workspace, Cargo.lock and all ten plugin manifests move to 0.14.13.

Refs: #35
Release 0.14.13: ess:hardening, a specification-hardening catalogue (#35)
- PR #9's release commit 683b26a was never the released 0.10.0: the
  tag 0.10.0 points at 514ef9e, which main already contains, and main
  has since shipped 0.11.0 through 0.14.13.
- Recorded as merged with main's tree unchanged (merge strategy ours),
  so no later release is rolled back and the PR's history is kept.
@b10x-bot
b10x-bot Bot merged commit ed58e9e into main Sep 26, 2026
5 of 6 checks passed
@b10x-bot
b10x-bot Bot deleted the release/0.10.0 branch September 26, 2026 08:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant