Skip to content

CI proof only, do not merge: union v2 (#11 #13 #14 #15 #16 #19, pin, #23, #24) - #25

Closed
hyperpolymath wants to merge 9 commits into
mainfrom
ci-proof/union-bactrian-v2
Closed

hyperpolymath wants to merge 9 commits into
mainfrom
ci-proof/union-bactrian-v2

Conversation

@hyperpolymath

Copy link
Copy Markdown
Owner

CI proof only, do not merge. Union v2 for bactrian, on main d5e5111: #11, #13, #15, #16, #19, #14, the Hypatia pin (#21), the replacement proof-status PR (#23, which replaces the closed #17), and the verbatim documents (#24) applied as an overlay commit after #11 (a cherry-pick of #24 conflicts with #11 on .machine_readable/mint-verbatim.txt, which is the stacking conflict described on #24). Nine signed commits.

Local gates on this tree: check-root-shape.sh, check-no-placeholders.sh, check-internal-links.sh, check-mint-tokens.sh, check-container-pins.sh all exit 0. CI result not seen yet. One push to a new branch name, output has no "Bypassed". Will be closed after the result is read; branch left for the owner.

https://claude.ai/code/session_0136P7Zm6f3TYUpUuzGd5KAQ


Generated by Claude Code

… files

The upgrade kept the repo's old mint-verbatim list, so new template files
that carry {{TOKEN}} text failed the placeholder gates. The list now comes
from the template, minus entries for files this repo does not have. The
tokens in the other new or changed files are filled the way the mint fills
them. The retired .cursorrules and .windsurfrules are removed. The
build/docs-seed exemption and the matching structural_drift entry in the
Hypatia rule-order policy are removed, as the mint does, because this repo
has no build/docs-seed. The repo map was regenerated.

CLAUDE.md, the arrival pack, licence files, deeds and :repo-uuid are
untouched.

Co-Authored-By: Claude <noreply@anthropic.com>
(cherry picked from commit f1a5e50)
The container-templates directory entry on line 228 was 1159 octets,
over the 998-octet DEED line cap. This splits it onto three lines,
copied from the current template deed (lines 223 to 225). No words
change. Only line breaks and indentation differ.

The owner approved this one deed edit. No hash, receipt or pin covers
deed lines.

Co-Authored-By: Claude <noreply@anthropic.com>
(cherry picked from commit 0e69041)
The two issue template links in .github/CONTRIBUTING.md resolved to
.github/.github/..., and the templates are .yml files, not .md. The
SECURITY.md link in docs/troubleshooting.adoc pointed at the repo root,
but the file is .github/SECURITY.md.

The owner approved this docs fix. No gate or allowance change.

Co-Authored-By: Claude <noreply@anthropic.com>
(cherry picked from commit 9f58659)
The template added a module-level dupeZ helper to main.zig after this
repository was cut from it. The template upgrade added
tests/ffi_strings_test.sh, which calls that helper, but did not apply
the matching main.zig change. The test fails to compile with "use of
undeclared identifier 'dupeZ'".

This file was identical to the base mint, so the change is the template
update applied with the project name filled in. Nothing else changes.

Co-Authored-By: Claude <noreply@anthropic.com>
(cherry picked from commit 72633ad)
Both FROM lines in build/container/Containerfile resolve to the Chainguard
wolfi-base OCI index digest, written as digest only: SonarCloud rule
docker:S8431 rejects a reference carrying both a tag and a digest, and the
estate gate accepts any @sha256:<64 hex> reference.

Co-Authored-By: Claude <noreply@anthropic.com>
(cherry picked from commit 88a5dde)
The template root-shape gate requires LICENSE.adoc. This adds it with
two lines. Line 1 is the SPDX identifier for the dual licence. Line 2
is a plain-text note that MPL-2.0 covers code and CC-BY-SA-4.0 covers
prose. It is not an SPDX tag, because REUSE has no header tag for a
code and prose split.

docs/architecture/REPOSITORY-MAP.adoc is regenerated with just
repo-map, because the map lists root files and goes stale when
LICENSE.adoc is added.

Co-Authored-By: Claude <noreply@anthropic.com>
(cherry picked from commit 3f4490e)
dogfood-gate.yml pinned Hypatia to be98f74, 112 commits before hypatia#1062
(37b8d01, the OTP segfault in the RSR oracle). The template moved to 51539ab in
rsr-template-repo#369; this is the same three-line change (ref, comment, cache
key). OTP 27.3.4.19 is already in the file. scripts/check-lock-sync.sh passes
before and after (rc=0), so actions.lock needs no change: the ref is a
checkout ref, not a uses: entry.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0136P7Zm6f3TYUpUuzGd5KAQ
(cherry picked from commit d383564)
…m, with the seven obligations as open rows

