AstrBot-Desktop/docs/decisions/pending-decisions.md
YokiiroBW 6a1eeabea8
一些检测仍在等待运行
ci / Portable quality checks (push) Waiting to run
ci / Windows Tauri build (push) Waiting to run
docs(p01): record foundation progress and profile boundary
2026-07-18 22:21:04 +08:00

4.5 KiB

Pending Decisions

PD-0001: Forgejo transport for the development machine

  • Status: resolved for HTTP push; SSH remains unavailable
  • Current value: ssh://git@localhost:18086/YokiiroBW/AstrBot-Desktop.git
  • Push URL: http://192.168.31.210:18085/YokiiroBW/AstrBot-Desktop.git
  • Observation: the authenticated Forgejo API confirmed YokiiroBW/AstrBot-Desktop existed, was empty, used main, and granted push permission before initialization.
  • SSH observation: localhost:18086 refuses connections. 192.168.31.210:18086 answers but rejects the available SSH key.
  • Push observation: Git Credential Manager was cleared and reauthenticated without placing a secret in the repository or chat. The approved non-forced HTTP push succeeded and remote main now points to 0d12b94.
  • Decision: retain the SSH URL as the fetch URL for future key repair and use the explicitly approved HTTP URL as the push URL for this workflow.
  • Safety impact: no force push or history overwrite occurred; feat/p00-bootstrap was created from the pushed baseline.

PD-0002: P00 branch naming

  • Status: resolved for this predevelopment workflow
  • Decision: use feat/p00-bootstrap as explicitly required by the workflow and current user request.
  • Follow-up: subsequent stages use the branch names in AGENTS.md.

PD-0003: Node.js release line

  • Status: monitor during bootstrap
  • Current environment: Node.js 24.
  • Decision: use the installed version initially; pin package-manager and dependency versions in the repository and record any Tauri/Vite incompatibility found by actual builds.

PD-0004: P00 source layout

  • Status: resolved for P00
  • Observation: the architecture document illustrates an apps/desktop monorepo, while the predevelopment workflow recommends root-level src and src-tauri directories.
  • Decision: keep the single desktop application at the repository root during P00 and use Cargo workspace crates for protocol and Mock Gateway isolation.
  • Reason: there is only one application, and the workflow explicitly recommends the root layout; this avoids an extra package layer without preventing a later move if a second application appears.

PD-0005: Source cleanup in the NAS Spike

  • Status: resolved for P00
  • Conflict: the implementation task mentions cleanup after verification, while the workflow and safety rules require source preservation and prohibit irreversible tests.
  • Decision: P00 always preserves source files and tests cleanup policy only as a non-executed plan field.
  • Follow-up: reversible recycle-bin behavior requires a later explicitly authorized Spike.

PD-0006: Provisional desktop gateway contract

  • Status: resolved for P00
  • Decision: define a provisional desktop-v1alpha1 contract and Mock Gateway without claiming compatibility with an unavailable real AstrBot Gateway.
  • Follow-up: authentication fields, error codes, event retention, ACK timing, and capability names require a later real-gateway contract review.

PD-0007: Repository-local Git author identity

  • Status: resolved
  • Decision: the user explicitly approved YokiiroBW <yokiirobw@gmail.com>.
  • Implementation: the identity is configured only in this repository.
  • Result: two Conventional Commit baseline commits were created on main, pushed normally, and followed by scoped feature-branch commits.
  • Safety impact: no global Git identity was changed.

PD-0008: Profile CRUD stage ownership

  • Status: unresolved; blocks Profile CRUD implementation only
  • Conflict: docs/01_Architecture_Design.md lists Profile CRUD in stage 1, while docs/02_Codex_Implementation_Tasks.md lists ConnectionProfile CRUD in Batch 2.
  • Impact: resolving this changes the database schema, Tauri IPC surface, frontend state model, and the acceptance boundary between feat/p01-foundation and feat/p02-dual-connections.
  • Safe current action: complete only the unambiguous P01 foundation work<72><6B>persistent migrations, validated bootstrap IPC, redacted logging, tray, single-instance, exit flow, and tests.
  • Paused work: profile tables, Profile CRUD commands, profile forms, and profile-to-slot assignment.
  • Required decision:
    • Option A: architecture document wins; implement basic Profile CRUD in P01 and leave slot assignment/connection behavior for P02.
    • Option B: implementation task batching wins; keep all ConnectionProfile CRUD in P02.
  • Recommendation: Option A is the literal higher-priority document, but the implementation remains paused because AGENTS.md requires explicit reporting for conflicts affecting database structure or public interfaces.