docs: onboarding, Settings screen, TOML config (ADR 0004) #15

deadstyle · 2026-10-01T22:09:10-05:00

deadstyle commented

2026-10-01 22:09:10 -05:00

Summary

Setup moves into the app: a first-run onboarding flow, and a Settings screen (S) that saves to a TOML config. There's no database.

Changes

design.md: new Onboarding section (7 steps: welcome → forge type → address → sign in → connection test → Renovate bot → name and save) and Settings section. S added to the keymap; onboarding and settings added to the v1 scope.
architecture.md: "Configuration and stored state": config.toml (managed by the app), state.toml (remembered values), token rules, atomic writes.
ADR 0004: TOML files with no database; BurntSushi/toml.

Tickets updated: #5 is now "Onboarding, Settings screen and TOML config", and #8 gains demo mode (--demo) for safe UI development and verification.

Needs PM approval before merge

This changes docs/design.md. The requirement (onboarding, editing config in the UI, TOML) came from the PM; the step list and the S key are engineering's proposal.

Decisions

Opus: TOML via BurntSushi/toml; separate state file; pasted tokens allowed only with 0600 permissions (ADR 0004).

## Summary Setup moves into the app: a first-run onboarding flow, and a Settings screen (`S`) that saves to a TOML config. There's no database. ## Changes - **design.md:** new Onboarding section (7 steps: welcome → forge type → address → sign in → connection test → Renovate bot → name and save) and Settings section. `S` added to the keymap; onboarding and settings added to the v1 scope. - **architecture.md:** "Configuration and stored state": `config.toml` (managed by the app), `state.toml` (remembered values), token rules, atomic writes. - **ADR 0004:** TOML files with no database; `BurntSushi/toml`. Tickets updated: #5 is now "Onboarding, Settings screen and TOML config", and #8 gains demo mode (`--demo`) for safe UI development and verification. ## Needs PM approval before merge This changes `docs/design.md`. The requirement (onboarding, editing config in the UI, TOML) came from the PM; the step list and the `S` key are engineering's proposal. ## Decisions - Opus: TOML via `BurntSushi/toml`; separate state file; pasted tokens allowed only with `0600` permissions (ADR 0004).

deadstyle added 1 commit

2026-10-01 22:09:10 -05:00

docs: onboarding, Settings screen, TOML config (ADR 0004)

ci / check (pull_request) Successful in 38s

Details

bc092bfd78

- design.md: first-run onboarding flow, Settings screen (S), v1 scope
- architecture.md: config.toml + state.toml, token handling, atomic writes
- ADR 0004: TOML files managed by the app, no database

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

deadstyle merged commit 8a1f1234d5 into develop

2026-10-01 22:13:28 -05:00

deadstyle deleted branch docs/onboarding-config

2026-10-01 22:13:28 -05:00

deadstyle referenced this pull request from a commit

2026-10-01 22:13:29 -05:00

docs: onboarding, Settings screen, TOML config (ADR 0004) (#15)

Sign in to join this conversation.

No reviewers