docs(parity): record the non-BuildKit Feature-staging gap as an open nonconformance - #720
Merged
Conversation
…nonconformance Filing issue 719 put the `Ledger (issue coverage)` check into the state it exists to catch: a behavioral-scope issue asserting a deacon-vs-reference difference with no row citing it. Verified red before this commit and green after, rather than assumed. The row carries both measured axes — compose Feature builds under podman, where the provider runs with DOCKER_BUILDKIT=0, and `--buildkit never` on plain docker, where deacon refuses cleanly rather than failing. The second is worth stating precisely: the refusal is honest and fail-fast, so it is not a defect on its own terms; it is the same missing capability wearing a better error. It also records what is deliberately NOT filed. The other three podman-lane exclusions are buildx exporter gaps, and `podman buildx version` printing `buildah 1.33.7` with exit 0 means the reference's own regex detection would reach the same wrong conclusion and pass the same rejected flags. Same failure on both sides is not a divergence, and writing that down is what stops it being re-investigated. Census: 233 recorded behaviors, 1 open nonconformance. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_016SFzA2sTh2EpX8MZU3TWNS
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
1 participant
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.
Filing #719 put the
Ledger (issue coverage)check into exactly the state it exists to catch — a behavioral-scope issue asserting a deacon-vs-reference difference with no row citing it:Verified red before this commit and green after (
16 open issue(s) checked, every obligation discharged), rather than assumed.What the row records
Both measured axes of the gap:
the classic builder doesn't support additional contexts, because podman runs its external compose provider withDOCKER_BUILDKIT=0. Onlybuild:-shape services; theimage:shape passes.--buildkit neveron plain docker — deacon refuses withInstalling Features requires BuildKit, which the current settings disable.That second one is worth stating precisely rather than lumping in: the refusal is honest and fail-fast, so it is not a defect on its own terms. It's the same missing capability wearing a better error. I'd assumed it was a silent failure until I ran it.
And what is deliberately not filed
The other three podman-lane exclusions are buildx exporter gaps.
podman buildx versionprintsbuildah 1.33.7and exits 0, so the reference's own regex detection (dockerUtils.ts:245) would reach the same wrong conclusion, emitbuildx build, and pass flags buildah rejects. Same failure on both sides is not a divergence — and writing that down is what stops it being re-investigated in three months.Census: 233 recorded behaviors, 1 open nonconformance.
🤖 Generated with Claude Code
https://claude.ai/code/session_016SFzA2sTh2EpX8MZU3TWNS