Skip to content

feat: declared runtime capability manifests (#900, manifests slice) - #911

Merged
0xNyk merged 1 commit into
mainfrom
plan/runtime-capability-manifests
Jul 25, 2026
Merged

feat: declared runtime capability manifests (#900, manifests slice)#911
0xNyk merged 1 commit into
mainfrom
plan/runtime-capability-manifests

Conversation

@0xNyk

@0xNyk 0xNyk commented Jul 25, 2026

Copy link
Copy Markdown
Member

First slice of #900 per the implementation contract in the issue thread: capability manifests, read-only, no behavior change. Aegis receipts enforcement (phase 2) deliberately waits for its own acceptance contract.

Refs #900 (slice 1 of 2 — leave open for the Aegis receipts phase). Verified: 5 new tests, full suite 1544/1544, typecheck, lint, leak-scan clean.

Every runtime adapter now declares its integration depth honestly through a
static RuntimeCapabilities manifest colocated with RUNTIME_META: dispatch,
session resume, PTY, cwd control, tool policy, budget caps, structured
output, skills inventory, and evidence receipts. Declared per adapter code
version, never probed from the host — detection answers 'is it here',
manifests answer 'what can Mission Control honestly do through it'.

- GET /api/agent-runtimes composes capabilities onto each detection result
- runtimes settings section renders the matrix as compact chips; dim means
  'this adapter cannot supply that control', making missing depth visible
  instead of implied
- claude's first manifest reflects shipped truth: #602 session resume,
  #720 tool policy / budget / cwd, JSON output, dispatch telemetry
- hermes skills_inventory stays false pending NousResearch/hermes-agent#71274;
  flipping it is the feature-detect story for #777's provider
- tests pin completeness and honesty: no adapter may claim receipts nothing
  produces, read-only scanners never claim dispatch depth

Aegis receipts enforcement (phase 2 of #900) deliberately untouched pending
its own acceptance contract. Verified: 1544/1544 unit tests, typecheck, lint.
@github-actions github-actions Bot added the screenshot-drift UI changed — README screenshots may need updating label Jul 25, 2026
@github-actions

Copy link
Copy Markdown

📸 Screenshot Drift Check

This PR modifies UI source files. Please verify whether the README screenshots need refreshing:

  • Any updated screenshot was captured from a disposable demo database
  • Every visible name, value, identifier, path, and notification is synthetic
  • Browser chrome and embedded image metadata contain no account or device data
Changed UI files
src/app/api/agent-runtimes/route.ts
src/components/settings/agent-runtimes-section.tsx

See docs/SCREENSHOT-GUIDE.md for instructions on capturing and optimising screenshots.

This comment is posted automatically and can be dismissed if no visual changes occurred.

@0xNyk
0xNyk merged commit 1718628 into main Jul 25, 2026
6 checks passed
@0xNyk
0xNyk deleted the plan/runtime-capability-manifests branch July 25, 2026 09:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

screenshot-drift UI changed — README screenshots may need updating

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant