Skip to content

R3: establish primitive-boundary topology - #8

Open
Riverbraid wants to merge 1 commit into
mainfrom
r3/primitive-boundary-core
Open

R3: establish primitive-boundary topology#8
Riverbraid wants to merge 1 commit into
mainfrom
r3/primitive-boundary-core

Conversation

@Riverbraid

Copy link
Copy Markdown
Owner

R3 scope

Integrate the exact read-only-reconciled R3 branch for Riverbraid/Riverbraid-Core into main.

  • Base: main @ b5c8cde0ebb56ac98bc738545a8e80c10c67b191
  • Head: r3/primitive-boundary-core @ 6fc03e99b0326830f3edc1ecbdddabf510a21a02
  • Set003 sequence: 1
  • S11 reconciliation: PASS_R3_BRANCH_SET_READY_FOR_SEPARATE_PR_REVIEW

This PR uses the exact S11-selected R3 branch r3/primitive-boundary-core at 6fc03e99b0326830f3edc1ecbdddabf510a21a02 for Set003 sequence 1.

Set003 operation classes: COPY_EXISTING_BLOB=13, CREATE_PATH=3, DELETE_PATH=9, REPLACE_PATH=7.

Boundary

Creating this PR does not merge it and does not authorize merge, ref movement, branch deletion, tagging, release creation, repository settings changes, or any other mutation. It does not claim truth, trust, evidentiary weight, legitimacy, certification, safety, production readiness, adoption, or external validation. Repository-specific authority and experimental/noncontrolling labels remain exactly scoped as already reviewed.

@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: 6fc03e99b0

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

Comment thread mechanical-verify.mjs
Comment on lines +100 to +101
subjectCommit = git(["rev-parse", "HEAD"]);
subjectTree = git(["rev-parse", "HEAD^{tree}"]);

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 Reject dirty worktrees before attributing a result

When any required or evidence file differs from the checked-out commit, the checks read and hash the working-tree bytes, but these lines still label the result with HEAD and HEAD^{tree}. For example, modifying README.md locally still produces PASS for the unchanged commit, so the emitted evidence can falsely attest to bytes that commit never contained. Either evaluate paths directly from the reported tree or fail when tracked/untracked state can affect the checks.

Useful? React with 👍 / 👎.

Comment thread mechanical-profile.json
Comment on lines +4 to +5
"cluster-manifest-v2.json",
"constellation-audit.mjs",

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 Migrate the remaining legacy verifier surface

After these legacy dependencies are removed from the root, the still-current root verify.mjs continues to require cluster-manifest-v2.json and constellation-audit.mjs; running it now exits 1 and overwrites verify-output.json with REQUIRED_FILES_MISSING. Until it is updated or archived alongside its dependencies—and the already tracked stale verify-output.json is handled—existing consumers of the repository's conventional verifier see either a failure or a VERIFIED artifact naming files that no longer exist.

Useful? React with 👍 / 👎.

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.

1 participant