Skip to content

Installer: backfill next step, nested-install guard: 0.7.2 - #7

Merged
emafriedrich merged 1 commit into
mainfrom
installer-next-steps
Sep 29, 2026
Merged

emafriedrich merged 1 commit into
mainfrom
installer-next-steps

Conversation

@emafriedrich

@emafriedrich emafriedrich commented Sep 29, 2026 •

Copy link
Copy Markdown
Owner

Two field fixes from the field adoption, where the installer was run from apps/api instead of the repository root.

  • Next steps suggest backfill. On an existing codebase the first move is knowledge backfill <domain> plus asking the coding agent to run it; seeding one decision stays as the greenfield path.
  • Nested-install guard. Inside a git repository, the installer walks up to the top level and refuses to run below a directory that already runs KDE, naming the directory to run from. Before this it silently created a second, empty catalog nothing reads.
  • Empty-catalog hint. A lifecycle command run where the catalog has no domains says the directory may be the wrong one, instead of only suggesting domain add (which, in the field, populated the stray catalog).

Tests: 65 pass. Validator ok.

…irectory of a repository that already runs KDE; empty-catalog errors say the directory may be wrong; 0.7.2

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@emafriedrich
emafriedrich merged commit eff61c5 into main Sep 29, 2026
@emafriedrich
emafriedrich deleted the installer-next-steps branch September 29, 2026 22:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant