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 #5936] test(setup): cover skill aliases and independent cleanup retries #7108

New issue
Open
opened 2026-11-01 21:45:26 +00:00 by bsakaguchi · 0 comments
bsakaguchi commented 2026-11-01 21:45:26 +00:00
Owner
Copy link

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/5936
Author: @dakjdakd
Created: 10/21/2026
Status: 🔄 Open

Base: main ← Head: fix/setup-skill-rollback-ownership

📝 Commits (5)

  • 111fc5b fix(setup): preserve concurrent skill edits during rollback
  • 0213368 chore: merge upstream main into setup skill fix
  • 97f2495 fix(setup): preserve primary skill failure during cleanup
  • 8ec8484 fix(setup): verify skill publication at its canonical destination
  • e4d312b test(setup): cover skill aliases and independent cleanup retries

📊 Changes

1 file changed (+171 additions, -0 deletions)

View changed files

➕ tests/boundary/filesystem/setupSkillPublicationLifecycle.test.ts (+171 -0)

📄 Description

Summary

Related to #5928. Adds six filesystem regression cases for the current SkillFilePublication owner: installation through a home-directory alias, and independent cleanup retries after either a verified installation or a later publication failure.

Main already addresses the original ownership and recovery problem in 211e3533b. Following the maintainer's scope request, this revision removes the superseded production changes from the PR diff and exercises that implementation directly. These are passing regression controls against main, rather than a claim of another reproduced runtime defect.

Problem and expected behavior

Setup installs a bundle of managed skill files. Its file-publication owner has to reconcile two different concerns: the destination must refer to the intended physical directory, and every acquired cleanup lease must remain reachable until release succeeds.

A home directory can be reached through a directory symlink, including a Windows junction. Installing through that spelling should produce the same complete bundle seen through the canonical home path. An upgrade must preserve the previous manifest in its recovery backup, and a repeat installation should report unchanged without replacing the alias.

Cleanup also needs to remain independent across files. If two publications cannot release their leases, retrying one successfully must not discard the other. This matters both after successful bundle verification and when a subsequent publication fails. In the latter case, the original write error must remain the primary diagnostic while earlier files are restored and the cleanup failures retain their own resource paths. Retrying cleanup must leave those restored files alone. After a verified installation, cleanup retries must likewise preserve the installed canonical bundle.

Change and scope

The final diff adds only tests/boundary/filesystem/setupSkillPublicationLifecycle.test.ts. It uses the real installCanonicalSkill, SkillFilePublication.prepare, publication writes, backups, and filesystem readback.

The six cases cover:

  • Fresh installation through a home-directory alias.
  • An upgrade through the alias with an existing manifest and missing references. Both alias cases check freshness through both path spellings, idempotence, and preservation of the alias; the upgrade also checks the original manifest backup.
  • Two independently blocked cleanup leases after a verified installation, without a resource scope.
  • The same verified-installation case with an ArtifactResourceScope.
  • Two independently blocked cleanup leases when preparation of the third publication throws, without a resource scope.
  • The same later-publication failure with an ArtifactResourceScope.

The cleanup cases seed every managed destination with known original contents. Only the first two real leases' release methods are gated; the test does not replace the publication implementation. It checks both attributed cleanup failures and both retained owners, unblocks one lease, confirms that the other remains pending, then releases the second. Before and after retries it verifies either the restored original contents or the canonical installed bundle. The write-failure cases additionally preserve the original cause object, reason, and write stage.

Contract and boundary impact

  • Semantic owner: the existing SkillFilePublication filesystem owner and its SetupSkill consumer; production behavior is unchanged.
  • Contribution scope: focused regression coverage within the existing setup lifecycle, as discussed in the linked maintainer comment. No additional capability or authority.
  • CLI, MCP/tool catalog, provider, bridge, evidence, and target-format contracts: unchanged.
  • Resource lifecycle: verifies retained ownership across independent release failures and partial retries, using both the returned error's retry method and the shared resource scope.
  • Generated metadata, package contents, installation code, and release metadata: unchanged. Test execution writes only isolated temporary fixtures and generated local build prerequisites.

Evidence and regression coverage

The six new cases pass against main at 79b8219f290ef6304e469d9b8c40dc2af30edba9. They cover directory identity and the final-cleanup/retry lifecycle through the production filesystem boundary. They supplement the owner controls already introduced on main; no new production fix is required by these cases.

