2.4 KiB
2.4 KiB
P00 Bootstrap Implementation Plan
Objective
Establish a reproducible Tauri 2 + React + TypeScript + Rust baseline and complete the high-risk technical Spikes required before formal feature development.
Ordered work
- Normalize repository documents and Git metadata on
main. - Verify Forgejo is empty before the first
mainpush; never overwrite remote history. - Create
feat/p00-bootstrapfrom the pushedmainbaseline. - Establish the Tauri 2 application and typed frontend-to-Rust IPC.
- Implement two independent REST/SSE clients and a dual-instance Mock Gateway.
- Verify Windows secure credential CRUD without exposing secret values to React or logs.
- Verify bounded Windows diagnostics: foreground window, UI Automation, selected-window capture, process information, event logs, ports, network targets, authorized log tails, configuration parsing, and redaction.
- Verify NAS transactions only in a dedicated generated fixture directory: dry run, temporary copy, size/hash verification, atomic commit, conflict handling, interruption recovery, and source preservation.
- Define protocol schemas and capability negotiation types.
- Add frontend, Rust, integration, and Forgejo CI checks.
- Run and record all checks, commit by independently verifiable increments, and push the feature branch without merging
main.
Safety gates
- No arbitrary command execution is exposed by product code.
- No real credential is used in fixtures, logs, snapshots, or commits.
- No NAS Spike touches an existing user file or directory.
- No remote branch is changed until
git ls-remotesucceeds and remote history is reviewed. - No test or build is marked successful without captured execution results.
Current handoff status
- Rust/MSVC/Tauri are verified and no longer block local work.
- Git Credential Manager reauthentication succeeded and the non-forced HTTP push created the remote
mainbaseline at0d12b94. - Development is active on
feat/p00-bootstrap; the remaining repository handoff step is a normal push of this feature branch. - 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.