- The configured SSH fetch endpoint still refuses connections and the LAN SSH endpoint rejects the available key, but the approved HTTP push URL is operational.
- Forgejo runner labels/jobs remain unverified, so the committed workflow is not claimed successful.
- Real UNC execution still requires a user-authorized disposable fixture.
Turn the P00 Spike skeleton into a durable application foundation. Under the project owner's option A decision, P01 includes basic non-sensitive Profile metadata CRUD while P02 retains all slot and runtime connection behavior.
Add durable companion and operations slot assignment, then build two independent Rust-owned REST/SSE runtimes without weakening the P01 credential and profile boundaries.
### Ordered work
1. Persist the two fixed connection slots and enforce that one Profile cannot occupy both slots.
2. Add bounded slot list/assign/clear IPC and a minimal settings UI for slot selection.
3. Add auto-connect validation: at most two Profiles, one per slot, with no duplicate Profile assignment.
4. Add an operations-switch guard that blocks Profile changes while an operations task is active.
5. Add duplicate `server_instance_id` detection and surface a warning without silently merging Profile identity.
6. Define the production credential enrollment/update/delete lifecycle entirely in Rust, with opaque references in SQLite and no secret values returned to React.
7. Review the provisional Gateway contract before enabling real configured connections; keep real AstrBot compatibility explicitly unclaimed until the server contract is available.
8. Implement independent REST discovery/authentication and SSE runtimes, per-Profile cancellation, replay cursors, de-duplication, retry state, and error state.
9. Integrate the existing dual-instance Mock Gateway and verify that one instance failure or auth expiry does not affect the other.
10. Add frontend/Rust/integration coverage, update protocol and progress documents, run the full stage checks, and push the branch normally without merging `main`.
### Safety gates
- Slot work must not accept or expose Token, password, API Key, Cookie, Authorization header, or NAS credentials.
- A server-supplied `profile_id` is never trusted; the Rust connection object binds every event to its local Profile and slot.
- A changed `server_instance_id` or certificate identity freezes the affected connection instead of silently rebinding it.
- Companion Profiles never gain local-tool authority from slot assignment alone.
- The provisional `/desktop/v1` contract and Mock Gateway are not evidence of compatibility with an unreviewed real AstrBot Gateway.
Implement SQLite schema v3 for the two fixed slot assignments, bounded list/assign/clear commands, database and command tests, and a minimal Profile-slot settings surface. This increment intentionally excludes network activation and credential values.
Implement auto-connect configuration validation, operations switch protection while a runtime operations task is active, and duplicate `server_instance_id` warnings without silent Profile merge. Auto-connect remains configuration-only and does not start REST/SSE. Operations task begin/end stay internal to Rust for this increment.
The next increment starts with the formal Rust-owned credential lifecycle. Real Gateway activation remains blocked until PD-0009 through PD-0012 are resolved.