Local execution used Windows x64, Node.js 24.22.1, and npm 11.16.0. The alias tests exercised Windows junctions. POSIX directory-symlink execution remains for CI; this local run does not establish macOS or Linux results. No real reverse-engineering provider or target interaction is involved.

Validation performed

  • npm run test:focused -- tests/boundary/filesystem/setupSkillPublicationLifecycle.test.ts — all six tests passed; required runtime and skill build preparation also passed.

  • npm run verify:test-discovery — all 2,641 test files were discovered exactly once.

  • npm run check:fast — typechecking and lint, including module-boundary verification, passed.

  • git diff --cached --check — passed.

  • npm run check — formatting and metadata checks passed, but the complete gate is blocked by main's unused staticFileUrlPath export and ObjcClassImportBindingCoverage type. Running npm run knip with the new test removed reports the same two findings. Full-gate completion remains a validation limitation for this base revision.

  • CI run 40440959853 passed static checks, package build, documentation, the three native package baselines, PR readiness, and title validation. Completion of the full gate is blocked by Apple inventory/provider-binding, Electron, SAZ, and Java-probe test failures also present in the main baseline run at 79b8219f. Several test shards were cancelled, so this run does not establish complete cross-platform execution of the six new cases.

Compatibility, safety, and release

No breaking changes, migration, production permission changes, or package metadata changes. Cleanup errors are deliberately injected into test-owned leases to check retention and retry behavior. Every test unblocks and closes its retained owners before its temporary directory is removed.

Author readiness

Human owner: @dakjdakd

  • 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 above.
  • Tests cover the selected observable behavior and meaningful failure paths.
  • Owning contracts and generated metadata were checked where applicable.
  • The final diff was checked for unrelated cleanup.

