morluto/rea
1
0
Fork 0
mirror of https://github.com/morluto/rea.git synced 2026-11-05 06:45:22 +00:00
Code Issues 1.3k Projects Packages Wiki Activity

[PR #7178] feat(ledger)!: require failing negative control before verifier closes obligation #7697

New issue
Open
opened 2026-11-03 13:39:43 +00:00 by bsakaguchi · 0 comments
bsakaguchi commented 2026-11-03 13:39:43 +00:00
Owner
Copy link

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/7178
Author: @hannesstrydom664-hash
Created: 10/25/2026
Status: 🔄 Open

Base: main ← Head: feat/reconstruction-negative-control-4396

📝 Commits (4)

  • 059e397 feat(ledger): require failing negative control before verifier closes obligation (#4396)
  • 6f403b4 fix(ledger): address verifier negative control review feedback (#4396)
  • ffe5ca9 feat(ledger)!: mark negative-control closure requirement as breaking (#4396)
  • a1f55c0 fix(ledger): reject negative controls that reuse the positive subject

📊 Changes

10 files changed (+1027 additions, -43 deletions)

View changed files

📝 docs/reconstruction-obligation-ledgers.md (+58 -10)
📝 src/application/ReconstructionObligationAuthority.ts (+8 -1)
📝 src/application/ReconstructionObligationLedger.authority.test.ts (+53 -25)
📝 src/application/ReconstructionObligationLedger.closure.test.ts (+664 -0)
📝 src/application/ReconstructionObligationLedger.fixture.ts (+56 -2)
📝 src/application/ReconstructionObligationLedgerEvaluation.ts (+140 -0)
📝 src/application/ReconstructionObligationLedgerProjection.ts (+6 -1)
📝 src/domain/reconstructionObligationLedgerIntegrity.ts (+10 -1)
📝 src/domain/reconstructionObligationLedgerSchemas.ts (+25 -0)
📝 tests/fixtures/reconstructionProofApplicability.ts (+7 -3)

📄 Description

Summary

Fixes #4396

Prevents vacuous ("always-pass") reconstruction verifiers from closing obligations in ReconstructionObligationLedger by requiring a verifier binding to demonstrate at least one failing negative control before an obligation transitions to verified.

Problem and expected behavior

  • Smallest trigger: Evaluate a ReconstructionObligationLedger where an obligation has a passing verifier binding (status: "pass") and passing fixture results, but either has no verifier.controls or has a negative control whose proof record passed (passed: true / status: "pass").
  • Violated invariant: A verifier that passes on a known-bad or mutated candidate (or has never been challenged against a negative control) does not establish behavioral equivalence and must not close an obligation as verified.
  • Expected behavior:
    • When verifier.controls is omitted or empty, evaluation emits diagnostic "missing-verifier-control", sets verifier_control_status: "unchallenged", and keeps the obligation open (status: "implemented").
    • When any negative control reports status: "pass" or its proof record reports passed: true, evaluation emits diagnostic "vacuous-verifier", sets verifier_control_status: "vacuous", keeps the obligation open, and escalates required open obligations with "vacuous-verifier" to ledger status "failed".
    • When all negative controls fail against their known-bad candidates with qualified negative-control proof records (expectedPassed: false) and positive verifier + fixtures pass, verifier_control_status is "challenged" and the obligation closes as verified.

Change and scope

Follow the contribution scope.
Scoped enhancement implementing issue #4396 (feat(ledger): require failing negative control before verifier closes obligation).

  • src/domain/reconstructionObligationLedgerSchemas.ts: Add verifierNegativeControlSchema (control_id, optional candidate_id and candidate_sha256, defect, status, and result_evidence_id), optional controls on verifierBindingSchema, verifierControlStatusSchema ("challenged" | "unchallenged" | "vacuous" | "missing-control-result" | "inapplicable-control-proof" | "control-unavailable"), optional verifier_control_status on reconstructionObligationSchema, and diagnostics "vacuous-verifier", "missing-verifier-control", "missing-verifier-control-result", "inapplicable-verifier-control-proof", and "verifier-control-unavailable".
  • src/domain/reconstructionObligationLedgerIntegrity.ts & src/application/ReconstructionObligationLedgerProjection.ts: Include negative control result_evidence_id references in reconstructionObligationEvidenceIds and obligationLedgerEvidenceLinks, and escalate required open obligations with "vacuous-verifier" diagnostics to ledger status "failed".
  • src/application/ReconstructionObligationAuthority.ts & src/application/ReconstructionObligationLedgerEvaluation.ts: Support expectedPassed: false in qualifyReconstructionProof (returning "passed-negative-control" if the proof record reports passed: true) and evaluate verifier.controls before permitting obligation closure.
  • Tests (src/application/ReconstructionObligationLedger.closure.test.ts, src/application/ReconstructionObligationLedger.authority.test.ts, src/domain/reconstructionObligationLedgerSchemas.test.ts, tests/conformance/readiness/report/reconstructionReadiness.test.ts): Update closure/conformance fixtures with failing negative controls and add regression tests for unchallenged, vacuous, missing-evidence, unavailable, and inapplicable negative controls.

Contract and boundary impact

  • Semantic owner and earliest changed stage: src/domain/reconstructionObligationLedgerSchemas.ts, src/application/ReconstructionObligationAuthority.ts, and src/application/ReconstructionObligationLedgerEvaluation.ts.
  • Contribution scope fit and linked maintainer decision: Implements #4396 (feat(ledger): require failing negative control before verifier closes obligation).
  • CLI and MCP/tool-catalog contract: Extends ReconstructionObligationLedger schema with optional verifier.controls and optional verifier_control_status so existing serialized ledgers without controls remain parseable while new closure evaluations enforce negative controls.
  • Provider, bridge, target-format, or platform compatibility: None.
  • Evidence, artifact, provenance, or reconstruction contract: Requires retained negative-control proof Evidence (expectedPassed: false) and links negative-control result_evidence_id into ledger Evidence integrity and projection links.
  • Target selection, authority, upstream behavior, and cleanup details (if applicable): Verifier negative-control proof records are checked for subject/candidate authority when candidate_id / candidate_sha256 are supplied on the control.
  • Generated metadata (docs/public/product-catalog.json), package, or installation impact: None.

Expected effects (check known effects; use documentation-only on its own).
Unchecked items do not establish absence; leave uncertainties visible.

  • Read existing files or captured data.
  • Launch or attach to a process.
  • Inject instrumentation or run scripts/code.
  • Change process memory, registers, files, or configuration.
  • Contact network services.
  • Recover protected code or work around protections.
  • Documentation or usability only; no target interaction.
  • Not sure yet; investigation or maintainer guidance needed.

Evidence and regression coverage

  • Tests added or updated:
    • src/application/ReconstructionObligationLedger.closure.test.ts
    • src/application/ReconstructionObligationLedger.authority.test.ts
    • src/domain/reconstructionObligationLedgerSchemas.test.ts
    • tests/conformance/readiness/report/reconstructionReadiness.test.ts
  • Base reproduction or other evidence:
    • Executed: Verified that a verifier without controls stays open (status: "implemented", verifier_control_status: "unchallenged", diagnostic "missing-verifier-control"), a verifier whose negative control passes is flagged (verifier_control_status: "vacuous", diagnostic "vacuous-verifier", ledger status "failed"), and a verifier with a qualified failing negative control closes the obligation (status: "verified", verifier_control_status: "challenged").
  • User-visible CLI/MCP output (if applicable):
    • Evaluated obligations include verifier_control_status ("challenged", "unchallenged", "vacuous", "missing-control-result", "inapplicable-control-proof", or "control-unavailable") and corresponding diagnostics when negative-control requirements are not met.
  • Remaining proof gaps: None.

For evidence-bearing changes:

  • Observed, derived, and inferred claims remain distinguishable.
  • Artifact identity, source provenance, and failed attempts remain preserved.
  • Unsupported, incomplete, unavailable, or uncertain outcomes remain visible.

Validation performed

  • npx vitest run src/application/ReconstructionObligationLedger.closure.test.ts src/application/ReconstructionObligationLedger.authority.test.ts src/domain/reconstructionObligationLedgerSchemas.test.ts tests/conformance/readiness/report/reconstructionReadiness.test.ts tests/boundary/cli/reconstructionObligationLedgerCli.test.ts — 5 test files passed, 82 tests passed.
  • npm run typecheck — passed (tsc --noEmit, 0 errors).
  • npm run format:check — passed (oxfmt --check .).
  • npm run lint — passed (oxlint 0 warnings/0 errors; verify:module-boundaries passed).
  • npm run verify:test-discovery — passed.
  • npm run verify:architecture-guards — passed.
  • npm run scan:todos — passed.
  • npm run jscpd — passed.

Compatibility, safety, and release

  • Breaking changes or migration steps: Existing stored ledgers without verifier.controls continue to parse cleanly (controls and verifier_control_status are optional on the wire); re-evaluating an obligation for verified closure now requires at least one failing negative control on verifier.controls.
  • Real Hopper/Ghidra, browser, or OS coverage: Not applicable (pure domain/application obligation ledger evaluation and conformance suite).
  • Package or release metadata impact: None.
  • Security, privacy, process, or containment review: Strengthens verification integrity by rejecting vacuous verifiers.

Author readiness

Human owner: @hannesstrydom664-hash

  • I reviewed the final diff and relevant existing code, understand the change and its edge cases, and take responsibility for the complete PR, including AI-assisted work.
  • I checked the evidence above, confirmed it supports the current change, and recorded meaningful validation gaps.
  • I declare this PR ready for initial maintainer review.

Before merge

  • This PR addresses a concrete problem or an agreed enhancement.
  • Material scope and authority questions are resolved, and any required maintainer scope decision covers the final diff.
  • The PR has one focused outcome and the title follows type(scope): outcome.
  • Related issue is linked, or the reason for not linking one is stated above.
  • Tests cover changed observable behavior and meaningful failure paths.
  • Owning docs, contracts, and generated metadata are updated where needed.
  • User-visible CLI/MCP changes include representative output.
  • I checked the final diff for secrets, unrelated cleanup, and unsupported claims.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/morluto/rea/pull/7178 **Author:** [@hannesstrydom664-hash](https://github.com/hannesstrydom664-hash) **Created:** 10/25/2026 **Status:** 🔄 Open **Base:** `main` ← **Head:** `feat/reconstruction-negative-control-4396` --- ### 📝 Commits (4) - [`059e397`](https://github.com/morluto/rea/commit/059e3979009bd20723adaac62db1db1f721c907a) feat(ledger): require failing negative control before verifier closes obligation (#4396) - [`6f403b4`](https://github.com/morluto/rea/commit/6f403b4e4a92343d2794b19e4d668176c280586a) fix(ledger): address verifier negative control review feedback (#4396) - [`ffe5ca9`](https://github.com/morluto/rea/commit/ffe5ca9eb799d6a01db3a7feb03bfcef9c386083) feat(ledger)!: mark negative-control closure requirement as breaking (#4396) - [`a1f55c0`](https://github.com/morluto/rea/commit/a1f55c0214f0837b7194a6424cf8f6ce43270c70) fix(ledger): reject negative controls that reuse the positive subject ### 📊 Changes **10 files changed** (+1027 additions, -43 deletions) <details> <summary>View changed files</summary> 📝 `docs/reconstruction-obligation-ledgers.md` (+58 -10) 📝 `src/application/ReconstructionObligationAuthority.ts` (+8 -1) 📝 `src/application/ReconstructionObligationLedger.authority.test.ts` (+53 -25) 📝 `src/application/ReconstructionObligationLedger.closure.test.ts` (+664 -0) 📝 `src/application/ReconstructionObligationLedger.fixture.ts` (+56 -2) 📝 `src/application/ReconstructionObligationLedgerEvaluation.ts` (+140 -0) 📝 `src/application/ReconstructionObligationLedgerProjection.ts` (+6 -1) 📝 `src/domain/reconstructionObligationLedgerIntegrity.ts` (+10 -1) 📝 `src/domain/reconstructionObligationLedgerSchemas.ts` (+25 -0) 📝 `tests/fixtures/reconstructionProofApplicability.ts` (+7 -3) </details> ### 📄 Description ## Summary Fixes #4396 Prevents vacuous ("always-pass") reconstruction verifiers from closing obligations in `ReconstructionObligationLedger` by requiring a verifier binding to demonstrate at least one failing negative control before an obligation transitions to `verified`. ## Problem and expected behavior - **Smallest trigger:** Evaluate a `ReconstructionObligationLedger` where an obligation has a passing `verifier` binding (`status: "pass"`) and passing fixture results, but either has no `verifier.controls` or has a negative control whose proof record passed (`passed: true` / `status: "pass"`). - **Violated invariant:** A verifier that passes on a known-bad or mutated candidate (or has never been challenged against a negative control) does not establish behavioral equivalence and must not close an obligation as `verified`. - **Expected behavior:** - When `verifier.controls` is omitted or empty, evaluation emits diagnostic `"missing-verifier-control"`, sets `verifier_control_status: "unchallenged"`, and keeps the obligation open (`status: "implemented"`). - When any negative control reports `status: "pass"` or its proof record reports `passed: true`, evaluation emits diagnostic `"vacuous-verifier"`, sets `verifier_control_status: "vacuous"`, keeps the obligation open, and escalates required open obligations with `"vacuous-verifier"` to ledger status `"failed"`. - When all negative controls fail against their known-bad candidates with qualified negative-control proof records (`expectedPassed: false`) and positive verifier + fixtures pass, `verifier_control_status` is `"challenged"` and the obligation closes as `verified`. ## Change and scope Follow the [contribution scope](https://github.com/morluto/rea/blob/main/CONTRIBUTING.md#contribution-scope). Scoped enhancement implementing issue #4396 (`feat(ledger): require failing negative control before verifier closes obligation`). - `src/domain/reconstructionObligationLedgerSchemas.ts`: Add `verifierNegativeControlSchema` (`control_id`, optional `candidate_id` and `candidate_sha256`, `defect`, `status`, and `result_evidence_id`), optional `controls` on `verifierBindingSchema`, `verifierControlStatusSchema` (`"challenged" | "unchallenged" | "vacuous" | "missing-control-result" | "inapplicable-control-proof" | "control-unavailable"`), optional `verifier_control_status` on `reconstructionObligationSchema`, and diagnostics `"vacuous-verifier"`, `"missing-verifier-control"`, `"missing-verifier-control-result"`, `"inapplicable-verifier-control-proof"`, and `"verifier-control-unavailable"`. - `src/domain/reconstructionObligationLedgerIntegrity.ts` & `src/application/ReconstructionObligationLedgerProjection.ts`: Include negative control `result_evidence_id` references in `reconstructionObligationEvidenceIds` and `obligationLedgerEvidenceLinks`, and escalate required open obligations with `"vacuous-verifier"` diagnostics to ledger status `"failed"`. - `src/application/ReconstructionObligationAuthority.ts` & `src/application/ReconstructionObligationLedgerEvaluation.ts`: Support `expectedPassed: false` in `qualifyReconstructionProof` (returning `"passed-negative-control"` if the proof record reports `passed: true`) and evaluate `verifier.controls` before permitting obligation closure. - Tests (`src/application/ReconstructionObligationLedger.closure.test.ts`, `src/application/ReconstructionObligationLedger.authority.test.ts`, `src/domain/reconstructionObligationLedgerSchemas.test.ts`, `tests/conformance/readiness/report/reconstructionReadiness.test.ts`): Update closure/conformance fixtures with failing negative controls and add regression tests for unchallenged, vacuous, missing-evidence, unavailable, and inapplicable negative controls. ## Contract and boundary impact - Semantic owner and earliest changed stage: `src/domain/reconstructionObligationLedgerSchemas.ts`, `src/application/ReconstructionObligationAuthority.ts`, and `src/application/ReconstructionObligationLedgerEvaluation.ts`. - Contribution scope fit and linked maintainer decision: Implements #4396 (`feat(ledger): require failing negative control before verifier closes obligation`). - CLI and MCP/tool-catalog contract: Extends `ReconstructionObligationLedger` schema with optional `verifier.controls` and optional `verifier_control_status` so existing serialized ledgers without `controls` remain parseable while new closure evaluations enforce negative controls. - Provider, bridge, target-format, or platform compatibility: None. - Evidence, artifact, provenance, or reconstruction contract: Requires retained negative-control proof Evidence (`expectedPassed: false`) and links negative-control `result_evidence_id` into ledger Evidence integrity and projection links. - Target selection, authority, upstream behavior, and cleanup details (if applicable): Verifier negative-control proof records are checked for subject/candidate authority when `candidate_id` / `candidate_sha256` are supplied on the control. - Generated metadata (`docs/public/product-catalog.json`), package, or installation impact: None. Expected effects (check known effects; use documentation-only on its own). Unchecked items do not establish absence; leave uncertainties visible. - [x] Read existing files or captured data. - [ ] Launch or attach to a process. - [ ] Inject instrumentation or run scripts/code. - [ ] Change process memory, registers, files, or configuration. - [ ] Contact network services. - [ ] Recover protected code or work around protections. - [ ] Documentation or usability only; no target interaction. - [ ] Not sure yet; investigation or maintainer guidance needed. ## Evidence and regression coverage - Tests added or updated: - `src/application/ReconstructionObligationLedger.closure.test.ts` - `src/application/ReconstructionObligationLedger.authority.test.ts` - `src/domain/reconstructionObligationLedgerSchemas.test.ts` - `tests/conformance/readiness/report/reconstructionReadiness.test.ts` - Base reproduction or other evidence: - Executed: Verified that a verifier without `controls` stays open (`status: "implemented"`, `verifier_control_status: "unchallenged"`, diagnostic `"missing-verifier-control"`), a verifier whose negative control passes is flagged (`verifier_control_status: "vacuous"`, diagnostic `"vacuous-verifier"`, ledger status `"failed"`), and a verifier with a qualified failing negative control closes the obligation (`status: "verified"`, `verifier_control_status: "challenged"`). - User-visible CLI/MCP output (if applicable): - Evaluated obligations include `verifier_control_status` (`"challenged"`, `"unchallenged"`, `"vacuous"`, `"missing-control-result"`, `"inapplicable-control-proof"`, or `"control-unavailable"`) and corresponding diagnostics when negative-control requirements are not met. - Remaining proof gaps: None. For evidence-bearing changes: - [x] Observed, derived, and inferred claims remain distinguishable. - [x] Artifact identity, source provenance, and failed attempts remain preserved. - [x] Unsupported, incomplete, unavailable, or uncertain outcomes remain visible. ## Validation performed - `npx vitest run src/application/ReconstructionObligationLedger.closure.test.ts src/application/ReconstructionObligationLedger.authority.test.ts src/domain/reconstructionObligationLedgerSchemas.test.ts tests/conformance/readiness/report/reconstructionReadiness.test.ts tests/boundary/cli/reconstructionObligationLedgerCli.test.ts` — 5 test files passed, 82 tests passed. - `npm run typecheck` — passed (`tsc --noEmit`, 0 errors). - `npm run format:check` — passed (`oxfmt --check .`). - `npm run lint` — passed (`oxlint` 0 warnings/0 errors; `verify:module-boundaries` passed). - `npm run verify:test-discovery` — passed. - `npm run verify:architecture-guards` — passed. - `npm run scan:todos` — passed. - `npm run jscpd` — passed. ## Compatibility, safety, and release - Breaking changes or migration steps: Existing stored ledgers without `verifier.controls` continue to parse cleanly (`controls` and `verifier_control_status` are optional on the wire); re-evaluating an obligation for `verified` closure now requires at least one failing negative control on `verifier.controls`. - Real Hopper/Ghidra, browser, or OS coverage: Not applicable (pure domain/application obligation ledger evaluation and conformance suite). - Package or release metadata impact: None. - Security, privacy, process, or containment review: Strengthens verification integrity by rejecting vacuous verifiers. ## Author readiness Human owner: @hannesstrydom664-hash - [x] I reviewed the final diff and relevant existing code, understand the change and its edge cases, and take responsibility for the complete PR, including AI-assisted work. - [x] I checked the evidence above, confirmed it supports the current change, and recorded meaningful validation gaps. - [x] I declare this PR ready for initial maintainer review. ## Before merge - [x] This PR addresses a concrete problem or an agreed enhancement. - [x] Material scope and authority questions are resolved, and any required maintainer scope decision covers the final diff. - [x] The PR has one focused outcome and the title follows `type(scope): outcome`. - [x] Related issue is linked, or the reason for not linking one is stated above. - [x] Tests cover changed observable behavior and meaningful failure paths. - [x] Owning docs, contracts, and generated metadata are updated where needed. - [x] User-visible CLI/MCP changes include representative output. - [x] I checked the final diff for secrets, unrelated cleanup, and unsupported claims. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
codex/procedure-reference-stacked
release-please--branches--main--components--rea-agents
release-please--branches--main--components--rea-agents--release-notes
codex/kuna-independent-retry
codex/byte-search-overlay-coverage
codex/open-failure-target-receipt
codex/kuna-xref-evidence
codex/ghidra-ambiguous-procedure-recovery
codex/function-source-bundle
codex/trace-function-integration-prototype
codex/snapshot-source-closure
codex/recorded-evidence-array-pages
codex/evidence-recovery-redesign
codex/trace-feature-address-scope
codex/call-discovery-scope
codex/ghidra-literal-candidate-evidence
codex/decompile-directory-independent-retry
codex/retry-provenance-base
codex/value-flow-capability-experiment
codex/ghidra-containing-instruction
cursor/readme-discord-button-ef9f
dependabot/github_actions/actions/setup-node-7.1.0
dependabot/github_actions/actions/upload-artifact-7.0.2
dependabot/npm_and_yarn/npm-minor-and-patch-d8d97ce6df
codex/kuna-1989
fix/8559-native-ui-fixture-ownership
fix/8555-go-verifier-mcp-ownership
codex/provider-capability-recovery
fix/8642-rizin-target-stdin
codex/ghidra-memory-effect-scope
codex/ghidra-annotation-entry-selector
codex/ghidra-readonly-recovery
codex/ghidra-regex-verifier-recovery
codex/evidence-discovery-view-guidance
fix/8545-bulk-append-overflow
fix/8428-navigation-refusal-alternatives
codex/address-context-recovery
codex/matching-member-limitations
codex/unknown-scope-contract
codex/evidence-view-guidance
feat/8373-native-trace-views
codex/ghidra-snapshot-verifier-binding
codex/elf-export-visibility
codex/evidence-view-recovery
codex/native-reference-cli-help
codex/provider-candidate-observation-scope
codex/kuna-session-verification
codex/ghidra-switch-lifetime-guidance
codex/pseudocode-paging-discovery
codex/clarify-evidence-view-support
codex/kuna-xrefs-selector-recovery
codex/context-capacity-recovery
codex/evidence-closure-large-links
codex/same-function-evidence-identity
codex/ghidra-verifier-inspected-jdk
codex/audit-guided-workflows
codex/crash-prompt-retained-dossiers
codex/analysis-view-error-recovery
codex/kuna-verifier-target-selection
codex/ghidra-selected-project-call-coverage
codex/docs-native-analysis-scope
codex/ghidra-java-socket-boundary
codex/ghidra-retained-snapshot-verifier
codex/ghidra-search-inventory-facts
fix/8284-zero-argument-parameter-bindings
fix/8198-ui-action-handler-offset
fix/8257-elf-entry-label-identity
fix/8304-deferred-output-schema-projection
fix/8277-call-path-computed-target-uncertainty
fix/pr-8089-conflicts
fix/ci-static-duplicate-export
dependabot/npm_and_yarn/lint-staged-17.6.0
dependabot/github_actions/actions/download-artifact-8.0.2
dependabot/npm_and_yarn/write-file-atomic-8.0.0
dependabot/npm_and_yarn/canonicalize-5.1.0
dependabot/github_actions/actions/cache/restore-6.1.0
dependabot/npm_and_yarn/toon-format/toon-4.4.0
dependabot/github_actions/actions/deploy-pages-5.0.1
codex/review-fixes-pr-2403
codex/review-fixes-pr-2400
codex/process-terminal-width
codex/test-brittleness-cleanup
verify/7167-browser-connect-macos
fix/7167-browser-connect
feat/native-matching-allowance-setting
feat/browser-scenario-dry-run
test/managed-caller-parameters-20261024
codex/parser-fortythird-boundaries
fix/6926-pinvoke-platform-decorations-20261023
fix/6889-har-body-encoding-20261023
fix/6888-sqlite-schema-budget-20261023
fix/dependency-security-gates-6708
cursor/evidence-overwrite-rebase-b4ac
feat/4057-verify-native-exports
fix/windows-acl-observer-overhead-20261022
cursor/erlang-beam-restack-4476
cursor/pe-certificate-review-bf32
fix/6116-javascript-application-fs-errors
fix/6061-unmapped-runtime-script-unknown
feat/browser-scenario-summary
fix/pe-certificates
codex/verify-3407
cursor/rebase-5699
cursor/rebase-5352
cursor/rebase-5600
cursor/fix-cli-schema-omission-10a8
codex/audit-hopper-shutdown-reasons-20261021
fix/demangle-swift-omitted-record
fix/nib-boolean-value-types
cursor/cancellation-partial-observation-a5ac
fix/ib-object-limit-reasons
fix/electron-fuse-limit-advice
fix/kuna-doctor-dangling-cache
fix/fixed-budget-refusal-advice
fix/js-ipc-listener-dedup
fix/js-return-member-provenance
fix/dmg-integrity-retry-advice
fix/ida-doctor-readiness
fix/kuna-version-probe-output-drain
fix/legacy-swift-runtime-name-matching
fix/dylib-lazy-load-commands
fix/browser-scenario-startup-cancel
fix/swift-nested-punycode-classification
fix/compare-unselected-scopes
fix/objc-method-budget-coverage
fix/dmg-mounted-root-observations
audit/ci-tests-20261019-round2
release/6.7.0
fix/wabt-cleanup-retry-resolution
fix/electron-fuse-elf-pe-architecture
fix/native-plist-descriptor-ownership
fix/kuna-caller-cleanup-ownership
experiment/atomic-codemode-20261016
review/first-contributor-3776
fix/call-resolution-full-read-cycles
fix/member-mutation-selection-repeat
experiment/atomic-re-tools-20261015
perf/member-mutation-lazy-origins
perf/static-network-mutation-index
fix/hopper-startup-lifecycle
audit/3050-windows-proof-20261015
feat/windows-window-capture-2183
audit/3049-windows-proof-20261015
audit/3735-macos-fixtures-20261015
fix/batch-decompile-null-pseudocode
fix/kuna-inventory-honors-jobs
experiment/browser-codemode-tool-design-20261015
fix/hopper-clean-runtime-argv
codex/review-2049-27f1b367
review-fixes/pr-2787-routing
fix/3360-scoped-this-emitters
fix/3367-replaced-global-effects
fix/3838-compact-any-value-items
test/hopper-download-probe-20261015
codex/windows-runtime-creation-red-green-20261015
codex/windows-readonly-root-red-green-20261015
codex/windows-root-share-red-green-20261015
codex/exp-1685-win-mcp-startup
codex/bug-sweep-20261015
investigate/2190-windows-package-phases
investigate/3543-macos-cli-deadline
perf/3281-reverse-tools-feedback-quality
fix/3406-hopper-doctor-fixture
fix/3341-wrapper-require-test-context
fix/3301-owned-uninstall-fixtures
fix/3164-compiler-input-ownership
fix/pcap-cleanup-stdout-newline-20261014
perf/interface-builder-summary
codex/review-fixes-pr-1977
fix/ghidra-effective-jvm-platform
fix/docs-turkish-rust-link-20261013
fix/main-maintenance-ci-20261010
fix/recover-binary-session-process-effects
codex/review-fixes-pr-2457
codex/ci-required-cancellation-gate
fix/main-format-baseline-20261013
fix/setup-preserve-entry-fields
cursor/restore-main-checks-1ffc
fix/ghidra-bridge-hashmap-import
codex/shared-ci-jadx-json-default-20261013
codex/shared-ci-ghidra-test-groups-20261013
codex/shared-ci-java-fixture-format-20261013
codex/fix-intrinsic-invocation-boundaries
test/release-preflight-reusable-jobs
test/js-parameter-provenance-expectation
fix/linux-hopper-verification-current
test/2419-ghidra-elf-probe-size
followup/pr-1544-native-ida
codex/fold-pr-2230-contribution
docs/readme-responsible-use
fix/issue-2064
fix/issue-2050
fix/issue-2053
fix/issue-1968
fix/issue-1945
experiment/codemode-bridge-20261011
fix/tool-effects-negative-wording-1904-20261012
fix/1842-electron-interop-provenance
feat/recover-javascript-multi-input
refactor/website-i18n-prep
fix/nativeaot-pe-virtual-extent
fix/browser-verifier-ci-hang
fix/pe-resources-input-selection
docs/beginner-friendly-guides
docs/beginner-setup-guide
fix/javascript-analysis-worker-1563
fix/1649-ghidra-duplicate-names
fix/javascript-export-keys-integration-1369
test/maintenance-boundary-contracts-20261011
review/javascript-export-keys-1369
review/process-live-progress-1483
test/javascript-1495-growth-ratio
fix/ci-escape-timing
docs/normalized-terminal-geometry-1450
release/6.3.0
archive/release-6.3.0-pr1381
release/6.2.0
fix/electron-preload-dynamic-override
fix/javascript-self-referential-bundler-edges
release/6.1.0
cursor/grok-client-cherry-pick-0b56
feat/signature-posture
feat/dyld-shared-cache
feat/artifact-integrity-policy
feat/pkg-inventory
release/6.0.0
chore/sync-release-5.0.0
release/5.0.0
cursor/cloud-agent-node-787e
fix/javascript-xhr-open-endpoints
review/pr-711-realpath-fallback-wording
cleanup/replay-confinement
codex/test-suite-performance
codex/issue-foundations
codex/address-open-issues-2026-07-20
agent/javascript-vite-rollup-esbuild-adapters
agent/process-cleanup
agent/triage-integration
agent/unknown-commands-registry
feat/mcp-identity-metadata
morlvps/issue_cleanup
codex/installer-redesign
morl/roadmap-investigation-core
morl/roadmap-investigation-docs
release-please--branches--main--components--rea
rea-agents-6.8.0
rea-agents-6.7.0
rea-agents-6.6.0
experiment/atomic-codemode-wait-runtime-20261016
rea-agents-6.5.0
rea-agents-6.4.0
rea-agents-6.3.0
rea-agents-6.2.0
rea-agents-6.1.0
rea-agents-6.0.0
rea-agents-5.0.0
rea-agents-4.1.0
rea-agents-4.0.1
rea-agents-4.0.0
rea-agents-3.2.1
rea-agents-3.2.0
rea-agents-3.1.0
rea-agents-3.0.0
rea-agents-2.7.0
rea-agents-2.6.0
rea-agents-2.5.1
rea-agents-2.5.0
rea-agents-2.4.0
rea-agents-2.3.0
rea-agents-2.2.0
rea-agents-2.1.0
rea-agents-2.0.0
rea-agents-1.7.0
rea-agents-1.6.0
rea-agents-1.5.0
rea-agents-1.4.0
rea-agents-1.3.0
rea-agents-1.2.0
rea-agents-1.1.0
rea-agents-1.0.0
rea-agents-0.5.0
rea-agents-0.4.0
rea-agents-0.3.0
rea-0.2.1
rea-0.2.0
Labels
Clear labels   
area: bridge

   
area: bridge

   
area: build

   
area: build

   
area: build

   
area: cli

   
area: domain

   
area: evidence

   
area: mcp

   
area: native

   
area: providers

   
area: runtime

   
area: server

   
area: setup

   
area: tests

   
bug

   
design

   
documentation

   
enhancement

   
enhancement

   
enhancement

   
experiment

   
help wanted

   
i18n

   
invalid

   
P0: critical

   
P1: high

   
P2: medium

   
P2: medium

   
P2: medium

   
P3: low

   
performance

   
provider-request

   
pull-request
Mirrored from GitHub Pull Request

  
question

   
roadmap

   
triage
No labels
area: bridge
area: bridge
area: build
area: build
area: build
area: cli
area: domain
area: evidence
area: mcp
area: native
area: providers
area: runtime
area: server
area: setup
area: tests
bug
design
documentation
enhancement
enhancement
enhancement
experiment
help wanted
i18n
invalid
P0: critical
P1: high
P2: medium
P2: medium
P2: medium
P3: low
performance
provider-request
pull-request
question
roadmap
triage
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
morluto/rea#7697
No description provided.