morluto/rea

Fork 0

mirror of https://github.com/morluto/rea.git synced 2026-11-05 06:45:22 +00:00

[PR #4031] feat(artifacts): select extraction entries and output destination #6002

New issue

Open

opened 2026-10-31 01:11:05 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-31 01:11:05 +00:00

Owner

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/4031
Author: @jsk1004ha
Created: 10/15/2026
Status: 🔄 Open

Base: main ← Head: feat/artifact-selection-3490

📝 Commits (8)

9c72458 feat(artifacts): select extraction entries and output destination
60c3c21 fix(artifacts): omit absent selection from execution parameters
5901a36 fix(artifacts): protect source directories and verify public selection
3d2920e fix(artifacts): keep optional selection inputs JSON-safe
e23a802 fix(artifacts): preserve selected occurrence and destination identity
917730a fix(artifacts): separate reader ownership from selected destinations
92eb9a0 fix(artifacts): sync extraction selection with current main
204766d fix(artifacts): advertise absolute extraction destinations

📊 Changes

13 files changed (+1099 additions, -57 deletions)

View changed files

📝 docs/mcp-contracts.md (+20 -0)
📝 src/application/artifacts/ArtifactExtractionDestination.ts (+5 -3)
📝 src/artifacts/ArtifactProvider.ts (+3 -0)
📝 src/artifacts/extraction/ArtifactExtraction.ts (+59 -41)
➕ src/artifacts/extraction/ArtifactExtractionSelection.ts (+77 -0)
📝 src/cli/artifactCommands.ts (+18 -2)
📝 src/contracts/artifactToolContracts.ts (+23 -5)
📝 src/server/registerArtifactTools.ts (+12 -5)
➕ tests/acceptance/artifactExtractionSelection.test.ts (+177 -0)
📝 tests/boundary/mcp/absoluteLocalPathSchema.test.ts (+6 -0)
📝 tests/boundary/mcp/unityFsMcp.test.ts (+13 -1)
➕ tests/boundary/providers/native/artifactProvider.extractionDestination.test.ts (+61 -0)
➕ tests/boundary/providers/native/artifactProvider.extractionSelection.test.ts (+625 -0)

📄 Description

Summary

Fixes #3490.

extract_artifact can now write to a caller-selected destination and extract only selected inventory occurrences. This lets a caller take a native library from an APK without materializing unrelated resources whose names collide on the destination filesystem. Omitting both options keeps the existing all-file extraction into a fresh temporary directory.

Change and scope

The CLI accepts --output-root and repeatable --occurrence-id flags. MCP exposes the same options as output_root and occurrence_ids. Selection uses occurrence identity rather than content identity, so two paths with identical bytes can be selected independently.

Selection is resolved against the active reader's complete inventory before output creation. Unknown, duplicate, empty, root, directory, link and nested-member selections are refused. Nested archive members remain outside this change: extract their containing archive and inspect it separately. No glob matching is added.

Full reader-inventory consistency checks are kept separate from materialization. Deliberately excluded files are not mistaken for missing entries, while unexpected or missing regular entries still prevent publication. Selected writes retain their expected hashes and lengths, and failures use the existing owned-output rollback.

A custom destination must be absolute, absent, and have an existing parent. Existing destinations are never overwritten. The resolved output parent is checked before creating the tree, preventing extraction into the source directory through either a direct path or a symlink alias. Successful output remains available after the operation and after closing the session.

Contract and boundary impact

Semantic owner: ArtifactExtractionSelection selects active occurrences; ArtifactExtraction verifies and materializes them. SafeOutputTree keeps output ownership and cleanup.
Contribution scope: ordinary archive extraction within the existing provider; a separate advance scope decision is not applicable. No new provider, target execution, instrumentation, decryption or network access is introduced.
CLI/MCP: two optional, additive inputs. No existing required input changes.
Evidence: the extraction manifest records the selected occurrence IDs; selection order and output location do not change its identity. The source inventory manifest is preserved.
Compatibility: existing artifact readers and default selection remain in place. Windows-specific behavior has not been exercised on a Windows host.
Generated metadata: catalog/documentation checks ran; generated outputs and validation-only workflows are not part of this branch.

Expected effects:

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.

The write effect is limited to extraction output and its cleanup. Target bytes are not modified.

Evidence and regression coverage

Added 19 tests across selection, destination protection and public CLI/MCP acceptance. Coverage includes identical-content occurrences, omitted selection, excluded case-distinct names, invalid IDs, request-order independence, nested-member refusal, existing destinations, cancellation, changed bytes and rollback, source-directory aliases, repeated CLI flags, CLI/MCP manifest parity, and output persistence after close_binary.

The original limitation is documented in #3490. Source inspection of base 6fcfc5b5 confirms that the adapter chose the temporary root and exposed no occurrence selection. The original third-party APK and its Windows bind-mount reproduction were not independently rerun. The executed checks use self-generated archives and directories, including case-distinct resource names.

The public acceptance test selects lib/selected.so and lib/other.so from a ZIP that also contains res/2f.xml and res/2F.xml. These are the result fields asserted by that passing CLI test, with its temporary directory abbreviated:

{
  "output_root": "<temporary-test-root>/chosen-output",
  "artifacts": [
    { "relative_path": "lib/other.so" },
    { "relative_path": "lib/selected.so" }
  ]
}

The single-file CLI and stdio MCP calls return identical artifact lists and extraction manifests. The tests also check that no res directory is materialized and that extracted files remain readable after close_binary.

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

Verified source: 3d2920e2e4c9f31f1978015c8809b9071117a1b3.

Linux and macOS verification run.

Node 24.18.0 / npm 11.16.0, locked dependencies.
Linux: npm run test:focused -- the 11 extraction, output-ownership and public-acceptance files listed in the run — 73 passed.
macOS arm64: npm run test:focused -- the six selection, destination, extraction, archive-safety, output-tree and public-acceptance files listed in the run — 42 passed, 1 skipped.
Linux: npm run check — passed, including type checking, lint, formatting, Knip, metadata and architecture checks. Existing repository lint warnings remain.
Linux: npm run verify:test-discovery — passed.
Linux: npm run docs:check — passed, including the generated catalog and five README consistency tests.

Earlier iterations failed on optional-property typing and test/harness expectations; those were corrected before this verified revision. These results do not claim the full repository suite, real Windows coverage, or a performance improvement. Inventory still covers the complete input, so subset extraction is not a promise of proportionally lower inventory time or memory use.

Compatibility, safety, and release

No new dependency or migration is required. Caller-owned output is refused rather than replaced. Existing containment, integrity, cancellation and cleanup checks remain; the existing portable pathname-race limitation is unchanged. Nested extraction, wildcard selection and encrypted-entry recovery are not included.

Author readiness

Human owner: @jsk1004ha

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.

Review fixes and validation — 2026-10-27

Synchronized with upstream 6749bd090 and resolved all six conflicts. ZIP extraction now preserves ordered occurrence identity for duplicate paths, including selecting the second occurrence or excluding all duplicates; selecting conflicting output destinations is rejected before writing. Destination handling preserves symlink-sensitive parent traversal, rejects missing parents, and returns the actual canonical output root. Optional CLI fields now use the correct optional schema wrappers, and directory fixtures follow source admission requirements.

Validation on the final synchronized tree:

92/92 tests passed across 11 files, including CLI/MCP acceptance, CLI schema consistency, duplicate ZIP selection, canonical destinations, source identity/admission, rollback, and extraction completeness.
npm run check:fast, build, formatting, and staged diff checks passed.
Documentation validation passed with 9 README consistency tests before four nonoverlapping upstream commits.
Fresh upstream CI reports action_required; test-job execution awaits workflow approval.

Existing human declarations above are preserved.

Follow-up review fixes

Published 917730ac79e23113da8cb00f8723290e575917aa after validating the fresh review findings:

Full reader inventory/path validation is separate from destination collision checking, so excluded PyInstaller file/directory declarations do not block unrelated selected entries. Conflicting selected destinations are still refused.
Active-reader membership follows occurrence-parent ownership through directories, allowing independently owned prefix-sharing names while refusing nested-reader members.
MCP lifecycle and analysis acceptance calls use artifactMcpCall to discover and validate advertised public schemas.

The final 57/57 focused cases passed: 10 extraction unit, 31 selection, 14 completeness, and 2 CLI/MCP acceptance cases. These include real PyInstaller/ASAR fixtures and excluded-entry missing/added/unsafe-path regressions. npm run check:fast, formatting, and staged diff checks also passed. All three corresponding follow-up review threads are resolved; full upstream CI remains subject to workflow approval.

Main synchronization and validation (2026-11-05)

Merged upstream 71f680d7c1aa7a45ba0325fe87b104744b0c105f into this branch as 92eb9a05e02e2ff42409755c11e5792e9da82044. The extraction conflict is resolved while preserving occurrence selection, destination handling, and the upstream UnityFS/wxapkg directory-status refusals. UnityFS MCP now also verifies unsupported-layout extraction refusal and absence of the requested output directory under both schema profiles.

Validation on the published tree, on Linux with Node 24.22.1 and the available npm 11.9.0 (the repository pins npm 11.16.0):

180/180 tests passed across 19 focused files, covering selection, destinations, source admission/identity, inventory completeness, output ownership/rollback, CLI/MCP acceptance, and UnityFS/wxapkg. The strengthened UnityFS MCP cases were rerun: 2/2 passed.
Runtime compilation, typecheck, ordinary lint, formatting, Knip, metadata, module-boundary and architecture checks passed.
Typed lint limited to all 11 changed TypeScript files passed with 0 errors and 13 warnings.
npm run docs:check passed, including 9 README consistency tests. Test discovery found all 3031 test files exactly once.
The complete npm run check did not finish successfully: its repository-wide typed-lint subprocess was terminated by SIGKILL. Earlier stages passed; the focused typed-lint rerun does not replace a full-repository pass.

GitHub now reports the PR as conflict-free. CI, CodeQL, and PR title for this exact revision are action_required and await upstream workflow approval. The complete test suite and Windows behavior were not rerun. Existing human declarations above are unchanged.

Advertised extraction-path constraint

Follow-up commit 204766d9d7d1ea6a9cc142414b034ba409796ee0 replaces the runtime-only isAbsolute refinement with the shared absoluteLocalPathStringSchema. The runtime, CLI and SDK-converted MCP schema now share the host-absolute, nonempty and NUL-free constraint. The existing advertised-path/MCP-handler matrix now includes extract_artifact.output_root.

The new advertised-schema assertion first reproduced the defect by accepting a relative output root, then passed after the fix. Final validation: 64/64 cases across 7 files, npm run check:fast, runtime build, formatting, staged diff checks, and npm run docs:check including 9 README tests passed. Typed lint for the two follow-up files passed with 0 errors and 0 warnings. The earlier repository-wide typed-lint SIGKILL limitation remains; these results are focused checks, not the complete test suite.

The published head remains conflict-free. Its CI, CodeQL, and PR-title run are still action_required, awaiting upstream workflow approval.

_{🔄 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/4031 **Author:** [@jsk1004ha](https://github.com/jsk1004ha) **Created:** 10/15/2026 **Status:** 🔄 Open **Base:** `main` ← **Head:** `feat/artifact-selection-3490` --- ### 📝 Commits (8) - [`9c72458`](https://github.com/morluto/rea/commit/9c724583e406803a82b404d3158e26b8013ec463) feat(artifacts): select extraction entries and output destination - [`60c3c21`](https://github.com/morluto/rea/commit/60c3c213d736757e057598fab49a7b1d999a0792) fix(artifacts): omit absent selection from execution parameters - [`5901a36`](https://github.com/morluto/rea/commit/5901a36324b6660c1a5964581418074cdb22c20f) fix(artifacts): protect source directories and verify public selection - [`3d2920e`](https://github.com/morluto/rea/commit/3d2920e2e4c9f31f1978015c8809b9071117a1b3) fix(artifacts): keep optional selection inputs JSON-safe - [`e23a802`](https://github.com/morluto/rea/commit/e23a802c33df29b38ea2278a53dd93c5391b0a74) fix(artifacts): preserve selected occurrence and destination identity - [`917730a`](https://github.com/morluto/rea/commit/917730ac79e23113da8cb00f8723290e575917aa) fix(artifacts): separate reader ownership from selected destinations - [`92eb9a0`](https://github.com/morluto/rea/commit/92eb9a05e02e2ff42409755c11e5792e9da82044) fix(artifacts): sync extraction selection with current main - [`204766d`](https://github.com/morluto/rea/commit/204766d9d7d1ea6a9cc142414b034ba409796ee0) fix(artifacts): advertise absolute extraction destinations ### 📊 Changes **13 files changed** (+1099 additions, -57 deletions) <details> <summary>View changed files</summary> 📝 `docs/mcp-contracts.md` (+20 -0) 📝 `src/application/artifacts/ArtifactExtractionDestination.ts` (+5 -3) 📝 `src/artifacts/ArtifactProvider.ts` (+3 -0) 📝 `src/artifacts/extraction/ArtifactExtraction.ts` (+59 -41) ➕ `src/artifacts/extraction/ArtifactExtractionSelection.ts` (+77 -0) 📝 `src/cli/artifactCommands.ts` (+18 -2) 📝 `src/contracts/artifactToolContracts.ts` (+23 -5) 📝 `src/server/registerArtifactTools.ts` (+12 -5) ➕ `tests/acceptance/artifactExtractionSelection.test.ts` (+177 -0) 📝 `tests/boundary/mcp/absoluteLocalPathSchema.test.ts` (+6 -0) 📝 `tests/boundary/mcp/unityFsMcp.test.ts` (+13 -1) ➕ `tests/boundary/providers/native/artifactProvider.extractionDestination.test.ts` (+61 -0) ➕ `tests/boundary/providers/native/artifactProvider.extractionSelection.test.ts` (+625 -0) </details> ### 📄 Description ## Summary Fixes #3490. `extract_artifact` can now write to a caller-selected destination and extract only selected inventory occurrences. This lets a caller take a native library from an APK without materializing unrelated resources whose names collide on the destination filesystem. Omitting both options keeps the existing all-file extraction into a fresh temporary directory. ## Change and scope The CLI accepts `--output-root` and repeatable `--occurrence-id` flags. MCP exposes the same options as `output_root` and `occurrence_ids`. Selection uses occurrence identity rather than content identity, so two paths with identical bytes can be selected independently. Selection is resolved against the active reader's complete inventory before output creation. Unknown, duplicate, empty, root, directory, link and nested-member selections are refused. Nested archive members remain outside this change: extract their containing archive and inspect it separately. No glob matching is added. Full reader-inventory consistency checks are kept separate from materialization. Deliberately excluded files are not mistaken for missing entries, while unexpected or missing regular entries still prevent publication. Selected writes retain their expected hashes and lengths, and failures use the existing owned-output rollback. A custom destination must be absolute, absent, and have an existing parent. Existing destinations are never overwritten. The resolved output parent is checked before creating the tree, preventing extraction into the source directory through either a direct path or a symlink alias. Successful output remains available after the operation and after closing the session. ## Contract and boundary impact - Semantic owner: `ArtifactExtractionSelection` selects active occurrences; `ArtifactExtraction` verifies and materializes them. `SafeOutputTree` keeps output ownership and cleanup. - Contribution scope: ordinary archive extraction within the existing provider; a separate advance scope decision is not applicable. No new provider, target execution, instrumentation, decryption or network access is introduced. - CLI/MCP: two optional, additive inputs. No existing required input changes. - Evidence: the extraction manifest records the selected occurrence IDs; selection order and output location do not change its identity. The source inventory manifest is preserved. - Compatibility: existing artifact readers and default selection remain in place. Windows-specific behavior has not been exercised on a Windows host. - Generated metadata: catalog/documentation checks ran; generated outputs and validation-only workflows are not part of this branch. Expected effects: - [x] Read existing files or captured data. - [ ] Launch or attach to a process. - [ ] Inject instrumentation or run scripts/code. - [x] 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. The write effect is limited to extraction output and its cleanup. Target bytes are not modified. ## Evidence and regression coverage Added 19 tests across selection, destination protection and public CLI/MCP acceptance. Coverage includes identical-content occurrences, omitted selection, excluded case-distinct names, invalid IDs, request-order independence, nested-member refusal, existing destinations, cancellation, changed bytes and rollback, source-directory aliases, repeated CLI flags, CLI/MCP manifest parity, and output persistence after `close_binary`. The original limitation is documented in #3490. Source inspection of base `6fcfc5b5` confirms that the adapter chose the temporary root and exposed no occurrence selection. The original third-party APK and its Windows bind-mount reproduction were not independently rerun. The executed checks use self-generated archives and directories, including case-distinct resource names. The public acceptance test selects `lib/selected.so` and `lib/other.so` from a ZIP that also contains `res/2f.xml` and `res/2F.xml`. These are the result fields asserted by that passing CLI test, with its temporary directory abbreviated: ```json { "output_root": "<temporary-test-root>/chosen-output", "artifacts": [ { "relative_path": "lib/other.so" }, { "relative_path": "lib/selected.so" } ] } ``` The single-file CLI and stdio MCP calls return identical artifact lists and extraction manifests. The tests also check that no `res` directory is materialized and that extracted files remain readable after `close_binary`. - [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 Verified source: `3d2920e2e4c9f31f1978015c8809b9071117a1b3`. [Linux and macOS verification run](https://github.com/jsk1004ha/rea/actions/runs/38702595598). - Node 24.18.0 / npm 11.16.0, locked dependencies. - Linux: `npm run test:focused --` the 11 extraction, output-ownership and public-acceptance files listed in the run — **73 passed**. - macOS arm64: `npm run test:focused --` the six selection, destination, extraction, archive-safety, output-tree and public-acceptance files listed in the run — **42 passed, 1 skipped**. - Linux: `npm run check` — passed, including type checking, lint, formatting, Knip, metadata and architecture checks. Existing repository lint warnings remain. - Linux: `npm run verify:test-discovery` — passed. - Linux: `npm run docs:check` — passed, including the generated catalog and five README consistency tests. Earlier iterations failed on optional-property typing and test/harness expectations; those were corrected before this verified revision. These results do not claim the full repository suite, real Windows coverage, or a performance improvement. Inventory still covers the complete input, so subset extraction is not a promise of proportionally lower inventory time or memory use. ## Compatibility, safety, and release No new dependency or migration is required. Caller-owned output is refused rather than replaced. Existing containment, integrity, cancellation and cleanup checks remain; the existing portable pathname-race limitation is unchanged. Nested extraction, wildcard selection and encrypted-entry recovery are not included. ## Author readiness Human owner: @jsk1004ha - [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. ## Review fixes and validation — 2026-10-27 Synchronized with upstream `6749bd090` and resolved all six conflicts. ZIP extraction now preserves ordered occurrence identity for duplicate paths, including selecting the second occurrence or excluding all duplicates; selecting conflicting output destinations is rejected before writing. Destination handling preserves symlink-sensitive parent traversal, rejects missing parents, and returns the actual canonical output root. Optional CLI fields now use the correct optional schema wrappers, and directory fixtures follow source admission requirements. Validation on the final synchronized tree: - **92/92 tests passed across 11 files**, including CLI/MCP acceptance, CLI schema consistency, duplicate ZIP selection, canonical destinations, source identity/admission, rollback, and extraction completeness. - `npm run check:fast`, build, formatting, and staged diff checks passed. - Documentation validation passed with 9 README consistency tests before four nonoverlapping upstream commits. - Fresh upstream CI reports `action_required`; test-job execution awaits workflow approval. Existing human declarations above are preserved. ### Follow-up review fixes Published `917730ac79e23113da8cb00f8723290e575917aa` after validating the fresh review findings: - Full reader inventory/path validation is separate from destination collision checking, so excluded PyInstaller file/directory declarations do not block unrelated selected entries. Conflicting selected destinations are still refused. - Active-reader membership follows occurrence-parent ownership through directories, allowing independently owned prefix-sharing names while refusing nested-reader members. - MCP lifecycle and analysis acceptance calls use `artifactMcpCall` to discover and validate advertised public schemas. The final **57/57 focused cases** passed: 10 extraction unit, 31 selection, 14 completeness, and 2 CLI/MCP acceptance cases. These include real PyInstaller/ASAR fixtures and excluded-entry missing/added/unsafe-path regressions. `npm run check:fast`, formatting, and staged diff checks also passed. All three corresponding follow-up review threads are resolved; full upstream CI remains subject to workflow approval. ## Main synchronization and validation (2026-11-05) Merged upstream `71f680d7c1aa7a45ba0325fe87b104744b0c105f` into this branch as [`92eb9a05e02e2ff42409755c11e5792e9da82044`](https://github.com/jsk1004ha/rea/commit/92eb9a05e02e2ff42409755c11e5792e9da82044). The extraction conflict is resolved while preserving occurrence selection, destination handling, and the upstream UnityFS/wxapkg directory-status refusals. UnityFS MCP now also verifies unsupported-layout extraction refusal and absence of the requested output directory under both schema profiles. Validation on the published tree, on Linux with Node 24.22.1 and the available npm 11.9.0 (the repository pins npm 11.16.0): - **180/180 tests passed across 19 focused files**, covering selection, destinations, source admission/identity, inventory completeness, output ownership/rollback, CLI/MCP acceptance, and UnityFS/wxapkg. The strengthened UnityFS MCP cases were rerun: **2/2 passed**. - Runtime compilation, typecheck, ordinary lint, formatting, Knip, metadata, module-boundary and architecture checks passed. - Typed lint limited to all **11 changed TypeScript files** passed with **0 errors** and 13 warnings. - `npm run docs:check` passed, including **9 README consistency tests**. Test discovery found all **3031 test files exactly once**. - The complete `npm run check` did **not** finish successfully: its repository-wide typed-lint subprocess was terminated by **SIGKILL**. Earlier stages passed; the focused typed-lint rerun does not replace a full-repository pass. GitHub now reports the PR as conflict-free. [CI](https://github.com/morluto/rea/actions/runs/41967873386), [CodeQL](https://github.com/morluto/rea/actions/runs/41967873319), and [PR title](https://github.com/morluto/rea/actions/runs/41967873343) for this exact revision are `action_required` and await upstream workflow approval. The complete test suite and Windows behavior were not rerun. Existing human declarations above are unchanged. ### Advertised extraction-path constraint Follow-up commit [`204766d9d7d1ea6a9cc142414b034ba409796ee0`](https://github.com/jsk1004ha/rea/commit/204766d9d7d1ea6a9cc142414b034ba409796ee0) replaces the runtime-only `isAbsolute` refinement with the shared `absoluteLocalPathStringSchema`. The runtime, CLI and SDK-converted MCP schema now share the host-absolute, nonempty and NUL-free constraint. The existing advertised-path/MCP-handler matrix now includes `extract_artifact.output_root`. The new advertised-schema assertion first reproduced the defect by accepting a relative output root, then passed after the fix. Final validation: **64/64 cases across 7 files**, `npm run check:fast`, runtime build, formatting, staged diff checks, and `npm run docs:check` including **9 README tests** passed. Typed lint for the two follow-up files passed with **0 errors and 0 warnings**. The earlier repository-wide typed-lint SIGKILL limitation remains; these results are focused checks, not the complete test suite. The published head remains conflict-free. Its [CI](https://github.com/morluto/rea/actions/runs/41969191594), [CodeQL](https://github.com/morluto/rea/actions/runs/41969191556), and [PR-title run](https://github.com/morluto/rea/actions/runs/41969191500) are still `action_required`, awaiting upstream workflow approval. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

bsakaguchi added the

pull-request

label

2026-10-31 01:11:05 +00:00

bsakaguchi referenced this issue

2026-11-01 21:45:33 +00:00

[PR #6018] [CLOSED] fix(wasm): preserve caller cancellation reason during active WABT inspection (#6002) #7123

bsakaguchi referenced this issue

2026-11-01 21:45:52 +00:00

[PR #6151] [CLOSED] fix(cancellation): preserve the caller abort reason #7168