give every ward config that blocks first time setup an interactive onboarding flow step #1059

Closed
opened 2026-07-10 17:39:22 +00:00 by coilysiren · 1 comment
Owner

The problem

For example, the interactive step where a user marks which repos are trusted.

This requires something that was previously optional: the ability to point at a local config file. The brew install or setup path probably should auto-generate a minimal config file with placeholder sentinels and place it under ~/.ward.

The goal is to make onboarding one-shot without ever having to read a line of KDL or write one manually.

Proposed change

Split the setup blockers into narrow issues rather than trying to one-shot every config.

Split children

  • ward#1338 generates a minimal local ~/.ward config.
  • ward#1339 fails loudly when required setup config sentinels remain.
  • ward#1340 supports local ward config file refs for setup-generated config.
  • ward#1341 adds trusted owner/repo onboarding as its own setup step.

Alternatives considered

No response

Before filing

  • I searched existing issues and this is not a duplicate.
  • This stays within ward's scope (the dev-verb gate / agent driver), not a personal-infra or downstream-repo verb.

Decision for release inclusion

Removed from warded control plane coherence as a broad parent. Kai confirmed this needs fine-grained work because trying to cover every setup-blocking config in one issue will likely get the flow wrong. The release should carry narrow child deliverables instead.

### The problem For example, the interactive step where a user marks which repos are trusted. This requires something that was previously optional: the ability to point at a local config file. The brew install or setup path probably should auto-generate a minimal config file with placeholder sentinels and place it under `~/.ward`. The goal is to make onboarding one-shot without ever having to read a line of KDL or write one manually. ### Proposed change Split the setup blockers into narrow issues rather than trying to one-shot every config. ### Split children - ward#1338 generates a minimal local `~/.ward` config. - ward#1339 fails loudly when required setup config sentinels remain. - ward#1340 supports local ward config file refs for setup-generated config. - ward#1341 adds trusted owner/repo onboarding as its own setup step. ### Alternatives considered _No response_ ### Before filing - [x] I searched existing issues and this is not a duplicate. - [x] This stays within ward's scope (the dev-verb gate / agent driver), not a personal-infra or downstream-repo verb. --- ## Decision for release inclusion Removed from `warded control plane coherence` as a broad parent. Kai confirmed this needs fine-grained work because trying to cover every setup-blocking config in one issue will likely get the flow wrong. The release should carry narrow child deliverables instead.
Member

Closing as absorbed by #1624. Ward v1 will document exact supported configuration and first-run behavior rather than build a broad interactive configuration generator.

Closing as absorbed by #1624. Ward v1 will document exact supported configuration and first-run behavior rather than build a broad interactive configuration generator.
Sign in to join this conversation.
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
coilyco-flight-deck/ward#1059
No description provided.