Sub-issue of #321 (lore-overlay, ADR-093). Depends on #322 (extraction).
Corpus: Initiative 2 (provisioning half) of rac/roadmaps/lore-overlay.md; deployment model ratified in ADR-100.
Scope:
- The adoption barrier for the target audience is setup, not capture UX: a non-technical author will not configure a model gateway or a GitHub App. An administrator does it once — gateway endpoint/key/model, GitHub App identity, target repository — composing with the ADR-088 profile-scaffold pattern; the author-facing surface is only hotkey → interview → "is this what you decided?".
- Provisioning documentation is a first-class deliverable (ADR-100 consequence): the one-time setup must be completable from the docs alone.
- Success bar: an admin completes provisioning from the documentation without support, after which an author never sees a configuration surface.
Tick on #321 when a documented provisioning run succeeds end to end.
Sub-issue of #321 (
lore-overlay, ADR-093). Depends on #322 (extraction).Corpus: Initiative 2 (provisioning half) of
rac/roadmaps/lore-overlay.md; deployment model ratified in ADR-100.Scope:
Tick on #321 when a documented provisioning run succeeds end to end.