Skip to content

fix(team): use manifest.v2 as canonical team cwd metadata source#1114

Merged
Yeachan-Heo merged 1 commit intoYeachan-Heo:devfrom
wwenrr:fix/1108-manifest-canonical-cwd
Apr 1, 2026
Merged

fix(team): use manifest.v2 as canonical team cwd metadata source#1114
Yeachan-Heo merged 1 commit intoYeachan-Heo:devfrom
wwenrr:fix/1108-manifest-canonical-cwd

Conversation

@wwenrr
Copy link
Copy Markdown
Contributor

@wwenrr wwenrr commented Apr 1, 2026

Summary

  • remove non-canonical team cwd metadata fallbacks in resolveTeamWorkingDirectoryFromMetadata
  • resolve team working directory from manifest.v2.json only (plus OMX_TEAM_STATE_ROOT env override)
  • add regression coverage proving manifest metadata wins even if config.json metadata points elsewhere

Why

Issue #1108 tracks seam-gap cleanup after the thin-adapter cutover. This PR addresses acceptance criterion: one canonical metadata source for team state-root / working-directory resolution.

Verification

  • npm run build
  • node --test dist/team/__tests__/api-interop.test.js dist/compat/__tests__/rust-runtime-compat.test.js

Closes #1108

@github-actions github-actions Bot added the size/M label Apr 1, 2026
@Yeachan-Heo
Copy link
Copy Markdown
Owner

CI failure is unrelated to your changes — it's a known flaky test in notify-fallback-watcher.test.js (Ralph debounce race condition, expected: 1, actual: 2). Your PR only touches api-interop.ts and compat tests.

Re-running CI.


[repo owner's gaebal-gajae (clawdbot) 🦞]

@Yeachan-Heo Yeachan-Heo merged commit d616703 into Yeachan-Heo:dev Apr 1, 2026
26 of 28 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants