Skip to content

refactor: derive installer Harness rules from adapter declarations - #291

Merged
SaladDay merged 1 commit into
mainfrom
refactor/installer-harness-catalog
Sep 30, 2026
Merged

SaladDay merged 1 commit into
mainfrom
refactor/installer-harness-catalog

Conversation

@SaladDay

@SaladDay SaladDay commented Sep 30, 2026 •

Copy link
Copy Markdown
Collaborator

Installer acceptance inferred provider protocols and required limits from Harness names while process-schema membership repeated the built-in catalog. The catalog generator now exports adapter-authored Go declarations to Python and checks installer enums/default membership. The existing three-combination acceptance campaign stays explicitly selected and validated against that generated support.

A fresh independent review found no blocking issues. Catalog freshness/generator tests, six acceptance tests, configuration/manifest tests, affected Go tests/build/vet and name guard passed. Catalog and acceptance checks passed after rebasing onto current main. No live-model calls, database access or full make check were performed.


View with [code]smith Autofix with [code]smith
Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.

@SaladDay
SaladDay merged commit e55850b into main Sep 30, 2026
@SaladDay
SaladDay deleted the refactor/installer-harness-catalog branch October 7, 2026 06:38
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