Expose the config schema via GET /api/config #136
Notifications
Due Date
No due date set.
Blocks
Depends on
Reference: sam/archie#136
Reference in new issue
Block a user
Extend handleConfig's response with a schema-driven shape (sections of fields, each carrying its descriptor and current value) built from the field descriptors, replacing the flat ConfigView value tree the frontend currently re-interprets by hand. Keep the existing Locked/Overridden/Reload/Provenance top-level fields -- they describe runtime state, not the field catalog, and the schema-driven fields reference into them (locked_reason, overridden) rather than duplicating that logic.
Close reason
ConfigView gains a Schema []ConfigSection field, populated in handleConfig via buildConfigSchema(view), which attaches each request's Value/LockedReason/Overridden onto the static configFieldDescriptors() catalog. The flat ConfigView fields (Identity, Repositories, etc.) are untouched -- Schema is additive. Tests confirm schema values match the flat fields they derive from, locked reasons propagate, structured fields stay non-editable, and secrets never reach the schema block.
Imported from beads
archie-core-b6ew.2· GitHub #695 · type feature · priority P2 · created 2026-09-02 · closed 2026-09-02