Skip to content

Verify Full System activation before reporting sudo access - #3

Merged
kmanisk merged 9 commits into
mainfrom
fix/full-system-activation-verification
Nov 14, 2026
Merged

kmanisk merged 9 commits into
mainfrom
fix/full-system-activation-verification

Conversation

@kmanisk

@kmanisk kmanisk commented Nov 14, 2026

Copy link
Copy Markdown
Owner

Scope

  • Require the protected host-controller activation marker to match the freshly signed Full System lease, reverting to STANDARD if verification fails.
  • Have the CLI check local signed lease/controller state after the operator returns before treating bridge-dev mode sudo as successful.
  • Avoid asserting gateway acknowledgment based solely on the operator; document the separate MCP agent_status acceptance check and stale launcher diagnosis.
  • Extend operator fixture coverage for truthful status reporting.

Safety

GitHub source-only change. No live sudo activation, deployment, host service restart, or policy relaxation. Existing managed production remains on 8479250.

Validation

Run CI for test:cli, test:policy, test:portable and tool count manifest. Real host-root/MCP acknowledgment still requires separate independent operator acceptance.

@kmanisk
kmanisk marked this pull request as ready for review November 14, 2026 12:32
@kmanisk
kmanisk merged commit 70f6b63 into main Nov 14, 2026
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant