Repository navigation
fix: remove stale banned gen-v-connector V-lang recipe - #5
Merged
Merged
Conversation
Held consumer sweep following rsr-template-repo PR #22, which removed the banned gen-v-connector V-lang connector-scaffold recipe from the template. This repo carried a pre-PR#22 copy of that drift recipe. Removes the "Generate a V-lang connector scaffold from the Groove manifest" Justfile recipe and its full body (the connectors/v-*/ generator and embedded main.v heredoc). V-lang ban-enforcement assets (check-no-vlang.sh, estate-rules workflow, 6a2/PLAYBOOK.a2ml) are intentionally left untouched: they contain the gen-v-connector/vlang string as a detection pattern. The legitimate groove-setup and verify-template recipes and the GROOVE & V-TRIPLE SETUP section header are unchanged.
hyperpolymath
added a commit
that referenced
this pull request
Sep 17, 2026
…ws (#65) Restore working CI through shared source repairs and immutable dependency locks. The standards reusable workflows now use e9fa12b965897f485f8ec143e048a424b52f689a from hyperpolymath/standards#764. The shared scanner fetches and verifies the exact revision used for its cache key, including cache hits. SSH mirrors verify independently approved host fingerprints before exporting strict SSH configuration or pushing. Optional mirror credentials are mapped explicitly. Canonical metadata is under .machine_readable/descriptiles/. Session coordination and custom checks are actual Nickel records. CI installs checksum-verified Nickel and evaluates them; envelope-aware typechecking has both passing and deliberately failing controls. The inactive E2E scaffold is a template, and the local E2E command reports that implementation is required. Action dependencies use GitHub's runtime-enforced actions.lock mechanism. The authoritative gh actions-lock tool verifies the exact commits, including transitive dependencies: https://github.com/github/gh-actions-lock#how-it-works . Inline mutable-looking tags do not imply mutable execution under this mechanism. Sonar's inline-SHA findings were classified individually after full lock verification; no rule-wide exclusion was added. Review disposition: the scanner/cache and mirror trust findings are fixed at source. Retired AGENTIC and anchor references and the directory-tree documentation are corrected. The earlier request to restore 8f2ee508 is superseded: that revision predates these security fixes. Local initialisation explicitly defers Nickel validation when Nickel is unavailable; CI always provisions it and requires validation. Also consumes the merged K9 archive repair (#43) and the merged CI/CD suite manifest gate (#5), whose valid/invalid controls pass. Pull-request triggers include stacked PR targets. This PR remains stacked on #64. The .envrc project name deliberately identifies this instantiated scientific repository. Restoring a template placeholder here would make the active project configuration incorrect; reusable minting behavior belongs in rsr-template-repo. Validation: workflow conventions and session Nickel evaluation pass; empty/malformed Nickel controls prove rejection. The CI/CD suite now runs real maintained A2ML/K9 structure validators, and the source tests establish their failure behavior. This is not a proof of full K9 semantics or production deployment. --------- Signed-off-by: Jonathan D.A. Jewell <6759885+hyperpolymath@users.noreply.github.com> Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com> Co-authored-by: Jonathan D.A. Jewell <6759885+hyperpolymath@users.noreply.github.com> Co-authored-by: Mistral Vibe <vibe@mistral.ai> Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com> Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: Claude Opus 5 <noreply@anthropic.com> Co-authored-by: rhodibot <rhodibot@hyperpolymath.dev> Co-authored-by: Arena Agent <bot@arena.ai>
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.
This is the held consumer sweep following
rsr-template-repoPR #22, which removed the bannedgen-v-connectorV-lang connector-scaffold recipe from the template. This repo carried a pre-PR#22 copy of that drift recipe.Removed
gen-v-connectorJustfile recipe (the "Generate a V-lang connector scaffold from the Groove manifest" recipe and its full body, including theconnectors/v-*/generator and embeddedmain.vheredoc).Preserved
scripts/check-no-vlang.sh, estate-rules workflow,6a2/PLAYBOOK.a2ml), where present, legitimately contains thegen-v-connector/vlangstring as a detection pattern and is left intact.groove-setupandverify-templaterecipes and theGROOVE & V-TRIPLE SETUPsection header (which they share) are unchanged.Justfile remains syntactically valid (
just --listsucceeds).🤖 Generated with Claude Code