🔄 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/5936 **Author:** [@dakjdakd](https://github.com/dakjdakd) **Created:** 10/21/2026 **Status:** 🔄 Open **Base:** `main` ← **Head:** `fix/setup-skill-rollback-ownership` --- ### 📝 Commits (5) - [`111fc5b`](https://github.com/morluto/rea/commit/111fc5b68b14a96778aa49dc0aeb81c37d05935f) fix(setup): preserve concurrent skill edits during rollback - [`0213368`](https://github.com/morluto/rea/commit/02133688f40116c16d570f411a10183b770b3e3b) chore: merge upstream main into setup skill fix - [`97f2495`](https://github.com/morluto/rea/commit/97f24953471c8ea1801d0eba589ee0f9995de619) fix(setup): preserve primary skill failure during cleanup - [`8ec8484`](https://github.com/morluto/rea/commit/8ec8484c357c301ea5fdcb8ae84f72d1dab66729) fix(setup): verify skill publication at its canonical destination - [`e4d312b`](https://github.com/morluto/rea/commit/e4d312b189d2bbc6f905e86100e12492d4510d33) test(setup): cover skill aliases and independent cleanup retries ### 📊 Changes **1 file changed** (+171 additions, -0 deletions) <details> <summary>View changed files</summary> ➕ `tests/boundary/filesystem/setupSkillPublicationLifecycle.test.ts` (+171 -0) </details> ### 📄 Description ## Summary Related to #5928. Adds six filesystem regression cases for the current `SkillFilePublication` owner: installation through a home-directory alias, and independent cleanup retries after either a verified installation or a later publication failure. Main already addresses the original ownership and recovery problem in [211e3533b](https://github.com/morluto/rea/commit/211e3533b34f81ae0910ad4f53f2a3d3c8587d3e). Following the [maintainer's scope request](https://github.com/morluto/rea/pull/5936#issuecomment-6428415060), this revision removes the superseded production changes from the PR diff and exercises that implementation directly. These are passing regression controls against main, rather than a claim of another reproduced runtime defect. ## Problem and expected behavior Setup installs a bundle of managed skill files. Its file-publication owner has to reconcile two different concerns: the destination must refer to the intended physical directory, and every acquired cleanup lease must remain reachable until release succeeds. A home directory can be reached through a directory symlink, including a Windows junction. Installing through that spelling should produce the same complete bundle seen through the canonical home path. An upgrade must preserve the previous manifest in its recovery backup, and a repeat installation should report `unchanged` without replacing the alias. Cleanup also needs to remain independent across files. If two publications cannot release their leases, retrying one successfully must not discard the other. This matters both after successful bundle verification and when a subsequent publication fails. In the latter case, the original write error must remain the primary diagnostic while earlier files are restored and the cleanup failures retain their own resource paths. Retrying cleanup must leave those restored files alone. After a verified installation, cleanup retries must likewise preserve the installed canonical bundle. ## Change and scope The final diff adds only `tests/boundary/filesystem/setupSkillPublicationLifecycle.test.ts`. It uses the real `installCanonicalSkill`, `SkillFilePublication.prepare`, publication writes, backups, and filesystem readback. The six cases cover: - Fresh installation through a home-directory alias. - An upgrade through the alias with an existing manifest and missing references. Both alias cases check freshness through both path spellings, idempotence, and preservation of the alias; the upgrade also checks the original manifest backup. - Two independently blocked cleanup leases after a verified installation, without a resource scope. - The same verified-installation case with an `ArtifactResourceScope`. - Two independently blocked cleanup leases when preparation of the third publication throws, without a resource scope. - The same later-publication failure with an `ArtifactResourceScope`. The cleanup cases seed every managed destination with known original contents. Only the first two real leases' `release` methods are gated; the test does not replace the publication implementation. It checks both attributed cleanup failures and both retained owners, unblocks one lease, confirms that the other remains pending, then releases the second. Before and after retries it verifies either the restored original contents or the canonical installed bundle. The write-failure cases additionally preserve the original cause object, reason, and write stage. ## Contract and boundary impact - Semantic owner: the existing `SkillFilePublication` filesystem owner and its `SetupSkill` consumer; production behavior is unchanged. - Contribution scope: focused regression coverage within the existing setup lifecycle, as discussed in the linked maintainer comment. No additional capability or authority. - CLI, MCP/tool catalog, provider, bridge, evidence, and target-format contracts: unchanged. - Resource lifecycle: verifies retained ownership across independent release failures and partial retries, using both the returned error's retry method and the shared resource scope. - Generated metadata, package contents, installation code, and release metadata: unchanged. Test execution writes only isolated temporary fixtures and generated local build prerequisites. ## Evidence and regression coverage The six new cases pass against main at `79b8219f290ef6304e469d9b8c40dc2af30edba9`. They cover directory identity and the final-cleanup/retry lifecycle through the production filesystem boundary. They supplement the owner controls already introduced on main; no new production fix is required by these cases. Local execution used Windows x64, Node.js 24.22.1, and npm 11.16.0. The alias tests exercised Windows junctions. POSIX directory-symlink execution remains for CI; this local run does not establish macOS or Linux results. No real reverse-engineering provider or target interaction is involved. ## Validation performed - `npm run test:focused -- tests/boundary/filesystem/setupSkillPublicationLifecycle.test.ts` — all six tests passed; required runtime and skill build preparation also passed. - `npm run verify:test-discovery` — all 2,641 test files were discovered exactly once. - `npm run check:fast` — typechecking and lint, including module-boundary verification, passed. - `git diff --cached --check` — passed. - `npm run check` — formatting and metadata checks passed, but the complete gate is blocked by main's unused `staticFileUrlPath` export and `ObjcClassImportBindingCoverage` type. Running `npm run knip` with the new test removed reports the same two findings. Full-gate completion remains a validation limitation for this base revision. - [CI run 40440959853](https://github.com/morluto/rea/actions/runs/40440959853) passed static checks, package build, documentation, the three native package baselines, PR readiness, and title validation. Completion of the full gate is blocked by Apple inventory/provider-binding, Electron, SAZ, and Java-probe test failures also present in the [main baseline run at `79b8219f`](https://github.com/morluto/rea/actions/runs/40440009919). Several test shards were cancelled, so this run does not establish complete cross-platform execution of the six new cases. ## Compatibility, safety, and release No breaking changes, migration, production permission changes, or package metadata changes. Cleanup errors are deliberately injected into test-owned leases to check retention and retry behavior. Every test unblocks and closes its retained owners before its temporary directory is removed. ## Author readiness Human owner: @dakjdakd - [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 above. - [x] Tests cover the selected observable behavior and meaningful failure paths. - [x] Owning contracts and generated metadata were checked where applicable. - [x] The final diff was checked for unrelated cleanup. --- <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#7108
No description provided.