Replaces #17. The template-form PROOF-STATUS.adoc, with the {{PROJECT}} title
token filled (bactrian), and the seven mandatory obligations from
PROOF-NEEDS.adoc (ABI-1..5, TP-1, TP-2) restated as rows with status token open,
PWG ungraded and no receipt, so the census sees open obligations. No row claims a
proof. Row text is copied from PROOF-NEEDS.adoc. witness-map.ncl is unchanged
from #17.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0136P7Zm6f3TYUpUuzGd5KAQ
(cherry picked from commit afea451)
…ctrian#24's end state)

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0136P7Zm6f3TYUpUuzGd5KAQ
@coderabbitai

coderabbitai Bot commented Nov 14, 2026 •

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

You'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 31 minutes.

Check out review usage here.

View limit details

Limit details: You’ve used the included review currently available.

Learn how review limits work.

Review configuration:

Run configuration

Commits

Reviewing files that changed from the base of the PR and between d5e5111 and 5bfc23b.

Files selected for processing: 21

  • .cursorrules
  • .github/CONTRIBUTING.md
  • .github/workflows/dogfood-gate.yml
  • .hypatia-ignore
  • .machine_readable/coaptation/witness-map.ncl
  • .machine_readable/mint-verbatim.txt
  • .machine_readable/policies/hypatia-rule-order.json
  • .windsurfrules
  • CHANGELOG.adoc
  • LICENSE.adoc
  • README.adoc
  • bactrian_chora.deed
  • build/container/Containerfile
  • docs/architecture/REPOSITORY-MAP.adoc
  • docs/status/PROOF-STATUS.adoc
  • docs/status/TEST-NEEDS.adoc
  • docs/troubleshooting.adoc
  • src/interface/Abi/Foreign.idr
  • src/interface/Abi/Types.idr
  • src/interface/ffi/src/main.zig
  • tests/aspect_tests.sh

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.

Share

@sonarqubecloud

Copy link
Copy Markdown

@hyperpolymath
hyperpolymath marked this pull request as ready for review November 14, 2026 16:44
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Nov 14, 2026 •

Copy link
Copy Markdown
Codex Review Summary: ✅ Completed

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-11-14T16:52:28.357972Z 5bfc23b Draft marked ready
🔒 Security Review ✅ Completed 2026-11-14T16:49:43.811407Z 5bfc23b Draft marked ready
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 5bfc23ba49

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

tests/workflows/mint_cleanup_test.sh # instruction-block fixture
tests/workflows/self_name_pass_test.sh # template-name fixtures
tests/workflows/template_conformance_test.sh # template-slug fixtures
tests/workflows/julia_library_test.sh # PACKAGE_UUID brace-token fixture

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Remove the stale verbatim-manifest entry

On any template-mode repo-init invocation, this entry makes the mint abort before writing because tests/workflows/julia_library_test.sh does not exist anywhere in the committed tree. The preflight at build/just/repo-init.just explicitly rejects every missing path listed in mint-verbatim.txt, so either restore the named test or remove/correct this entry.

Useful? React with 👍 / 👎.

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a CI proof branch and is not for merging. The finding is verified and fixed in the real PR: julia_library_test.sh is carried byte-identical in bactrian#28.


Generated by Claude Code

Comment thread tests/aspect_tests.sh

echo "═══════════════════════════════════════════════════════════════"
echo " BACTRIAN — Aspect Tests (Cross-Cutting Concerns)"
echo " {{PROJECT}} — Aspect Tests (Cross-Cutting Concerns)"

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Render the project name instead of shipping this token

Running tests/aspect_tests.sh now prints the literal {{PROJECT}}, and the newly added tests/aspect_tests.sh entry in mint-verbatim.txt excludes the entire file from both mint substitution and the placeholder gate. Consequently the token also survives unchanged in every minted child while validation still reports success; keep functional output free of fixture tokens or avoid exempting the whole script.

Useful? React with 👍 / 👎.

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a CI proof branch and is not for merging. The cause is the template's own tests/aspect_tests.sh line 42; fixed at source in rsr-template-repo#390. bactrian#28 keeps the file byte-identical to the template pin.


Generated by Claude Code

| — | — | — | —
| ID | Claim (and the artefact that proves or tests it) | Token | PWG | Rocq leg | Lean leg | Receipt

| ABI-1 | Non-null pointer proofs (`So (ptr /= 0)`) (artefact: `verification/proofs/idris2/ABI/Pointers.idr`) | open | ungraded | — | — | —

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Mark Idris engineering obligations outside the PWG ladder

