Skip to content

fix(wcore): preserve workspace receipts and inherited approvals - #1329

Closed
FerroxLabs wants to merge 1 commit into
mainfrom
fix/workspace-policy-1188
Closed

FerroxLabs wants to merge 1 commit into
mainfrom
fix/workspace-policy-1188

Conversation

@FerroxLabs

Copy link
Copy Markdown
Owner

Core workspace-policy receipts currently disappear at the manager’s empty-message guard, leaving the chat without filesystem-access evidence. This change preserves accepted receipts and exposes live readable/writable roots and executable capabilities beside the permission selector; dead or disposing sessions report unknown access. Raw stream payloads only trigger a fresh main-process read.

The Tools pane now preserves an absent allow-list as inherited instead of writing a hardcoded default list when a setting changes. Inherited per-tool states remain unknown, and independent registration gates remain editable. Existing explicit custom lists still round-trip.

Related to #1188. This is an intermediate repair: producer-backed tool inventory, mode effects and inheritance-preserving per-tool overrides remain tracked in #1328. The workspace receipt describes filesystem access and does not prove a tool’s registration or approval state. No issue closure is requested.

Validation: full Linux bun run test passed 21,470 Vitest tests (53 skipped) and 285 Bun-native tests; typecheck passed against the exact committed tree. Focused macOS receipt/settings/access tests passed 142 cases, plus all 24 voice integration cases. Both receipt-drop and default-materialization regression tests failed before the fixes. Repository lint has the existing 3,017 warnings and zero errors; i18n and the complete local prek checks passed. The initial full run exposed a missing mock for the new access control in the voice harness; its evidence was retained and the corrected full run passed with no source drift. Native packaged user-flow acceptance remains pending.

@github-actions github-actions Bot added area:desktop-ui Desktop UI area:core Wayland Core engine / backends labels Sep 5, 2026
@FerroxLabs

Copy link
Copy Markdown
Owner Author

Closing as obsolete: this targets Wayland Core / Nano code that was removed in the 0.13.0 cutover. As of 0.13.1 Fuigo is the only engine, so these files no longer exist on main and the change cannot be rebased.

If the underlying behaviour still matters under Fuigo, it is worth a fresh issue against the current code rather than reviving this branch.

@FerroxLabs FerroxLabs closed this Sep 18, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:core Wayland Core engine / backends area:desktop-ui Desktop UI

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants