Skip to content

chore: carry the template's prose-token documents verbatim (mint-verbatim sync) - #24

Closed
hyperpolymath wants to merge 1 commit into
mainfrom
fix/mint-verbatim-documents
Closed

hyperpolymath wants to merge 1 commit into
mainfrom
fix/mint-verbatim-documents

Conversation

@hyperpolymath

Copy link
Copy Markdown
Owner

Owner ruling relayed by the sweep session: carry the template's prose-token documents verbatim, now, as one small PR (not the full template delta).

What it does: syncs .machine_readable/mint-verbatim.txt from the template (rsr-template-repo main d183b32, which lists the six prose-token documents since rsr-template-repo#375) and makes the documents on that list byte-identical to the template. Six documents: CHANGELOG.adoc, docs/reports/compliance/RSR-TEMPLATE-DAMAGE-2026-10-30.adoc, docs/status/TEST-NEEDS.adoc, scripts/survey-template-damage.sh, scripts/check-mint-tokens.sh, tests/aspect_tests.sh. On bactrian main three of them already equal the template (the damage report, the survey script, check-mint-tokens.sh); the PR therefore changes four files: the list, CHANGELOG.adoc (a template-name reference that the mint had rewritten), TEST-NEEDS.adoc (title and one converted-placeholder sentence), tests/aspect_tests.sh (the banner token). Verified with cmp against the template.

Local effect: the prose-token reds are gone for these files. check-mint-tokens.sh and check-no-placeholders.sh still exit 1 on this branch, now only for README.adoc ({{OWNER}} {{REPO}}) and {{project}} in the Abi files. Those are the token fills in #11 and are not touched here.

Stacking with #11 and merge order. #11 rewrote the same six documents (the damage report, the survey script and check-mint-tokens.sh differ from the template there; CHANGELOG, TEST-NEEDS and aspect_tests differ too). So this PR and #11 touch the same lines of those files and will conflict whichever merges second. #11 sits on a guarded branch (no update push). Recommended order: merge this PR first, then replace #11 with a regenerated #11' that leaves those documents alone (same replacement method as bactrian#23); or merge #11 first and re-take these six files from the template afterwards (a one-commit overlay). Tell me which and I will build it. In the CI-proof union I apply this PR as an overlay after #11, so the end state is the same either way.

Not run: CI on this branch. One push to a new branch name; output has no "Bypassed" (the guard for the name lists code_coverage).

https://claude.ai/code/session_0136P7Zm6f3TYUpUuzGd5KAQ


Generated by Claude Code

Syncs .machine_readable/mint-verbatim.txt from the template (the list now has the
six prose-token documents) and brings the documents on it that differ here back
to the template's bytes: CHANGELOG.adoc, docs/status/TEST-NEEDS.adoc,
tests/aspect_tests.sh. The damage report, survey-template-damage.sh and
check-mint-tokens.sh already equal the template on main. The mint had rewritten
the template name or the project-name brace token inside their prose; the
mint-token and placeholder gates skip files on the list.

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 008eea6.

Files selected for processing: 4

  • .machine_readable/mint-verbatim.txt
  • CHANGELOG.adoc
  • docs/status/TEST-NEEDS.adoc
  • 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

@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:48:22.339361Z 008eea6 Draft marked ready
🔒 Security Review ✅ Completed 2026-11-14T16:48:00.784299Z 008eea6 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: 008eea697b

ℹ️ 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.

P1 Badge Remove the stale Julia test from the verbatim manifest

Every non-chain just repo-init now aborts before prompting or modifying files because repo-init.just validates each manifest entry with [ -f "$_v" ] || exit 1, while tests/workflows/julia_library_test.sh does not exist anywhere in the target commit's tracked tree. Either include the referenced test or remove this entry so ordinary template instantiation remains possible.

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.

Verified, and this one is my miss. The template's mint-verbatim.txt lists tests/workflows/julia_library_test.sh (the template has the file), and repo-init.just line 184 exits when a listed file is absent. This repository does not have it. Checked every entry of the 21 on this head: this is the only missing one. The fix is to carry the template's file byte-identical. I cannot push it to this branch: its guard lists a code-coverage rule that an update push would bypass, and I do not bypass gates. It will go in as a replacement from a new branch name once the sweep agrees (and #26, stacked on this, moves with it). Left open until then.


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 in the aspect-test banner

Running just aspect in this repository now prints the literal {{PROJECT}} in its heading instead of the repository name. This also persists in future minted children because the same commit adds tests/aspect_tests.sh to mint-verbatim.txt, excluding the entire script from both substitution and leftover-placeholder checks; preserve the lowercase fixture in the comment without leaving an active banner token.

Useful? React with 👍 / 👎.

@hyperpolymath hyperpolymath Nov 14, 2026 •

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.

Verified, and the cause is upstream, not this PR. The template's own tests/aspect_tests.sh line 42 carries the same upper-case project token and is listed verbatim, so every minted repository prints the literal token. This PR must keep the file byte-identical to the template, so I am not editing it here. Fixed at source: rsr-template-repo#390 takes the name from the directory at run time and adds a guard test. This repository gets it with the next template sync.


Generated by Claude Code

@github-actions

Copy link
Copy Markdown

Hypatia grid green

🟢 clean · commit 008eea697bda · run 43617224931 · scope: this change (4 file(s))

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

Unique graded findings across gating and advisory rows: 0 (0 reporter observations; 0 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 🟠 indeterminate 0 0 0 0 — no comparable baseline (no prior PR grid or unreadable snapshot)
pons asinorum advisory 🟠 indeterminate 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 🟠 indeterminate 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 🟠 indeterminate 0 0 0 0 — 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 🟠 indeterminate 0 0 0 0 — 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: not_run — no status envelope was produced
  • 🟠 indeterminate: no status envelope was produced
pons asinorum: not_run — no status envelope was produced
  • 🟠 indeterminate: no status envelope was produced
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): not_run — enrolled, but no report-back was received
  • 🟠 indeterminate: enrolled, but no report-back was received
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): not_run — enrolled, but no report-back was received
  • 🟠 indeterminate: enrolled, but no report-back was received
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): not_run — enrolled, but no report-back was received
  • 🟠 indeterminate: enrolled, but no report-back was received
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 in favour of #28, which carries the same four files plus tests/workflows/julia_library_test.sh (the one manifest entry this PR listed but did not carry; Codex P1). The push guard on this branch lists a code-coverage rule that an update push would bypass, so the fix goes in as a replacement. The aspect-test banner finding is fixed at source in rsr-template-repo#390. The branch stays for the owner to delete.


