chore: promote dev to canary (v0.1.1 prep)

[iap]

Summary

Promotes dev to canary — 69 commits since last promotion.

Key changes

• fix(contracts): CEI fix — consumedIntents set before external verifier call
• docs(contracts): THREAT_MODEL.md and KNOWN_ISSUES.md for audit preparation
• fix(docs): corrected two inaccurate invariants in THREAT_MODEL
• fix(ops): staging rehearsal pipeline fixes (working-directory, post-deploy, verifier env handoff)
• fix(ci): workflow correctness fixes
• feat(frontend): protocol info page

Verification

74 tests passing. Staging rehearsal passed on OP Sepolia.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: ed4bf7cc-0870-4535-a5c7-f15b3eea33dd

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch dev

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[iap]

Closing — replaced by #72 which resolves merge conflicts.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 8627f4be97

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

[chatgpt-codex-connector]

Strip optional .git suffix when inferring GH_REPO

The infer_repo_from_remote regex captures owner/repo.git into BASH_REMATCH[1] for the common origin forms git@github.com:owner/repo.git and https://github.com/owner/repo.git, because [^/]+ greedily consumes .git and the optional group stays empty. That makes repo become mark.git, so API calls are sent to /repos/<owner>/<repo>.git and governance verification fails even with valid credentials.

Useful? React with 👍 / 👎.

[chatgpt-codex-connector]

Avoid requiring checks from path-filtered workflows

This branch-protection baseline requires checks like Analyze (javascript-typescript) and Release Gate Container, but those workflows are configured with on.pull_request.paths filters (.github/workflows/codeql.yml and .github/workflows/contracts-release-gate-container.yml). For PRs that don't touch those paths, GitHub leaves required checks in Pending/Waiting for status to be reported, which blocks merges despite no failures.

Useful? React with 👍 / 👎.

[chatgpt-codex-connector]

Use non-greedy repo capture when parsing origin URL

The infer_repo_from_remote pattern captures owner/repo.git (including the suffix) for normal GitHub remotes like https://github.com/org/repo.git and git@github.com:org/repo.git. That makes repo become repo.git, so subsequent API calls target /repos/<owner>/<repo>.git/... and fail even with a valid GH_PAT, breaking the pre-transfer readiness check in the common setup.

Useful? React with 👍 / 👎.

[chatgpt-codex-connector]

Build release-gate image with buildx for gha cache flags

This script uses docker build together with --cache-from type=gha / --cache-to type=gha,mode=max, but Docker’s gha cache backend is documented for Buildx and is not supported by the default docker driver in standard setups. In CI this can cause the required “Release Gate Container” job to fail during image build before the gate runs.

Useful? React with 👍 / 👎.

[chatgpt-codex-connector]

Wait for supersim HTTP readiness, not just open TCP port

The integration workflow now waits only for port 8420 to accept TCP connections, which can occur before supersim’s readiness endpoint is actually healthy. wait-port supports HTTP targets specifically to require a 2xx response; dropping the http://.../ready check introduces a race where integration tests start too early and fail intermittently.

Useful? React with 👍 / 👎.

[chatgpt-codex-connector]

Strip .git suffix when inferring GH_REPO in readiness script

The origin parser captures owner/repo.git for standard remotes like https://github.com/owner/repo.git and git@github.com:owner/repo.git, because the main capture group greedily includes .git. That makes later API requests hit /repos/<owner>/<repo>.git/..., which causes the pre-transfer governance readiness check to fail even with a valid token.

Useful? React with 👍 / 👎.

[chatgpt-codex-connector]

Build container with buildx before using gha cache options

This script invokes docker build while passing --cache-from type=gha and --cache-to type=gha,mode=max; Docker documents the gha cache backend as a Buildx flow and not supported by the default docker driver in common setups. As written, the containerized release-gate path can fail during build on CI runners before the gate itself runs.

Useful? React with 👍 / 👎.

[chatgpt-codex-connector]

Remove path filter from required release-gate workflow

This workflow is path-filtered to only run for contracts/** and its own workflow file, but governance baseline now requires the Release Gate Container status check on protected branches. For PRs that do not touch those paths, GitHub leaves the required check as “Waiting for status to be reported,” blocking merges even when everything else passes.

Useful? React with 👍 / 👎.