Skip to content

Harden joinery boundaries and gate main with verified CI - #218

Open
hyperpolymath wants to merge 8 commits into
mainfrom
codex/joinery-beta-20260906
Open

Harden joinery boundaries and gate main with verified CI#218
hyperpolymath wants to merge 8 commits into
mainfrom
codex/joinery-beta-20260906

Conversation

@hyperpolymath

Copy link
Copy Markdown
Collaborator

Scope

Add scoped, authenticated native signaling with strict frame parsing, room/peer membership checks, bounded mailboxes and effect-time deadlines. Run real Burble endpoint pairing and GTK lifecycle acceptance against reviewed Gossamer commit 8a99e6422439f0313b642a0ca1ba2708fdfe6344.

Safety and CI

  • Signed implementation and CI commits; existing main rulesets remain in place.
  • Run relevant checks on pull requests and merge groups, with stable checks for workflow syntax/action-lock coverage.
  • Keep dependency locks and compiler versions explicit; add RustSec audits in the Rust-bearing repositories and expand CodeQL to supported implementation languages.
  • Retain required secrets, code-scanning and governance checks. A green YAML validation or a report-only legacy scanner is not evidence of runtime safety.

Verification and limits

Earlier local acceptance was recorded before these CI commits. The PR checks must independently pass for the exact PR head, followed by merge-queue checks; do not bypass protections or infer a pass from a missing check.

This work is NOT a production-beta release. Native microphone/camera/WebRTC media acceptance remains unqualified on the installed WebKit runtime. Idris proof models and rejection controls are not proof-to-binary correspondence or proof of distributed O6/O7 composition.

Includes the Hypatia SARIF permission repair proposed in #217; that existing PR has not been merged or closed here.

@github-advanced-security

Copy link
Copy Markdown

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

  • The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
  • Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
  • You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.

Comment thread .github/workflows/hypatia-scan.yml Fixed
runs-on: ubuntu-latest
timeout-minutes: 15
steps:
- uses: actions/checkout@v7.0.1
- uses: actions/checkout@v7.0.1
with:
persist-credentials: false
- uses: dtolnay/rust-toolchain@v1
version: '0.15.2'
- name: Install just
uses: taiki-e/install-action@37f7c5781271959fb65b6b35224e28652ff2b63d # v2.87.0
uses: taiki-e/install-action@v2.87.0
echo "HEX_HOME=$RUNNER_TEMP/joinery/hex"
echo "PAIRING_ARTIFACT_DIR=$RUNNER_TEMP/joinery/acceptance"
} >> "$GITHUB_ENV"
- uses: actions/checkout@v7.0.1
# pull, and the failure was masked. Config comes from .oikos.yml.
- name: Run OikosBot analysis
uses: hyperpolymath/oikosbot@3fdad0c2b027f328e784ecf08caf62bf80a784c1 # v0.1.3
uses: hyperpolymath/oikosbot@v0.1.3
Comment thread .github/workflows/scorecard.yml Fixed
Comment thread .github/workflows/scorecard.yml Fixed
Comment thread .github/workflows/scorecard.yml Fixed
runs-on: ubuntu-latest
timeout-minutes: 10
steps:
- uses: actions/checkout@v7.0.1
Ratchet-exception: .gitleaks.toml — five exact published BLE-SPA v1 conformance values derived from public fixture inputs. No file or key-shaped class is exempted. Pinned gitleaks 8.18.4 accepts the corpus and rejects a different generated key in the same file; these controls are required in Workflow safety.
permissions:
actions: read
contents: read
security-events: write
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.

2 participants