feat(extension): bound native messaging host authority by seonghobae · Pull Request #82 · ContextualWisdomLab/OriginWeave

seonghobae · 2026-08-11T10:35:40Z

Partial implementation of #27.

Buyer/security gap

Issue #27 requires native messaging only behind explicit host-managed authority and bounded transport. Chrome's nativeMessaging permission, a manifest host-name string, or bytes received from a native process must never become OriginWeave Agent authority by implication.

Current implementation

The exact branch provides:

Chrome-compatible native-host name identity: lowercase ASCII alphanumeric, underscore, and dot only; no leading, trailing, or consecutive dot; 256-byte maximum;
explicit exact extension-ID plus host-name grants and access requests;
typed denial for missing grant, extension mismatch, or host mismatch;
process-wide single-extension ownership for the native-messaging control boundary;
bounded native-messaging framing with a 64 MiB browser-to-host limit and 1 MiB host-to-browser limit;
typed ControlRequest / ControlReply framing helpers and deterministic frame/I/O errors; and
public read-only identity getters.

The reader grows only from delivered bytes under the direction limit; an advertised frame length does not cause an unbounded/pre-sized allocation.

Documentation/provenance repair

The branch strengthens tests/test_doctoring_reference_contract.py so docs/doctoring.md and docs/doctoring/mv3-compatibility.md retain the immutable Chromium revision/source-path evidence for the native-messaging compatibility claims instead of accepting a moving refs/heads/main reference. This does not change production authority or protocol semantics.

Fresh protected-main adoption

Protected main is exact c789b802fc98a8d7fd8c09d9327f36828054d2a1. The old PR base 542ca1e9c0a863595b8b6697790005d2471f5413 is two commits behind, and GitHub compare reports no file delta between those protected-main revisions.

Commit cec5992c0bdf32bd9b33c3edf475b95d312bab70 therefore adopts current protected main as a second parent while preserving predecessor head 90c4e9a8f31eb94eb46243343160d3f6c96921ef's product tree exactly. The branch moved by normal non-force fast-forward; no destructive rebase or force-push was used.