All seven rows classify their obligations as ungraded, even though this document defines that value only for theory theorems and explicitly assigns n/a to engineering proofs in Idris2. The ABI and typing requirements identify these as Idris2 engineering obligations (TP-2 also says APIs are assigned to Idris2), so the estate census that consumes this table will incorrectly place them on the theory PWG ladder; use n/a for these open engineering claims.

Useful? React with 👍 / 👎.

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a CI proof branch and is not for merging. The owner ruled ungraded rows with no PWG asserted, and the template's intro paragraph says the same, while the vocabulary in the same file puts engineering proofs at n/a. The template disagrees with itself there, so the choice is for the owner at the template. Not changed.


Generated by Claude Code

@github-actions

Copy link
Copy Markdown

Hypatia grid green

🟢 clean · commit 5bfc23ba4907 · run 43618570217 · scope: this change (21 file(s))

Advisory: 11 row(s), worst 🔴 high (0 critical, 9 high in grid scope) — reported, never grading the change.

Unique graded findings across gating and advisory rows: 53 (53 reporter observations; 25 without sufficient identity to corroborate). Row counts remain per reporter; unique totals do not change gating.
Raw Hypatia alert-derived observations: 39 (code-scanning, Dependabot and secret-scanning; some may also be in SARIF; not an extra total).

Reporter Gate Status Critical High Medium Minor Since previous revision
Hypatia scan gating 🟢 clean 0 0 0 0 — no comparable baseline (no prior PR grid or unreadable snapshot)
panic-attack assail advisory 🟢 clean 0 0 0 0 — no comparable baseline (no prior PR grid or unreadable snapshot)
pons asinorum advisory 🟢 clean 0 0 0 0 — no comparable baseline (no prior PR grid or unreadable snapshot)
echidnabot advisory ⚪ not applicable 0 0 0 0 — no comparable baseline (no prior PR grid or unreadable snapshot)
rhodibot (RSR compliance) advisory 🟢 clean 0 0 0 0 — no comparable baseline (no prior PR grid or unreadable snapshot)
panicbot advisory ⚪ not applicable 0 0 0 0 — no comparable baseline (no prior PR grid or unreadable snapshot)
sustainabot advisory ⚪ not applicable 0 0 0 0 — no comparable baseline (no prior PR grid or unreadable snapshot)
glambot (presentation quality) advisory 🔵 minor 0 0 0 11 — no comparable baseline (no prior PR grid or unreadable snapshot)
seambot advisory ⚪ not applicable 0 0 0 0 — no comparable baseline (no prior PR grid or unreadable snapshot)
finishingbot (release readiness) advisory 🔴 high 0 9 31 2 — no comparable baseline (no prior PR grid or unreadable snapshot)
cipherbot advisory ⚪ not applicable 0 0 0 0 — no comparable baseline (no prior PR grid or unreadable snapshot)
accessibilitybot advisory ⚪ not applicable 0 0 0 0 — no comparable baseline (no prior PR grid or unreadable snapshot)
Hypatia scan: 4 finding(s)
  • 4 further finding(s) in files this change does not touch: reported, not graded (0 critical, 0 high).
panic-attack assail: 18 finding(s)
  • 18 further finding(s) in files this change does not touch: reported, not graded (0 critical, 0 high).
pons asinorum: 9 finding(s)
  • 9 further finding(s) in files this change does not touch: reported, not graded (0 critical, 0 high).
echidnabot: not_applicable — template default: enrol once the repository carries proofs and an ECHIDNA engine is configured
  • ⚪ not applicable: template default: enrol once the repository carries proofs and an ECHIDNA engine is configured
rhodibot (RSR compliance): 11 finding(s)
  • 11 further finding(s) in files this change does not touch: reported, not graded (0 critical, 10 high).
panicbot: not_applicable — panic-attack is already graded by the verdict grid's own panic-attack row, from static-analysis-gate.yml evidence; enrolling panicbot would report one scanner twice and give two rows that can disagree
  • ⚪ not applicable: panic-attack is already graded by the verdict grid's own panic-attack row, from static-analysis-gate.yml evidence; enrolling panicbot would report one scanner twice and give two rows that can disagree
sustainabot: not_applicable — reserved fleet slot; no adapter exists (gitbot-fleet bots/sustainabot/README.adoc)
  • ⚪ not applicable: reserved fleet slot; no adapter exists (gitbot-fleet bots/sustainabot/README.adoc)