Generated by Claude Code

hyperpolymath added a commit that referenced this pull request Nov 14, 2026
…lia test (replaces #24) (#28)

* chore: carry the template's prose-token documents verbatim

Syncs .machine_readable/mint-verbatim.txt from the template (the list now has the
six prose-token documents) and brings the documents on it that differ here back
to the template's bytes: CHANGELOG.adoc, docs/status/TEST-NEEDS.adoc,
tests/aspect_tests.sh. The damage report, survey-template-damage.sh and
check-mint-tokens.sh already equal the template on main. The mint had rewritten
the template name or the project-name brace token inside their prose; the
mint-token and placeholder gates skip files on the list.

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

* chore: carry tests/workflows/julia_library_test.sh verbatim

mint-verbatim.txt lists it (synced from the template at d183b32) and
repo-init.just exits on a listed file that is absent. Carry the template's
file byte-identical. All 21 manifest entries now exist.

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

---------

Co-authored-by: Claude <noreply@anthropic.com>
hyperpolymath added a commit that referenced this pull request Nov 14, 2026
…eplaces #26, needs the #24 replacement) (#29)

* chore: carry the template's prose-token documents verbatim

Syncs .machine_readable/mint-verbatim.txt from the template (the list now has the
six prose-token documents) and brings the documents on it that differ here back
to the template's bytes: CHANGELOG.adoc, docs/status/TEST-NEEDS.adoc,
tests/aspect_tests.sh. The damage report, survey-template-damage.sh and
check-mint-tokens.sh already equal the template on main. The mint had rewritten
the template name or the project-name brace token inside their prose; the
mint-token and placeholder gates skip files on the list.

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

* chore: carry tests/workflows/julia_library_test.sh verbatim

mint-verbatim.txt lists it (synced from the template at d183b32) and
repo-init.just exits on a listed file that is absent. Carry the template's
file byte-identical. All 21 manifest entries now exist.

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

* chore: drop the retired .cursorrules and .windsurfrules

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0136P7Zm6f3TYUpUuzGd5KAQ
(cherry picked from commit a7de0af)

* chore: remove the stale build/docs-seed hypatia exemption and refresh the rule order

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0136P7Zm6f3TYUpUuzGd5KAQ
(cherry picked from commit ba3baa5)

* docs: fill the README repo-init sentence with this repository's identity

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0136P7Zm6f3TYUpUuzGd5KAQ
(cherry picked from commit 523eeba)

* fix(abi): fill the foreign-library tokens in Foreign.idr and Types.idr

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0136P7Zm6f3TYUpUuzGd5KAQ
(cherry picked from commit 7f7e602)

* docs: regenerate the repository map

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

---------

Co-authored-by: Claude <noreply@anthropic.com>
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