Fresh compare against current protected main is 31 ahead / 0 behind, merge base exactly c789b802fc98a8d7fd8c09d9327f36828054d2a1, with 16 semantic paths: the extension bounded-context crate and its tests, Cargo workspace membership/lock state, CHANGELOG, immutable Chromium doctoring, and repository/documentation contracts. No .github/**, ruleset, provider/model, browser policy, secret, or coverage-denominator change is present.

Exact-current evidence

Current exact contributor head is cec5992c0bdf32bd9b33c3edf475b95d312bab70; GitHub reports the PR open, Draft, content-mergeable, and based on current protected main.

Predecessor exact 90c4e9a8... had repository-native CI, Manifest V3, SAST, Security Scan, and coverage success, but also central Strix/Noema/OpenCode control-plane failures or incompleteness. None of that transfers to the new head.

Fresh workflows for cec5992c... have materialized and are non-terminal:

CI 33776057802: queued;
Manifest V3 Compatibility 33776057734: queued;
SAST Semgrep 33776057765: queued;
Security Scan 33776057846: queued;
OSV-Scanner PR 33776059260: queued;
Scorecard PR 33776057738: queued; and
one-shot Materialize Rust nightly refresh once 33776057891: completed as skipped and is not product evidence.

No exact-current GREEN or independent approval is claimed. Keep Draft until the unchanged head obtains repository contracts, strict Rust checks/rustdoc, exact 100% owned-production function/line/region/branch coverage, pinned-Chromium/MV3 evidence, applicable security/review verdicts, and live governance acceptance.

Truth boundary

This branch does not validate installed native-host manifests or OS registration ownership, launch/sandbox/supervise a native host process, trust arbitrary native-process JSON, authenticate the native peer, resolve secrets, persist authority, or grant arbitrary Agent capabilities. ControlRequest / ControlReply remain bounded framing/control contracts only.

Protected-main AGENTS.md and live governance remain authoritative. This scheduled writer does not merge, self-approve, bypass, force-push, destructively rebase, alter workflows/rulesets/secrets, weaken checks, tag, release, or publish.

coderabbitai · 2026-08-11T10:35:53Z

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

@coderabbitai resume to resume automatic reviews.
@coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

▶️ Resume reviews
🔍 Trigger review

📝 Walkthrough

Walkthrough

네이티브 메시징 권한 평가와 프레임 인코딩·디코딩·스트림 읽기 API를 추가했습니다. 방향별 페이로드 상한, UTF-8 검증, 잘린 프레임과 잔여 데이터 거부를 구현했습니다. 권한, 프레이밍, Chromium 호환성 근거를 테스트와 문서에 반영했습니다.

Changes

네이티브 메시징 경계

Layer / File(s)	Summary
권한 평가 검증 `crates/originweave-core/tests/native_messaging_authority.rs`, `crates/originweave-core/tests/native_messaging_host_bounds.rs`, `crates/originweave-core/tests/native_messaging_manifest_policy.rs`	호스트 이름 문법과 256자 경계, 정확한 확장 ID·호스트 이름 grant, `stdio`, 허용 origin 목록, 오류 동작을 검증합니다.
프레이밍 계약과 공개 API `crates/originweave-core/src/native_messaging.rs`, `crates/originweave-core/src/root.rs`	프레임 방향, 방향별 페이로드 상한, 오류 타입, 스트림 읽기, 인코딩, 디코딩, UTF-8 검증 API를 추가하고 루트 모듈에서 재export합니다.
프레이밍 동작 검증 `crates/originweave-core/tests/native_messaging_framing.rs`	네이티브 엔디언 길이 접두사, 청크 읽기, 상한 초과, 잘림, 길이 불일치, UTF-8 오류와 오류 원인을 검증합니다.
호환성 근거와 변경 기록 `docs/doctoring.md`, `docs/doctoring/mv3-compatibility.md`, `tests/test_doctoring_reference_contract.py`, `CHANGELOG.md`	프레이밍 경계와 Chromium 불변 참조를 문서화하고, 참조 URL과 결정 추적 내용을 검사합니다.

Estimated code review effort: 4 (Complex) | ~45 minutes

Merge Risk: 🟡 Moderate · up to 89fe0

The PR adds bounded native-messaging identities, grants, and framing without directly granting Agent authority, but merge readiness is not established while a required exact-head gate is failing. In addition, the reference-integrity test should validate the complete pinned Chromium path and blob so documentation drift cannot pass unnoticed.

Sequence Diagram(s)

sequenceDiagram
  participant NativeMessagingStream as 네이티브 메시징 스트림
  participant PayloadReader as read_native_messaging_payload
  participant FrameCodec as encode_native_messaging_frame
  participant TextDecoder as decode_native_messaging_text_frame
  NativeMessagingStream->>PayloadReader: 길이 접두사와 페이로드 읽기
  PayloadReader-->>FrameCodec: 상한 내 페이로드 전달
  FrameCodec-->>TextDecoder: 완전한 프레임 전달
  TextDecoder-->>NativeMessagingStream: UTF-8 텍스트 반환

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 62 functions across 8 files. (3 skipped: 3…
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	제목은 네이티브 메시징 호스트 권한을 제한하고 경계를 설정하는 주요 변경 사항을 정확히 요약합니다. 짧고 명확하며 변경 내용과 직접 관련됩니다.

Full details: Docstring Coverage

Explanation

Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 62 functions across 8 files. (3 skipped: 3 unsupported.)

✨ Finishing Touches 💡 1

🛠️ Fix failing CI checks 💡

Create stacked PR
Commit on current branch

📝 Generate docstrings

Create stacked PR
Commit on current branch

🧪 Generate unit tests (beta)

Create PR with unit tests
Commit unit tests in branch feat/native-messaging-host-authority

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

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

cursor · 2026-08-16T21:29:00Z

Bugbot is not enabled for your account, so this pull request was not reviewed.

Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs.

opencode-agent

Pull request overview

OpenCode cannot approve yet because required coverage evidence did not pass.

Review outcome

1. HIGH .github/workflows/opencode-review.yml:1 - Coverage evidence did not prove required test/docstring evidence

Problem: The required coverage-evidence job result was failure, so OpenCode cannot establish approval sufficiency for this head.
Root cause: Automated approval is only valid when the same-head coverage-evidence job proves supported repository test suites passed and configured docstring gates passed or were advisory, or reports not applicable because no supported source files or package manifests exist. Missing, failed, skipped, unavailable, or unsupported-tooling test evidence is a blocker.
Fix: Install or configure the repository test/docstring evidence tooling when source files or package manifests exist, rerun the current-head coverage-evidence job, and approve only after it reports success with required evidence or explicit no-source not-applicable evidence.
Regression test: Keep the approval branch checking needs.coverage-evidence.result == success before posting APPROVE, and publish REQUEST_CHANGES when coverage-evidence blocker states such as cancelled, skipped, failed, unsupported-tooling, or below-100 evidence are present.
Result: REQUEST_CHANGES
Reason: coverage-evidence result was failure, so required test/docstring evidence was not proven for current head c639cd78e3acad235be4cbbfdef67b84ce7ddbfa.
Head SHA: c639cd78e3acad235be4cbbfdef67b84ce7ddbfa
Workflow run: 32132787181
Workflow attempt: 1

Coverage evidence

Coverage Decision

Result: FAIL
Test evidence: not proven passing
Docstring evidence: not proven passing when configured
Failure count: 1

Changed-File Evidence Map

flowchart LR
  PR["PR changed files"] --> Evidence["OpenCode bounded evidence"]
  Evidence --> S1["Changed file (5 files)"]
  S1 --> I1["repository behavior"]
  I1 --> R1["Review risk: Changed file (5 files)"]
  R1 --> V1["required checks"]

opencode-agent · 2026-08-18T13:01:36Z

OpenCode Review Overview

Head SHA: c639cd78e3acad235be4cbbfdef67b84ce7ddbfa
Workflow run: 32139252038
Workflow attempt: 1
Gate result: REQUEST_CHANGES (approval step)

Pull request overview

OpenCode cannot approve yet because required coverage evidence did not pass.

Review outcome

1. HIGH .github/workflows/opencode-review.yml:1 - Coverage evidence did not prove required test/docstring evidence

Problem: The required coverage-evidence job result was failure, so OpenCode cannot establish approval sufficiency for this head.
Root cause: Automated approval is only valid when the same-head coverage-evidence job proves supported repository test suites passed and configured docstring gates passed or were advisory, or reports not applicable because no supported source files or package manifests exist. Missing, failed, skipped, unavailable, or unsupported-tooling test evidence is a blocker.
Fix: Install or configure the repository test/docstring evidence tooling when source files or package manifests exist, rerun the current-head coverage-evidence job, and approve only after it reports success with required evidence or explicit no-source not-applicable evidence.
Regression test: Keep the approval branch checking needs.coverage-evidence.result == success before posting APPROVE, and publish REQUEST_CHANGES when coverage-evidence blocker states such as cancelled, skipped, failed, unsupported-tooling, or below-100 evidence are present.
Result: REQUEST_CHANGES
Reason: coverage-evidence result was failure, so required test/docstring evidence was not proven for current head c639cd78e3acad235be4cbbfdef67b84ce7ddbfa.
Head SHA: c639cd78e3acad235be4cbbfdef67b84ce7ddbfa
Workflow run: 32139252038
Workflow attempt: 1

Coverage evidence

Coverage Decision

Result: FAIL
Test evidence: not proven passing
Docstring evidence: not proven passing when configured
Failure count: 1

Changed-File Evidence Map

flowchart LR
  PR["PR changed files"] --> Evidence["OpenCode bounded evidence"]
  Evidence --> S1["Changed file (5 files)"]
  S1 --> I1["repository behavior"]
  I1 --> R1["Review risk: Changed file (5 files)"]
  R1 --> V1["required checks"]

opencode-agent

Pull request overview

OpenCode cannot approve yet because required coverage evidence did not pass.

Review outcome

1. HIGH .github/workflows/opencode-review.yml:1 - Coverage evidence did not prove required test/docstring evidence

Problem: The required coverage-evidence job result was failure, so OpenCode cannot establish approval sufficiency for this head.
Root cause: Automated approval is only valid when the same-head coverage-evidence job proves supported repository test suites passed and configured docstring gates passed or were advisory, or reports not applicable because no supported source files or package manifests exist. Missing, failed, skipped, unavailable, or unsupported-tooling test evidence is a blocker.
Fix: Install or configure the repository test/docstring evidence tooling when source files or package manifests exist, rerun the current-head coverage-evidence job, and approve only after it reports success with required evidence or explicit no-source not-applicable evidence.
Regression test: Keep the approval branch checking needs.coverage-evidence.result == success before posting APPROVE, and publish REQUEST_CHANGES when coverage-evidence blocker states such as cancelled, skipped, failed, unsupported-tooling, or below-100 evidence are present.
Result: REQUEST_CHANGES
Reason: coverage-evidence result was failure, so required test/docstring evidence was not proven for current head c639cd78e3acad235be4cbbfdef67b84ce7ddbfa.
Head SHA: c639cd78e3acad235be4cbbfdef67b84ce7ddbfa
Workflow run: 32139252038
Workflow attempt: 1

Coverage evidence

Coverage Decision

Result: FAIL
Test evidence: not proven passing
Docstring evidence: not proven passing when configured
Failure count: 1

Changed-File Evidence Map

flowchart LR
  PR["PR changed files"] --> Evidence["OpenCode bounded evidence"]
  Evidence --> S1["Changed file (5 files)"]
  S1 --> I1["repository behavior"]
  I1 --> R1["Review risk: Changed file (5 files)"]
  R1 --> V1["required checks"]

# Conflicts: # CHANGELOG.md # crates/originweave-core/src/root.rs

seonghobae · 2026-08-28T02:47:04Z

Verified against exact current head 79d8c85: the alleged missing CHANGELOG entry is already present at CHANGELOG.md:19, documenting bounded native-messaging host identity and explicit extension-to-host grants. The finding is stale/invalid; no source change is warranted.

Merge exact-head native messaging framing boundary into the native-host authority stack.

devin-ai-integration

Devin Review found 1 new potential issue.

seonghobae · 2026-09-02T09:08:22Z

@cwl-noema-review review exact head 90c4e9a8f31eb94eb46243343160d3f6c96921ef using the current protected central Noema workflow source. The previous attempt materialized stale trusted source .github@1ddc31fb341a75ddafe8516b86c5d52e26669933 and failed after healthy orchestrator/free transport with Noema request_changes requires a confirmed probe on a published finding; do not reuse that run as current evidence.

…hanges

test(extension): require native messaging host authority

afea70b

seonghobae added 3 commits August 11, 2026 19:40

test(extension): prove native host grant cannot mint agent authority

6502448

feat(extension): enforce native messaging host allow-list

6390465

style(extension): apply canonical rustfmt

9b2bbb7

seonghobae mentioned this pull request Aug 11, 2026

feat(extension): identify reduced-assurance attached tabs #83

Draft

test(extension): cover numeric native host names

28593cf

seonghobae marked this pull request as ready for review August 11, 2026 11:04

test(extension): bound native messaging host identity

1c32eff

seonghobae marked this pull request as draft August 14, 2026 00:36

seonghobae added 2 commits August 14, 2026 09:42

fix(extension): bound native messaging host identity

4ed1ac2

Merge protected main into native messaging authority

a0b1020

seonghobae marked this pull request as ready for review August 14, 2026 02:16

seonghobae mentioned this pull request Aug 14, 2026

feat(extension): bound native messaging framing #154

Merged

seonghobae added 2 commits August 15, 2026 22:24

test(extension): expose native messaging authority identities

8da1772

feat(extension): expose native messaging authority identities

427d2f3

seonghobae mentioned this pull request Aug 16, 2026

feat(extension): bind native host manifest authority #169

Draft

Merge branch 'main' into feat/native-messaging-host-authority

f6e0314

seonghobae added 3 commits August 17, 2026 07:32

test(core): align native messaging Agent request scope

ad1ece9

test(core): require standard native messaging host errors

2d16411

fix(core): expose standard native messaging host errors

c639cd7

opencode-agent Bot requested changes Aug 18, 2026

View reviewed changes

seonghobae mentioned this pull request Aug 21, 2026

feat(extension): bound native messaging frame codec #213

Closed

seonghobae added 2 commits August 24, 2026 01:47

docs(changelog): record native messaging authority

48521b2

docs: mark merged MCP foundation as protected-main truth

cdf9daa