Repository navigation
Release 0.13.0: issues #127–#130 - #132
Merged
Merged
Conversation
Add an optional `verify` identity probe to the behaviour layer: either a
`run` command whose stdout or a `url` whose 2xx body must match `expect`
(default `{commit}`; `{commit}` and `{ref}` expand to the stack side's
resolved commit and ref). It runs after `start` and before the tests in
every cycle; a mismatch fails the layer with both values, and collect and
stop still run. Without `verify` each cycle notes that the stack's code
was not verified, and every cycle notes the wall time of `start`.
Fixes #129
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01QszGCmzG1kAQaxaBvaTEyR
A literal consumers[].queue is the same at both refs, so an endpoint rename never reported message-consumer-moved. A consumer source can now set queueFrom (a regex or composed queue source) instead of queue, and optionally select, which keeps the names with a part value equal to it. The queue is resolved at each ref; no name or several names fail the layer without consumer findings. Fixes #128 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QszGCmzG1kAQaxaBvaTEyR
…it-id
An explicit-id insert the preconditions command left open now says what the
base's migrations wrote into the table: the highest explicit id (with the base
line as evidence) and whether they move its identity sequence. An optional
per-source `writers` list ({ table, files, patterns }) searches base code
outside the migrations for writers of the table. An accept entry with
`"basis": "migrations-only"` accepts the finding only while writers are
configured, none matches, and the base's highest explicit id is below the
first new id; otherwise a note says why it accepted nothing.
Fixes #130
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01QszGCmzG1kAQaxaBvaTEyR
A target captured from a configuration key (the appsettings path with `keyFrom: "appsettings"`, or a `key` group of the pattern) whose key the deploy's compose service sets (`service`, `composeFiles`) is now compared and reported as that key, e.g. `outbound-added Shop:BaseUrl`, with the interpolated variable and the file default in the message, the file line and the compose entry as evidence, and a topic that groups it with the `config` finding of the same key. A new file default under an overridden key gives no finding. readServiceEnvironment now also returns each value. Fixes #127 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QszGCmzG1kAQaxaBvaTEyR
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QszGCmzG1kAQaxaBvaTEyR
This was referenced Oct 8, 2026
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
2 participants
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.
Summary
keyFrom: "appsettings"or a(?<key>…)group) that the deploy's composeservicesets is reported by its key (Shop:BaseUrl (SHOP_BASE_URL at deploy …; file default …)), not by the file's host; the file host stays as evidence, and the finding groups with the config finding of the same key. New target fields:keyFrom,service,composeFiles.consumers[].queueFrom(+ optionalselect) resolves a consumer's queue from a queue source at each ref, so an endpoint rename reportsmessage-consumer-moved. Fails closed when the reference yields zero or several names.verifyprobe (runorurl,expectdefault{commit}) afterstartand beforetest; a mismatch fails the layer andstopstill runs. Withoutverifya note says the stack's code was not verified; the wall time ofstartis noted per cycle.insert-explicit-idgains git-only evidence (max explicit id the base migrations insert, sequence resets), optionalwritersto show no base code outside migrations writes the table, and accept entries withbasis: "migrations-only"that stop matching once the basis no longer holds.package.json,action.yml, README).Fixes #127
Fixes #128
Fixes #129
Fixes #130
Tests
New unit and e2e tests per issue (each set fails without its change). After merging all four:
vitest run1362 passed, 24 skipped;test:packpassed;tsc --noEmit,biome check .andnpm run buildclean.🤖 Generated with Claude Code
https://claude.ai/code/session_01QszGCmzG1kAQaxaBvaTEyR
Generated by Claude Code