feat(gateway): expose Mos coordination boundary #737

jason.woltje · 2026-07-13T12:59:13Z

jason.woltje commented

2026-07-13 12:59:13 +00:00

Summary

add AuthGuard-protected handoff, observe, and result routes for the existing Mos coordination service
derive actor and tenant only from the authenticated session; require correlation header before service invocation
preserve the existing server-configured requester identity and all service authority checks

Verification

pnpm --filter @mosaicstack/gateway test -- mos-coordination.controller.test.ts
pnpm --filter @mosaicstack/gateway typecheck
pnpm --filter @mosaicstack/gateway lint

Part of TESS-M4-W / #710.

## Summary - add AuthGuard-protected handoff, observe, and result routes for the existing Mos coordination service - derive actor and tenant only from the authenticated session; require correlation header before service invocation - preserve the existing server-configured requester identity and all service authority checks ## Verification - `pnpm --filter @mosaicstack/gateway test -- mos-coordination.controller.test.ts` - `pnpm --filter @mosaicstack/gateway typecheck` - `pnpm --filter @mosaicstack/gateway lint` Part of TESS-M4-W / #710.

jason.woltje added 1 commit 2026-07-13 12:59:14 +00:00

feat(gateway): expose Mos coordination boundary

ci/woodpecker/pr/ci Pipeline was successful

Details

f7b95f6066

jason.woltje referenced this issue from a commit

2026-07-13 13:01:37 +00:00

docs(tess): M4-W-001 split — #737 Mos-consumer slice open; provider-reg + memory-consumer BLOCKED (design ruling to Mos)

jason.woltje commented

2026-07-13 13:10:51 +00:00

VERIFIED APPROVE reviewer-of-record [W-jarvis:reviewer] head f7b95f6066

Findings: CI pipeline 1758 is green at the exact head. This partial slice is limited to the AuthGuard-protected Mos coordination consumer routes plus module registration; it exposes only handoff, observe, and result, with no runtime-provider registration or operator-memory consumer changes.
The controller derives actor/tenant scope via CurrentUser/scopeFromUser, requires X-Correlation-Id before service invocation, and leaves the previously reviewed MosCoordinationService authority boundary unchanged. apps/gateway/src/commands/command-authorization.service.ts is byte-identical to origin/main (hash a9f829e7ecec721c6c585fe0da56fb5d6a6441e9); no live creds or hardcoded Tess identity were introduced.

Marker: ROR-737-APPROVE-f7b95f60

VERIFIED APPROVE reviewer-of-record [W-jarvis:reviewer] head f7b95f60666a4abbbad9a08669637b19fa87c430 Findings: CI pipeline `1758` is green at the exact head. This partial slice is limited to the AuthGuard-protected Mos coordination consumer routes plus module registration; it exposes only `handoff`, `observe`, and `result`, with no runtime-provider registration or operator-memory consumer changes. The controller derives actor/tenant scope via `CurrentUser`/`scopeFromUser`, requires `X-Correlation-Id` before service invocation, and leaves the previously reviewed MosCoordinationService authority boundary unchanged. `apps/gateway/src/commands/command-authorization.service.ts` is byte-identical to `origin/main` (hash `a9f829e7ecec721c6c585fe0da56fb5d6a6441e9`); no live creds or hardcoded Tess identity were introduced. Marker: ROR-737-APPROVE-f7b95f60

jason.woltje referenced this issue from a commit

2026-07-13 13:12:47 +00:00

docs(tess): M4-W CI-green + ROR sync — #737 ROR-complete (17054, head f7b95f60), #738 CI-green ROR-routed (head 582c6db2)

jason.woltje merged commit e2376190e5 into main

2026-07-13 13:14:45 +00:00

jason.woltje deleted branch fix/tess-m4-reachability

2026-07-13 13:14:45 +00:00

jason.woltje referenced this issue from a commit

2026-07-13 13:14:46 +00:00

feat(gateway): expose Mos coordination boundary (#737)

jason.woltje referenced this pull request

2026-07-13 15:07:44 +00:00