jester/zlh-grind
1
0
Fork 0
Code Issues 3 Pull Requests Actions Packages Projects Releases Wiki Activity

SESSION_LOG: add decisions on auto-proceed + splitting provisionAgent

Browse Source
This commit is contained in:
jester 2025-12-14 23:57:37 +00:00
parent d5360bc24b
commit 8b381ad601
1 changed files with 4 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
SESSION_LOG.md
View File

@ -65,3 +65,7 @@ Next steps:
- Finalize runtime version field strategy (version vs runtimeVersion) across API + agent + DB payload. - Finalize runtime version field strategy (version vs runtimeVersion) across API + agent + DB payload.
- Complete node install.sh to use local artifacts and validate verify.go; then repeat for python/java/go. - Complete node install.sh to use local artifacts and validate verify.go; then repeat for python/java/go.
- Define addon dispatch + payload schema for addons (cross-cutting) and later store customer addon selections. - Define addon dispatch + payload schema for addons (cross-cutting) and later store customer addon selections.
### Decisions recorded (late-session)
- **Session “auto-proceed” rule (next session):** Proceed without asking when changes are localized/low-risk (internal refactors, helpers, file organization) and do not alter public API contracts, DB schemas, or game provisioning paths. Pause and ask for anything cross-repo, persistent, user-facing, or that could regress game provisioning.
- **zpack-api refactor direction:** Split `provisionAgent` into an orchestration entrypoint plus `provisionGame` and `provisionDev` handlers selected by `ctype`. Keep shared infra (Proxmox calls, VMID/ports allocation, agent HTTP) centralized; only split validation + payload shaping per ctype.