chore(tooling): centralize library verification - #17
Merged
Conversation
Adopt the shared immutable tooling contract while retaining queue-owned broker fixtures and content-addressed verification evidence. Impact: none Affects: github.com/faustbrian/go-queue/queueservice Affects: github.com/faustbrian/go-queue/rabbitmq
Prove permanent failures retain their original code when the delivery attempt also reaches the retry limit. Impact: none Affects: github.com/faustbrian/go-queue/rabbitmq
Pin the independently verified shared tooling release and retain only root-module checkpoints in the root mutation bootstrap archive. Impact: none Affects: github.com/faustbrian/go-queue/queueservice Affects: github.com/faustbrian/go-queue/rabbitmq
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.
Centralizes the queue repository verification contract on immutable
go-library-toolsv1.0.6. Queue-owned broker fixtures, API baselines,and content-addressed mutation evidence remain local so shared tooling
does not alter runtime APIs or backend behavior.
The RabbitMQ integration fixture remains CI-only and runs through the
repository-owned operation contract.