3.4 KiB
3.4 KiB
Implementation Plan
P00 Bootstrap (completed)
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. - Forgejo PR #1 merged P00 into
mainatb3420e4; development now continues onfeat/p01-foundation. - 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.
P01 Foundation (active)
Objective
Turn the P00 Spike skeleton into a durable application foundation without pulling Batch 2 connection-profile behavior forward across an unresolved document boundary.
Ordered work
- Initialize a persistent SQLite database in the Tauri application-data directory.
- Apply versioned, transactional, idempotent migrations and refuse unknown future schema versions.
- Validate Rust-to-TypeScript bootstrap payloads at runtime.
- Ensure tracing output passes through the shared redaction rules before it reaches a writer.
- Re-verify tray, single-instance, explicit exit, frontend, Rust, E2E, development startup, and production build behavior.
- Record the Profile CRUD stage conflict before changing its schema or IPC.
Paused boundary
docs/01_Architecture_Design.mdplaces Profile CRUD in stage 1.docs/02_Codex_Implementation_Tasks.mdplaces ConnectionProfile CRUD in Batch 2.- Because this changes database structure and public IPC, Profile CRUD remains paused under PD-0008 until the stage boundary is explicitly resolved.