Changelog

All notable changes to Soleur.

v3.354.17 — 2026-10-24

Fix intermittent g1b.B7/g1b.B7a/g1b.B7c/g2b.I6/fl.walk fixture failures on CI runners: replace loose-object rm -f corruption with never-written-oid forgery, add counted SKIP (loud): plumbing for genuine environment divergence, and extend the skip-persistence monitor to observe guard-script suites.

v3.354.16 — 2026-10-24

Web Platform

  • The Inngest scheduler-link self-gate failure event now names the failing stage (phase=connect|handshake|verify|ca_file|request|status|unknown, with tcp=, tls= and verify= counters), and the deploy state carries the same token as inngest_link_selfgate_phase.
  • The Inngest runbook and the deploy-status debugging reference gain a decode table for the new fields.

v3.354.15 — 2026-10-24

  • Fix the inngest config-bundle producer so cosign sign-blob emits a bundle the pinned verify-blob consumer can load (epic #10390, defect 3): repo-pinned signing-config on the emit surface plus a verify-before-publish gate that hard-fails on anything but Verified OK.
  • Extend diagnose-inngest-verify.yml with a verbatim-error LoadJSONFromPath probe and LOAD_OK verdict so bundle rejects name the failing check.
  • Bump the cloud-init name floor 5→6 with the merge→promote ordering gate recorded.

web-v0.358.12 — 2026-10-24

Web Platform

  • The Inngest scheduler-link self-gate failure event now names the failing stage (phase=connect|handshake|verify|ca_file|request|status|unknown, with tcp=, tls= and verify= counters), and the deploy state carries the same token as inngest_link_selfgate_phase.
  • The Inngest runbook and the deploy-status debugging reference gain a decode table for the new fields.

web-v0.358.11 — 2026-10-24

  • Fix the inngest config-bundle producer so cosign sign-blob emits a bundle the pinned verify-blob consumer can load (epic #10390, defect 3): repo-pinned signing-config on the emit surface plus a verify-before-publish gate that hard-fails on anything but Verified OK.
  • Extend diagnose-inngest-verify.yml with a verbatim-error LoadJSONFromPath probe and LOAD_OK verdict so bundle rejects name the failing check.
  • Bump the cloud-init name floor 5→6 with the merge→promote ordering gate recorded.

v3.354.14 — 2026-10-24

  • Fixed: the rehearsal orphan sweeps in the scheduled drift workflow read the read-only Hetzner token only, no longer run under the Tier-B environment, and email when they fail.
  • Added: guard rows in the drift suite that pin the property and run the real step bodies.

v3.354.13 — 2026-10-24

  • Sandbox: op=masked-dir-precreate failures now raise a Sentry email alert (masked-dir-precreate-failed) tagged by dir_kind.
  • Runtime Bash synthetic: creates the four production masked dirs when absent and journals masks_created / masks_note; an over-range masks_missing journals as 5+.
  • CI: the git-data/htpasswd apt fixtures share their apt cache across containers; failure and skip lines show the apt cause first.
  • Docs: ADR-079 addendum, ADR-188 amendment, runbook alert-response and rollback sections.

v3.354.12 — 2026-10-23

  • Fixed flag-set-role so updating an existing per-segment override sends the segment id Flagsmith requires; turning a flag off for a role that already has an override no longer ends in HTTP 400.
  • Added input guards for the segment id and the on/off value, and an agent-runnable regression suite.

v3.354.11 — 2026-10-23

  • Retired four followthrough probes of closed trackers and the test rows, baselines and registry entries that named them.
  • The bearer-sweep HMAC audit population is now derived from its manifest and cross-checked by a census.

v3.354.10 — 2026-10-23

  • fix(inngest): generation anchor reads the read-only Hetzner token alone (Site C, Ref #10664)

v3.354.9 — 2026-10-23

Marketing / Docs

  • Bespoke OG image for 2026-10-23-agentic-verification-checklist-shipped — closes the social-card gap the post shipped with

Refs #10922.

v3.354.8 — 2026-10-23

  • Fixed a flaky/false-green verdict class in the playwright-mcp-redact-proxy test suite: startup-exit rows no longer race the session driver's deadline windows (new --expect-death mode with a 30s death bound), and the G1 asserts are now per-observable so the next CI failure names exactly what failed.

v3.354.7 — 2026-10-23

  • fix: capture bounded cosign stderr and add a detail= classifier on inngest config-refresh VERIFY_FAIL rows
  • feat(ci): permanent dispatch-only diagnose-inngest-verify.yml probe for the private bundle verify path
  • chore(ops): AC7 soak probe, PIR, ADR-135 addendum, runbook taxonomy

v3.354.6 — 2026-10-23

  • Apply delivery gap follower: a read-only workflow files and closes one operator issue when a cancelled apply push has no delivering run.
  • Runbook and ADR-270 addendum describe the gap issue, the dispatch command, verification, and the evidence bar for a future fix.

v3.354.5 — 2026-10-23

  • Fixed the PR terraform-plan matrix so data-read-only infra roots (e.g. apps/cla-evidence/infra) no longer produce a permanently-red plan leg; validate coverage is unchanged
  • The go-session-gates H3 row now accepts any verified resolver arm instead of requiring plugin-root-token

Closes #10715 Closes #10714

v3.354.4 — 2026-10-23

  • fix(opencode): recognise OpenCode in soleur_op_in_agent_harness and qualify the receipt path in operator-bootstrap/SKILL.md (closes #10877).

v3.354.3 — 2026-10-23

Plugin

  • Arc-synthesis blog draft + multi-channel distribution for the agentic-verification epic; content-strategy pipeline updated

Refs #10902 #10903 #10904.

v3.354.2 — 2026-10-23

  • Added an advisory CI job, affected-index-ratchet, that fails (without blocking merge) when a test suite names a tracked path the affected-index does not declare.
  • Added the shrink-only baseline of today's gaps, the ratchet runbook sections and the ADR-276 amendment.

v3.354.1 — 2026-10-23

Plugin

  • ship Phase 7 gains Step 3.9: epic-close domain-leader sweep with per-child content-disposition census
  • ship Phase 5.5 CMO gate: resumed/manual ship tails must re-run gate detection before arming merge

v3.354.0 — 2026-10-23

  • Added @soleur/opencode npm package installer (npx @soleur/opencode install) with durable payload vendoring and automated release publishing workflow.

v3.353.6 — 2026-10-23

Patch — test-instrument margin hardening, no product surface.

v3.353.5 — 2026-10-23

  • fix(ci-head-verdict): the stall clock starts at the later of the ready event and the head's first CI appearance; unreadable check-suite data reports state=error instead of a verdict

v3.353.4 — 2026-10-23

Web Platform

  • The Inngest link canary no longer fails because a Doppler snapshot line duplicates a name the deploy passes with -e; the deploy scrubs INNGEST_BASE_URL and NODE_EXTRA_CA_CERTS from the env-file first.
  • A failed canary inspect check now names which condition was off (url_count, url_value, ca_count, ca_value, inspect_failed) with fixed integer counts, and records its own deploy-state reason.

Docs

  • Runbooks, the ADR-294 addendum and the postmerge deploy-status table cover the new events and reasons.

v3.353.3 — 2026-10-23

test: row_scan_ops mutation-battery row gains a materialization probe — hidden-collection mutants now die deterministically instead of flaking on a best-of-3 CPU bound.

Closes #10724

v3.353.2 — 2026-10-23

  • The infra test runner now relays suites' SKIP (loud): lines and the rehearsal suite's terminal line into the Actions log, so the daily skip-persistence probe can read a real verdict again instead of returning TRANSIENT.
  • ADR-188 and ADR-252 record the repaired evidence path; the plan skill's sharp edges gain a bullet on verifying causal attributions against history.

v3.353.1 — 2026-10-23

  • fix(opencode): judge shell calls against the per-call workdir instead of the session directory
  • docs(opencode): name the absent operator-stage approval gate and its fail-closed consequence
  • docs(adr): amend ADR-245's supported-harness set and ADR-291's hook posture with dated, clause-scoped notes
  • docs: add the OpenCode contributor path and replace stale harness counts with named or count-free phrasing

<!-- auto-close-scanner: confirm -->

v3.353.0 — 2026-10-23

Plugin

  • New skill soleur:verification-scaffold: guardrail-corpus audit + generation/install of pre-commit, pre-push, block-stash, orphan-test, and wrapper-boundary hooks plus an advisory verification-gates.yml CI workflow, driven by a guards.tsv manifest with a parity census.
  • review / work / plan-sharp-edges SKILL bodies: three routed learnings (sibling-session staging, full regen sweep, machine-gated decision-challenges table shape); bodies trimmed to stay under merge-base-anchored byte ceilings.

web-v0.358.9 — 2026-10-23

  • Fixed flag-set-role so updating an existing per-segment override sends the segment id Flagsmith requires; turning a flag off for a role that already has an override no longer ends in HTTP 400.
  • Added input guards for the segment id and the on/off value, and an agent-runnable regression suite.

web-v0.358.8 — 2026-10-23

  • fix(inngest): generation anchor reads the read-only Hetzner token alone (Site C, Ref #10664)

web-v0.358.7 — 2026-10-23

  • Fixed a flaky/false-green verdict class in the playwright-mcp-redact-proxy test suite: startup-exit rows no longer race the session driver's deadline windows (new --expect-death mode with a 30s death bound), and the G1 asserts are now per-observable so the next CI failure names exactly what failed.

View all releases on GitHub →

Frequently Asked Questions

How often is Soleur updated?

Soleur ships continuously — updates are released when ready and tagged with semantic versioning. There is no fixed release schedule. Changes range from new agents and skills to bug fixes and documentation improvements.

How do I upgrade Soleur?

Run claude plugin update soleur@soleur-marketplace, then restart Claude Code — plugin changes apply on restart, so the update is not picked up until you do. If you installed with --scope project or --scope local, pass the same scope. Check the changelog or GitHub releases page for details on what changed.

Does Soleur use semantic versioning?

Yes. Soleur follows semantic versioning — major versions for breaking changes, minor versions for new agents or skills, and patch versions for bug fixes and documentation updates. Version labels are set during PR review and applied automatically at merge.

Stay in the loop

Monthly updates about Soleur — new agents, skills, and what we're building next.