v1 readiness: CHANGELOG + threat model + first-run onboarding polish #26
Reference in New Issue
Block a user
Delete Branch "v1-readiness"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Closes the last three v1 blockers from the cross-cutting backlog so the project is ready to tag.
CHANGELOG.md(new) — Keep-a-Changelog format with a v1.0.0 entry summarising what each phase delivered, plus an empty Unreleased section.docs/threat-model.md(new) — structured walkthrough of assets, actors, attack surfaces (bootstrap, local accounts, OIDC, agent enrolment, agent ↔ server WS, credential lifecycle, restore, audit log, self-update), residual risks, and explicit out-of-scope items. Reviewed against the v1.0.0 surface.cmd/server/main.gonow prints a clickable$RM_BASE_URL/bootstrapURL at first-run startup (with a fallback hint whenRM_BASE_URLis unset), alongside the existing one-shot token for headless/api/bootstrapuse.web/templates/pages/bootstrap.htmlshows an explicit "Minimum 12 characters" hint under the password field so the rule is visible before submission./bootstrapUI already auto-applies the in-memory token (operator never has to type it), and/loginalready redirects to/bootstrapwhen no users exist. The actual gaps were just discoverability of the URL and visibility of the password rule, both addressed here.tasks.mdupdated to close X-01, X-04, X-05 with notes.Test plan
go vet ./...clean (passed locally + via pre-commit)/bootstrapURL