glambot (presentation quality): 88 finding(s)
  • info GS-001 — Install git-seo for comprehensive SEO analysis: https://github.com/hyperpolymath/git-seo
  • info MACH-007 — ECOSYSTEM.scm not found in .machine_readable/ directory.
  • info MACH-007 — META.scm not found in .machine_readable/ directory.
  • info MACH-007 — STATE.scm not found in .machine_readable/ directory.
  • info MACH-005 — No robots.txt found. Consider adding one for crawler control.
  • info VIS-005 — README.adoc:8 — Line 209 characters exceeds max length of 80.
  • info VIS-005 — docs/architecture/REPOSITORY-MAP.adoc:26 — Line 81 characters exceeds max length of 80.
  • info VIS-005 — docs/status/PROOF-STATUS.adoc:8 — Line 82 characters exceeds max length of 80.
  • info VIS-005 — docs/status/TEST-NEEDS.adoc:13 — Line 120 characters exceeds max length of 80.
  • info VIS-005 — docs/troubleshooting.adoc:3 — Line 94 characters exceeds max length of 80.
  • info VIS-005 — CHANGELOG.adoc:45 — Line 89 characters exceeds max length of 80.
  • 77 further finding(s) in files this change does not touch: reported, not graded (0 critical, 2 high).
seambot: not_applicable — template default: enrol once a seam register exists at spec/seams/seam-register.json
  • ⚪ not applicable: template default: enrol once a seam register exists at spec/seams/seam-register.json
finishingbot (release readiness): 177 finding(s)
  • high V1-DOC-ROADMAP.adoc — Required file ROADMAP.adoc not found (Project roadmap).
  • high TOOL-001 — .tool-versions file not found for asdf/mise version management.
  • high SCM-001-NEUROSYM.scm — Required SCM file NEUROSYM.scm not found (Neurosymbolic AI documentation).
  • high SCM-001-AGENTIC.scm — Required SCM file AGENTIC.scm not found (Agentic AI integration documentation).
  • high SCM-001-PLAYBOOK.scm — Required SCM file PLAYBOOK.scm not found (Operational playbooks and procedures).
  • high SCM-001-ECOSYSTEM.scm — Required SCM file ECOSYSTEM.scm not found (Project's place in the ecosystem).
  • high SCM-001-META.scm — Required SCM file META.scm not found (Meta-level information and architectural decisions).
  • high SCM-001-STATE.scm — Required SCM file STATE.scm not found (Project state and progress tracking).
  • high PH-100 — Found 127 placeholders, exceeds maximum allowed (0)
  • medium V1-COM-CONTRIBUTING.md — CONTRIBUTING.md file not found (Contribution guidelines).
  • medium V1-COM-CODE_OF_CONDUCT.md — CODE_OF_CONDUCT.md file not found (Code of conduct).
  • medium V1-SEC-001 — SECURITY.md not found for responsible disclosure.
  • medium TEST-001 — Could not determine if this is a Rust or Deno project.
  • medium REL-004 — No SECURITY.md file found
  • medium CLM-006 — CHANGELOG.adoc — Documentation references non-existent file: e2e.yml.template
  • medium CLM-006 — CHANGELOG.adoc — Documentation references non-existent file: hypatia-scan.yml
  • medium CLM-006 — CHANGELOG.adoc — Documentation references non-existent file: dogfood-gate.yml
  • medium CLM-006 — CHANGELOG.adoc — Documentation references non-existent file: security-policy.yml
  • medium PH-001 — build/container/Containerfile:110 — Found 'TODO' in: # TODO: Copy compiled binary/release from builder stage.
  • medium PH-001 — build/container/Containerfile:71 — Found 'TODO' in: # TODO: Copy source files and build
  • 22 more graded finding(s); see the structured report in the artifact.
  • 135 further finding(s) in files this change does not touch: reported, not graded (0 critical, 4 high).
cipherbot: not_applicable — template default: enrol once the repository implements cryptography
  • ⚪ not applicable: template default: enrol once the repository implements cryptography
accessibilitybot: not_applicable — template default: enrol once the repository serves HTML
  • ⚪ not applicable: template default: enrol once the repository serves HTML

Scope: static findings reported by each row's tool at the named commit. The table grades only findings in files this change touches, so the colour answers "does this change introduce anything?", not "what does the whole repository still carry?". Standing findings are counted in each accordion and in report.json; the baseline filter remains the place where acknowledged debt is recorded. The lane state is the worst GATING row; advisory rows are listed and counted but never set it. Purple, red, yellow and blue grade the worst GRADED finding present; orange is evidence missing, malformed or a scanner that did not run; grey is an explicit scope exclusion with its reason. No row is a security certification. report.json, badge.json and the raw findings are in the verdict-grid artifact on the linked run.

Copy link
Copy Markdown
Owner Author

Closing: this PR is a CI proof only (its title says do not merge), not a change to land. It was opened to show that the union of the listed PRs passes CI, and it was marked ready for review by mistake. The real changes are in the PRs it lists. I am leaving the branch in place for the owner to delete; nothing was deleted and nothing was merged.


Generated by Claude Code

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants