Repository navigation
chore(main): release rea-agents 6.9.0 - #7104
Conversation
Codex Review Summary: ✅ CompletedThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
[Medium impact] The release references reach package and plugin installation paths. Not ready to merge: the previously reported missing Findings
Fix with agent prompt### Issue 1
CHANGELOG.md:undefined-43
The release workflow will reject this bullet before creating a tag. Commit `5cf7133` has a `!` subject but no `BREAKING CHANGE:` footer, so `validateCandidate` requires its short SHA or PR number inside `BREAKING CHANGES`. This bullet has neither. The link under `Code Refactoring` does not count because the check reads only the breaking-change section.
Add `5cf7133` to this bullet. Migration prose alone will not satisfy the check.
### Issue 2
CHANGELOG.md:undefined-633
The 6.9.0 notes list #7119's 64 KiB fix, but commit `5d428390996498bc4dcca4da934641557f9109bc` explicitly reverted it before this release. The `full` profile still keeps complete schemas without that limit. Users whose clients reject large schemas may upgrade expecting a fix that is not included. Remove this entry or explain the revert.
```suggestion
```
### Issue 3
CHANGELOG.md:undefined-43
The JavaScript breaking-change entry does not name the removed `renderer` property or its replacement. Users reading these notes cannot tell how to update their clients. Explain that package observations now use `renderer_declarations` for source fields and `loads` edges for the selected candidate. Also note that previously retained evidence remains readable.
Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!
### Issue 4
CHANGELOG.md:undefined-932
The 6.9.0 performance list advertises `855eb70`'s prewarm improvement, but `c77735f` removed the setup prewarm step before this release. The installation guide confirms that setup no longer runs it. Remove this entry or mark it as superseded so users are not promised an improvement to code that no longer ships.
```suggestion
```
### Issue 5
CHANGELOG.md:undefined-1200
The `Continuous Integration` entry copies the `CI:` footer from `a95b83c`, which records checks and an admin bypass for #7508, not this release. Those counts and “Greptile 5/5, no findings” can make readers mistake an earlier change’s review results for this release’s checks. Remove the historical status paragraph or clearly label its original scope.
```suggestion
```
### Issue 6
CHANGELOG.md:undefined-842
The notes repeat `9842299` verbatim and list `cbeeeda` twice with different descriptions at lines 263–264. Each pair describes one commit, not two changes. Keep one entry per commit so readers do not have to compare duplicate claims.
Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!
### Issue 7
CHANGELOG.md:undefined-38
For `close_binary` with `snapshot_path` on a target without a replayable profile, errors now use `capability_unavailable` instead of `evidence_integrity_mismatch`. This bullet only repeats the commit title, so clients that branch on the old code get no migration guidance.
Name both codes and explain the recovery: use `export_evidence_bundle` if needed, then call `close_binary` without `snapshot_path`.
Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!
### Issue 8
CHANGELOG.md:undefined-37
The `#7847` entry does not explain the error-code change. For `import-reference-source`, roots that hit `ELOOP` or `ENAMETOOLONG` now return `invalid_request` instead of `unreadable_output`. Clients that check the old code must inspect the implementation to learn how to upgrade.
Name both codes and explain the recovery: repair the symlink chain or choose a shorter path.
### Issue 9
CHANGELOG.md:undefined-32
The #7889 entry does not explain that `trace-native-values` now rejects an empty `procedure` before opening the target. It returns `VALIDATION_ERROR` with `fieldErrors`, rather than the later `invalid_request` when the target opens successfully. Scripts that handle the old error get no migration guidance. Name the changed response and tell callers to supply a nonempty procedure symbol or address.
Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!
### Issue 10
CHANGELOG.md:undefined-33
The #7864 entry does not explain which callers are affected. When readable source entries share a normalized path, `analyze-javascript-application` now returns `artifact_operation_failed` with `details.reason: "path"`, instead of a later content-integrity failure. Explain the new reason and recovery: inspect the retained inventory, then analyze a copy whose member paths do not collide. Without that guidance, users cannot tell how to update their error handling or input.
Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!
### Issue 11
CHANGELOG.md:undefined-35
The #7903 entry does not name the changed error reason. For `trace-web-module-imports`, a relative or empty `REA_BROWSER_EXECUTABLE` now returns `capability_unavailable` with `details.reason: "invalid_browser_executable"`, instead of `"missing_browser_executable"`. Clients matching the old reason need migration guidance. Name both reasons and tell users to set an absolute Chromium path; an unset variable still uses the old reason.
Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!
### Issue 12
CHANGELOG.md:undefined-30
The `#7885` breaking note does not explain that `pull_adb_file`, `capture_adb_screen`, and `collect_adb_bugreport` now return `invalid_request` instead of `unreadable_output` when `output_directory` or a parent is a file. Clients matching the old code get no upgrade guidance.
Name both codes and tell users to choose a directory path whose parents are directories.
Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!
### Issue 13
CHANGELOG.md:undefined-31
For `build-reconstruction-obligation-ledger` and `evaluate-reconstruction-coverage`, passing one Evidence record as `evidence_bundle` now returns `invalid_request` instead of `evidence_integrity_mismatch`. This breaking note names neither code, so scripts matching the old error get no upgrade guidance.
Explain the change and tell users to pass the complete bundle from `export_evidence_bundle`. Damaged bundles still return `evidence_integrity_mismatch`.
Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!
### Issue 14
CHANGELOG.md:28-29
The #7900 and #7852 breaking notes repeat commit titles without explaining how callers should upgrade. Add the concrete changes:
- File-source errors move from `["evidence"]` to `["source", "path"]` for `export_environment_bundle`, and to `["capture"]` for `environment-build`.
- Markdown now refuses NUL, and Markdown/TOON refuse unpaired UTF-16 values. Use `--format json` or `--format yaml` to retain them.
Without these details, users must inspect the implementation to update error routing and text exports.
Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!
---
For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.(17 more issues omitted due to length limits.) SummaryPrepares
The registry metadata check passed. No new security issue was identified in the reviewed changes. Local tags show no newer release; live publication status was unavailable. Reviews (441) · Last reviewed commit: "chore(main): release rea-agents 6.9.0" · Reviewed by Greptile |
a920e33 to
764a07d
Compare
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 764a07d7fa
ℹ️ About Codex in GitHub
Codex has been enabled to automatically 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 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
5c6dcd3 to
97c6a21
Compare
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 97c6a21530
ℹ️ About Codex in GitHub
Codex has been enabled to automatically 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 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
c1a3204 to
9470244
Compare
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 947024480a
ℹ️ About Codex in GitHub
Codex has been enabled to automatically 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 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
4332ee2 to
5542d5d
Compare
9c6fce8 to
96cd503
Compare
778a369 to
c4d65a9
Compare
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 0363cd7ca3
ℹ️ About Codex in GitHub
Codex has been enabled to automatically 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 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 678b3e8e0e
ℹ️ About Codex in GitHub
Codex has been enabled to automatically 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 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: e9c7e51c4e
ℹ️ About Codex in GitHub
Codex has been enabled to automatically 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 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: e2b9b95d52
ℹ️ About Codex in GitHub
Codex has been enabled to automatically 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 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 8148d009b9
ℹ️ About Codex in GitHub
Codex has been enabled to automatically 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 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 1a800dd6a1
ℹ️ About Codex in GitHub
Codex has been enabled to automatically 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 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 127b2e3ed4
ℹ️ About Codex in GitHub
Codex has been enabled to automatically 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 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 2978e3151d
ℹ️ About Codex in GitHub
Codex has been enabled to automatically 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 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 4dac7a7aaa
ℹ️ About Codex in GitHub
Codex has been enabled to automatically 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 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 091b58273c
ℹ️ About Codex in GitHub
Codex has been enabled to automatically 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 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 160ca1a215
ℹ️ About Codex in GitHub
Codex has been enabled to automatically 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 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 5226703995
ℹ️ About Codex in GitHub
Codex has been enabled to automatically 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 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
|
🤖 Created releases: 🌻 |
🤖 I have created a release beep boop
Author readiness
Human owner: @morluto
6.9.0 (2026-11-11)
Highlights
Changes
Fixes
__chk_failFORTIFY handler import. #10136, #10036, issue morluto/rea#10025. Thanks @2SinceJuly, @coygeek, @rudycelekli.⚠ BREAKING CHANGES
effect,rea_restart_required,restart_requiredandrestartRequiredwithupdate_mode(runtime,restart,parameter) andpending_restart. Parameter-supplied limits cannot be changed by the runtime setter; restart-mode values retain their startup value until restart. #9885, be20bdfb26f7, aee1178839dd. Thanks @gensokyo-dev, @N0zoM1z0.details.secondary_failures/secondaryFailures: mixed batches keep physical/provider failures primary and retain typed cancellation with its original cause. Retained descriptors can producecleanup_incomplete; follow the returned recovery instead of treating it as ordinary cancellation. Custom adapters must consume owner-issued inspection/sampling facts and retain their cleanup scopes until release succeeds. #10141, #10113, #10109.rea mcp add --commandnow accepts a local stdio launcher only: HTTP(S) executable URLs are rejected before settings writes, and package acquisition is removed. Configure remote transports in each client’s native settings and install/select the local launcher before registration. #10102.identity.capture_evidence_idin addition to the capture digest and runtime key. Node IDs digest that identity, so regenerate reconciliation Evidence and rebuild node-keyed lookups even when the digest and runtime key are unchanged. #10063.stringsfield. Regenerate unversioned fixtures withnpm run build:fixtures. #9977.items.rows: null,coverage.status: "unavailable",coverage.total: nullandcoverage.exhausted: false; recorded empty collections still returnrows: []. Refresh schemas, stop paging unavailable data and inspectunknowns; older saved views retain their recorded facts. #9893, #8291, issue morluto/rea#8276. Thanks @Xinglan233.state.baseline_non_filesare rejected before state inspection, drafting or export; capture the application again to obtain contemporaneous SQLite member facts. #9898, #9470.save: []for request actions that save nothing, changing scenario/Evidence digests. Keep historical digests with historical captures and use freshly recorded digests for new ones. #9896.row_offsetandnext_row_offset;rows.orderisrowid,primary_keyorunspecified. A null next offset means either no continuation or no stated order: an unordered sample can still havetruncated: true. Inspect bothorderandtruncatedbefore concluding the sample is complete. #9331, issue morluto/rea#8234. Thanks @2SinceJuly, @555aaditya.evidence_id. Invalidate or re-key cached associations against the fresh Evidence, retaining old IDs only for their original observations. #9393. Thanks @HusnainMaroof.caller_input_pathsvalues may be ordered arrays of strings as well as strings. Update strict consumers to preserve repeated selections. #9626, #9624.observe_javascript_runtimeadds requiredexecution_context_idfields to scripts and contexts.context_keyis an opaque capture-local lifetime identity, not a reusable protocol ID, and Evidence identities change. Refresh schemas and recapture when new lifetime associations are needed. #9471, issue morluto/rea#3382. Thanks @coygeek.inspect_address_contextschemas: unavailable facets may carry typed input or resource-constraint errors while successful sibling facets remain available. #8444, #8424, #8419.analyze_function/trace_native_valuesrequirenative_value_flow.limitationson available and unavailable variants. Ghidra memory effects cover explicit high-p-codeLOAD/STOREoperations only; empty effects do not prove no memory access. Thevalue_flow_effect_scopeprofile commitment invalidates older snapshots: retain embedded historical Evidence, reopen without the snapshot and save a fresh one. #8651.skipped_overlays; loaded overlays no longer count as not loaded, and adjacent initialized blocks are searched with explicit coverage. Reopen targets and save fresh analysis snapshots after the profile/search-policy changes; historical Evidence stays importable. #8608, #8376, #8840, issue morluto/rea#8374, issue morluto/rea#8563, issue morluto/rea#8607.compare_functionsaddsfunction_match.method: "same-evidence"when both inputs authenticate to one Evidence ID and entry comparison is unavailable. Accept the new matched variant, retain unknown dimensions and do not infer complete equivalence; one observation cannot have contradictory changed dimensions or hashes. #8442, issue morluto/rea#8367.analyze_functioncan returnnative_value_flow: {available: false, reason, limitations}instead of null. Checkavailableand preserve the provider reason; null means procedure-scoped unrecorded unknown, not confirmed absence. The workflow-profile digest changes: older trace Evidence remains history but must be rerun to satisfy current replay. #8785, issue morluto/rea#8783.inspect_analysis_view. Discover it before use or batch it with its producer; the default full catalog remains available. #9151. Thanks @gensokyo-dev.batch_decompileand retained batch views now useitems[].status: "unavailable"withreason: "no_pseudocode"for null pseudocode, replacing the formererror/capability_unavailableitem. Empty or non-text values remainstatus: "error"withunreadable_output. Both count towardfailed; preserve item limitations and accept historical error items. #8737, issue morluto/rea#8736.import_evidence_bundle/CLIevidence-importnow reject snapshot-shaped JSON withinvalid_requestinstead ofevidence_integrity_mismatch. Restore it withopen_binary.snapshot_pathor a compatible CLI--snapshot; bundle imports require a canonical bundle fromexport_evidence_bundle. #8867.REA_BROWSER_NO_SANDBOX=truefallback disables Chromium’s sandbox and does not establish an REA isolation boundary. #8738, issue morluto/rea#8722. Thanks @chordpli, @hkeysai.gnu.objdump/GNU objdumpto{id: "objdump.command", name: "objdump command", version: null}; launch errors use the same ID and architecture-list subjects may be null. Update provider-keyed caches/readers and retain the selected executable parameters without assuming GNU semantics; historical Evidence stays readable. #8824, issue morluto/rea#8823.inspect_analysis_viewrejects mismatched native parent predicates withinvalid_requestatsource.predicate_type: function/inventory/observation views requirerea.analysis, and matching views requirerea.native-function-matching. Select the original correctly typed Evidence or rerun its producer; patching an existing predicate invalidates its identity. #8451.trace_featurecan succeed when xrefs exist but owner lookup is unavailable. Acceptreferences[].containing_procedure.status: "unavailable"with provider/reason fields instead of requiring afoundmember, and inspectresidual_unknowns;truncated: falsedoes not establish resolved ownership. #8368.close_binaryretains investigation records; usereset_investigationto clear them. Cross-process recovery requires an explicitly acknowledged Evidence-bundle checkpoint. #8361, issue morluto/rea#8347. Thanks @gensokyo-dev.compare_functionsadds the matchedfunction_match.method: "same-entry"variant with requiredentry_addresswhen authenticated artifact, architecture, mapping, slice and entry commitments agree despite a rename. Refresh schemas and keep name/identity changes separate from entry correspondence. #8263, issue morluto/rea#8213. Thanks @gensokyo-dev.inspect_native_load_imageNativeAOTmetadata_recoveryuses a status-discriminated union: complete reports requirereason: null; partial/not-applicable reports carry{code, ...}instead of prose reasons. Branch on codes and their fields while preserving historical/optional-extension strings. Invalid budgets now produce typed input/resource errors. #8053.trace_javascript_semanticsaddsinfluencesedges and moves direct literal-argument seeds from call-site to expression nodes. Relevant unknown dependencies can changefoundtopartial: handle that status and inspect unknowns. Reanalyze retained application graphs to obtain the new edges; old graphs stay readable. #7939, issue morluto/rea#7500. Thanks @Rinkia.inspect_managed_memberschangessignature_resolutionfromtype-names-v1totype-names-v2and appends readable names to signature operands, such asclass:4 (Fixture.Program). Branch on the resolution version, accept annotated v2 strings and preserve historical v1/null displays. Signature digests are unchanged;InternalCallmethods remain runtime-provided boundaries. #5309, #9547, issue morluto/rea#5149. Thanks @elricfd, @gensokyo-dev, @ln-bodicherla, @Plastic-time.resource_constraint,resource: "transport"andreported_limits.max_input_elements. For larger inline calls, setREA_MCP_MAX_INPUT_ELEMENTSto a digit-only positive decimal safe integer (1–9007199254740991) and restart, or select retained/file inputs. Fractional/exponent spellings are invalid; inputs are never truncated. #7905, issue morluto/rea#7882. Thanks @gensokyo-dev.inspect_machotext names/paths can be null for non-UTF-8 bytes, withname_bytes_hex,segment_bytes_hexandpath_bytes_hexalternatives; unsafe numeric sizes/offsets/alignments can be null with exact companion fields, and delayed-initoptionsare numeric. Refresh schemas and preserve these facts; absent byte fields in older Evidence remain unrecorded. #7952, issue morluto/rea#7391. Thanks @coygeek.evidenceissue path tocaptureforenvironment-buildandsource.pathfor environment bundle build/export. Missing/non-file/invalid UTF-8/JSON sources returninvalid_requestwithinvalid_value/invalid_formatissues andinspect_input_contractrecovery; repair the selected file. #7900, issue morluto/rea#7523. Thanks @coygeek.invalid_requestand a nonzero exit even after a successful operation; Markdown also refuses NUL. Use--format jsonor--format yamlto preserve these values rather than accepting substituted text. #7852, issue morluto/rea#7592, issue morluto/rea#7593. Thanks @coygeek.evidence_bundleinputs reject authenticated standalone records asinvalid_requestwith field-level issues instead of accepting/misclassifying them as damaged bundles. Bundle-file import/export/comparison reportsinvalid_request/invalid_inputwithdetails.reason: "wrong-kind". Supply a canonical bundle fromexport_evidence_bundle; tampered data remains an integrity failure. #7895, issue morluto/rea#7562. Thanks @coygeek.method-replayfor non-GET safe reads. Clock-generating write plans without a global clock anchor now returnserved: false,reason: "unknown-clock"instead of being served. Extend reason handling and recapture usable start times/completed durations before replaying those writes. #7834, 63220edcc3b4, issue morluto/rea#7387. Thanks @coygeek.not-in-listingfor in-memory addresses lacking listed instructions or defined data, replacing the formerundecodableinterpretation. Accept the new status and recreate snapshots after the raw-profile change; retain old embedded Evidence as history. #7823, issue morluto/rea#7490. Thanks @Entrpi.capture_process_scenario/CLI process capture rejectscolumns: 1before target launch; update both initial terminal widths and every resize to at least 2. Sensitive interactiondatais empty withsensitive/input_bytes, and raw echoes are redacted. Recapture both sides before comparing older private-input Evidence. #7848, #7804, issue morluto/rea#7582, issue morluto/rea#7782. Thanks @coygeek, @gensokyo-dev.prewarmor emits its progress events. c77735fa83a6. Thanks @gensokyo-dev.rendererproperty. Userenderer_declarationsfor source fields and package-load edges for the selected candidate; historical Evidence remains readable. 5cf7133f823b.--json=true/falsewith--json-output=true/false; bare--jsonstill selects CLI result formatting. Replacerea compare-bundleswithrea compare; MCPcompare_bundlesis unchanged. 567ea4b1e8bb, 3515b262218f.execution_failurerather thanunsupported_target; inspect retained upstream diagnostics for recovery. c4cdb7658b0e.unpacked: false. Accept an optional boolean; absent historical fields remain unknown. 60834e391c3f.MCP_ALLOWED_HOSTSorrea mcp --http --allowed-hosts. Bundle names must be unchanged HTTP hostnames within the 63-octet DNS-label limit. #7172. Thanks @DeryFerd, @gensokyo-dev.binary_session {}is compact by default and omits provider availability diagnostics/remediation, target-support diagnostics/capabilities and tool-group surface/effects/annotations. Request{"detail":"complete"}for these facts and recovery guidance. #7127, issue morluto/rea#7109. Thanks @kaoru0822-kitauji.details.operationand field-leveldetails.issues. Supply a nonemptytrace_native_values.procedure; CLItrace-native-valuesrejects an empty procedure before opening the target asVALIDATION_ERRORwithfieldErrors, while MCP reportsinvalid_requestatprocedure. #7889, issue morluto/rea#7572. Thanks @coygeek.analyze_javascript_applicationwithartifact_operation_failed,details.reason: "path"and a partial inventory instead of selecting one occurrence. Inspect the inventory and analyze a copy without collisions; all-unavailable colliding sources remain unknown. #7864, issue morluto/rea#7626. Thanks @coygeek.trace_web_module_importswith an empty/relativeREA_BROWSER_EXECUTABLEnow reportscapability_unavailablewithinvalid_browser_executableinstead ofmissing_browser_executable, retainingdetails.diagnostics.executable. Set an absolute Chromium path; an unset selection still means missing. #7903, issue morluto/rea#7639. Thanks @coygeek.import-reference-sourceroots, capture scenario files and web-network capture/Protobuf descriptor paths (ELOOP/ENAMETOOLONG) now reportinvalid_request/invalid_inputwith responsible field/host-code issues rather than generic execution/unreadable-output failures. Repair the symlink chain or choose a shorter path. #7847, #7814, issue morluto/rea#7607, issue morluto/rea#7636. Thanks @Abelo9996, @coygeek.close_binarywithsnapshot_pathon a profileless/archive target now returns nonretryablecapability_unavailableinstead ofevidence_integrity_mismatch, writes no snapshot and leaves the session open. Export needed Evidence, then close again withoutsnapshot_path. #7837, issue morluto/rea#7311. Thanks @coygeek.local_path/apk_pathand file-blockedoutput_directoryreturninvalid_requestwith field issues/host codes; output-producing calls formerly usedunreadable_output. Supply regular source files and a directory path whose parents are directories. #7885, issue morluto/rea#7549, issue morluto/rea#7550. Thanks @coygeek.EFBIG,ENOSPCorEDQUOTnow report nonretryableresource_constraint,details.reason: "storage-limit", path and optionalsystem_codeinstead ofexecution_failure/io. Raise file-size allowance or free space/quota before retrying; a failed staged-file cleanup remainscleanup_incomplete. #7887, issue morluto/rea#7573. Thanks @coygeek.unsigned_attribute_oids: fresh null means absent, an OID array means present, and omission in old Evidence is unrecorded. Unsigned attributes producecoverage.status: "partial"because nested signatures/timestamp contents remain undecoded; accept the new field and limitations. #7920, issue morluto/rea#7767. Thanks @Rinkia.resource_constraintrather thaninvalid_request/invalid_input, withmax_asn1_depth/max_oid_bytes. These format/resource bounds have no runtime override; retain the diagnostics and use an independently suitable parser when necessary. #9932.trace_call_path/build_call_pathrequire discovery and observed-result fields insearch_scope. An exhausted observed graph can still yieldgoal_status: "unknown"when provider discovery is incomplete. Refresh result schemas and workflow-profile expectations instead of equating graph exhaustion with complete discovery. #8443.inspect_native_instructionaddscontaining_instructionfornot-instruction-boundaryandcontaining_datafordata, with address/extent/identity/provenance. Accept these facts; omission in old Evidence is unrecorded. The Ghidra profile changes: reopen and save a fresh snapshot. #8777.trace_native_valuesadds requiredpage_truncatedand taggedtraversalcoverage.truncatedcombines page omission with traversal truncation; exactly filling a budget alone no longer proves truncation. Inspect page coverage before fetching another page and traversal reason before raising budgets. #8309, issue morluto/rea#8283. Thanks @kaoru0822-kitauji.batch_decompile.addresseshas a separate hard ceiling of 20,000 entries. Split larger batches into calls of at most that size; increasing the configurable MCP transport allowance cannot remove this operation limit. #5937, issue morluto/rea#5930. Thanks @dakjdakd.close_binarycan retire the target while retaining cleanup owners:cleanup_incompletemay haverecovery.kind: "retry_cleanup"despiteretryable: false. Keep the same connection open and callclose_binaryagain withoutsnapshot_pathto retry owned cleanup. #8329, issue morluto/rea#8211. Thanks @kaoru0822-kitauji.inspect_address_context,get_call_graphortrace_call_pathnow produces tool-levelcleanup_incompleterather than a successful partial result or cancellation. Keep admitted partial Evidence and follow the returned same-session cleanup recovery. #8417, #8516, issue morluto/rea#8369, issue morluto/rea#8416. Thanks @kaoru0822-kitauji.inspect_ntfs_journalomits detailedmftMetadata.record_headersby default and leaves continuation at the first omitted record. Selectmft_record_limitfrom 1 to 32 when those details are needed; inventory counts and explicit coverage remain inline. 1a8a9b749a. Thanks @gensokyo-dev, @N0zoM1z0.application.state_directories[].exists_at_start: nullplusexistence_errorwhen inspection fails (for example, access denial). Accept the tri-state field and preserve unknown instead of treating it as absence. #9899.Full contribution record: 1848 commits and 1073 merged PRs.
This PR was generated with Release Please. See documentation.