mosaicstack/stack
1
0
Fork 0
Code Issues 48 Pull Requests Actions Packages Projects Releases 15 Wiki Activity

feat(fleet): add shared role semantics #768

Merged
jason.woltje merged 7 commits from feat/758-shared-role-resolution into main 2026-07-15 00:53:48 +00:00
Conversation 0 Commits 7 Files Changed 19 +1650 -177
jason.woltje commented 2026-07-14 21:53:29 +00:00
Owner
Copy Link

Summary

  • canonicalize exactly the approved legacy role aliases before persona lookup while retaining requested and canonical identities
  • add immutable canonical-class authority metadata and asynchronous roster-v2 semantic validation through the existing shared persona resolver
  • reuse canonical readable-persona resolution in profiles and v1 provisioning, with required baseline role contracts and operator documentation

Verification

  • focused role-resolution suites: 6 files, 109 tests passed
  • full @mosaicstack/mosaic suite: 50 files, 713 tests passed
  • package typecheck and lint passed
  • repository pre-push typecheck, lint, and Prettier gates passed
  • independent code review: APPROVE
  • independent security review: APPROVE

Boundaries

  • no lifecycle, roster mutation, lease issuance, certificate workflow/storage, credentials, or v2 provisioning
  • roster-v2 semantic validation remains an explicit async handoff for later production wiring
  • issue remains open through M5

Refs #758

## Summary - canonicalize exactly the approved legacy role aliases before persona lookup while retaining requested and canonical identities - add immutable canonical-class authority metadata and asynchronous roster-v2 semantic validation through the existing shared persona resolver - reuse canonical readable-persona resolution in profiles and v1 provisioning, with required baseline role contracts and operator documentation ## Verification - focused role-resolution suites: 6 files, 109 tests passed - full @mosaicstack/mosaic suite: 50 files, 713 tests passed - package typecheck and lint passed - repository pre-push typecheck, lint, and Prettier gates passed - independent code review: APPROVE - independent security review: APPROVE ## Boundaries - no lifecycle, roster mutation, lease issuance, certificate workflow/storage, credentials, or v2 provisioning - roster-v2 semantic validation remains an explicit async handoff for later production wiring - issue remains open through M5 Refs #758
jason.woltje added 4 commits 2026-07-14 21:53:30 +00:00
chore(orchestrator): start FCM-M1-002 shared role resolution 462c58a1ac 
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
chore(orchestrator): reassign FCM-M1-002 to fresh worker 32e75c67b0 
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
feat(fleet): add shared role semantics 01202767df 
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
chore(docs): normalize fleet task table
Some checks failed
ci/woodpecker/pr/ci Pipeline failed
Details
67516adef4 
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
jason.woltje force-pushed feat/758-shared-role-resolution from 67516adef4 to 1c41adad1c 2026-07-14 22:16:34 +00:00 Compare
jason.woltje force-pushed feat/758-shared-role-resolution from 1c41adad1c to 4d990eee7c 2026-07-15 00:17:22 +00:00 Compare
jason.woltje added 1 commit 2026-07-15 00:46:32 +00:00
fix(fleet): close persona resolver authority edges
All checks were successful
ci/woodpecker/pr/ci Pipeline was successful
Details
ace73f1e03 
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
jason.woltje merged commit a5e8e55401 into main 2026-07-15 00:53:48 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
fleet-enhancement
Fleet-wide reliability/speed/cost improvements surfaced by the nightly enhance pass
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
jason.woltje
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: mosaicstack/stack#768
Delete Branch "feat/758-shared-role-resolution"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?