Repository navigation
chore(k9): retire the k9iser output and manifest - #223
Closed
hyperpolymath wants to merge 9 commits into
Closed
hyperpolymath wants to merge 9 commits into
hyperpolymath wants to merge 9 commits into
Conversation
generated/k9iser/cargo-manifest.k9 and container-build.k9 are k9iser output in a [must]/[trust] section format that predates K9 contract v1.0.0 (D173): no K9! envelope, no pedigree, not a Nickel component. The Validate K9 contracts gate rejects both, nothing in this repository reads them, echidna already gitignores the same directory, and no k9iser repository exists in the estate any more. The two gate messages that told people to run k9iser now point at the K9 contract spec. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_019a95kk88TZ1iegsBK3kox3
Contributor
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 5 minutes. View limit details
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
hyperpolymath
marked this pull request as ready for review
October 19, 2026 18:43
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
hyperpolymath
added this pull request to stack #224
October 19, 2026 20:48
Contributor
|
Add Carrot credits or activate Agent usage billing to use Autofix |
hyperpolymath
pushed a commit
that referenced
this pull request
Oct 19, 2026
…, and update K9 contracts and dependencies" This reverts commit afd3da7, pushed by CodeRabbit's CI-fix agent. This PR is the lock repair at the base of a stack; the clippy fixes, the readiness doc paths and the K9 retirement are the next three PRs (#220, #221, #223), and a second copy here would conflict with them. The commit also rewrote generated/k9iser/*.k9 to make them conform, which the owner has ruled the other way: k9iser is retired and #223 deletes those files. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_019a95kk88TZ1iegsBK3kox3
… k9iser Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_019a95kk88TZ1iegsBK3kox3
…it regenerated stays deleted Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_019a95kk88TZ1iegsBK3kox3
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_019a95kk88TZ1iegsBK3kox3
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_019a95kk88TZ1iegsBK3kox3
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_019a95kk88TZ1iegsBK3kox3
This was referenced Oct 20, 2026
Owner
Author
|
Superseded by the flattened direct-to-main PR #233. Its combined tree is preserved there, and the full PR CI suite has passed; closing this stacked child avoids the base-branch restriction. |
hyperpolymath
added a commit
that referenced
this pull request
Oct 20, 2026
## Summary Flatten the final combined tree of the readiness, dependency-audit, and K9-retirement stack onto current `main`. This direct-to-main PR avoids the GitHub stacked-PR base restriction that blocked retargeting the first child. - Clear the remaining Rust lint/readiness diagnostics fixes and update docs references. - Carry the dependency lockfile/advisory updates and workflow lock changes. - Retire the K9iser manifest and generated outputs as intended. - Preserve the final combined tree from the previous stack tip (#223), without carrying its stale branch ancestry. This supersedes the stacked series #220–#223 if this PR passes review and CI. ## Validation - `git diff --check` — passed. - `cargo test --all-targets` — not run locally; this environment has no `cargo` executable. Use the PR CI result as the test gate. - No merge performed; await full CI and review. Co-authored-by: arena-agent <297053741+arena-agent@users.noreply.github.com>
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.
Stacked on #222 (← #221 ← #220 ← #218). This is the K9 follow-up from #218 (comment):
Validate K9 contracts(dogfood-gate) fails ongenerated/k9iser/cargo-manifest.k9andcontainer-build.k9.Why delete rather than regenerate
[must]/[trust]/[dust]/[intend]section format. Under K9 contract v1.0.0 (standards ruling D173,1-formats/k9/spec/K9-CONTRACT-SPEC.adoc) a K9 file is a Nickel component with aK9!envelope and a pedigree; these are neither, so no validator in the estate can accept them.generated/k9iser/. echidna already lists the same directory in its.gitignore.hyperpolymath/k9iserrepository exists in the estate any more, so there is nothing to regenerate with.Change
generated/k9iser/andk9iser.tomlare removed.k9iser generate .now point at the K9 contract spec.Verification
bash .github/hooks/validate-k9.shon the branch:K9 validation passed.(1 file scanned, 0 errors).dogfood-gate.ymlstill parses.The wider finding, that every consumer repo runs a second non-canonical K9 validator and that the template repo's contractiles do not conform to contract v1.0.0, is being handled in standards, not here.
Generated by Claude Code