Skip to content

feat(configurator): share service guidance and described Assistant catalogue choices - #273

Merged
lweberru merged 20 commits into
mainfrom
fix/assistant-guided-git
Nov 18, 2026
Merged

lweberru merged 20 commits into
mainfrom
fix/assistant-guided-git

Conversation

@lweberru

@lweberru lweberru commented Nov 18, 2026 •

Copy link
Copy Markdown
Collaborator

This integration branch includes #274 so the actual combined release can be qualified before deployment. Merge #274 first with a merge commit, then this PR; after that base update the native Git/State changes remain owned by #274.

The Assistant previously repeated technical free-text questions and could ignore the selected English UI language. Supported service decisions now share catalogue-backed, described choices and a consultation policy that retains answered requirements.

  • Share the native-field-to-catalogue registry between editor, Assistant and coverage inventory. Git, VPN, Kubernetes, Observability, bastion/firewall VM decisions and native role/permission selections use one searchable picker. The inference wire grammar requires an explicit question kind, preventing omitted picker metadata. Business requirements remain business questions, including when they inform a flavor field. Source-network questions share reviewed bilingual text; current and previous Audit question wording both support short continuations.
  • Pass UI language explicitly through API and inference; legacy clients use the latest natural-language user answer. Historical customer messages and resource names remain unchanged. Retain setup intent across service switches rather than returning a field overview when choices are missing.
  • Author picker metadata server-side from scoped project/region catalogues. Public PIM facts require matching product, region and offering; conflicting/deprecated entries and unknown RAM units cannot become capacity claims. Model/presentation budgets disclose truncation. Unavailable and empty catalogues differ; ambiguous regional questions are clarified. Pending catalogue decisions use a grounded renderer; this is not a universal verifier of model prose.
  • Treat documented limits as architecture constraints. Git10/Git100 allow at most 10/100 users per instance. Above 100, discuss separate team/project instances or a narrower initial scope before choosing a flavor. Literal confirmed workload counts survive later incompatible plan selections; explicit scope reductions remain possible. This first numeric-limit policy covers Git without inventing limits for other products. The central devops input configures one instance; there is no automatic federation or distribution. Git flavor and ACL changes still replace the instance with the pinned provider.
  • Preserve firewall consultation-only turns and require complete requested native HA proposals when prerequisites are known. Read-only service consultation uses the typed catalogue/question contract with changes blocked by schema and server validation. Explicit current root Plan review questions receive the reviewed instructions directly; semantic fallbacks remain tested. Lifecycle instructions now follow the selected UI language. A confirmed draft that merely promises changes receives one bounded semantic repair under the same scope/schema guards.
  • Persist presentation metadata for reload, exclude it from proposal acceptance, and preserve tenant, IAM, source, revision, persistence and execution boundaries. A picker answer is not an accepted configuration change.

Maintained design and coverage: English · Deutsch.

Validation on the latest implementation:

  • npm run check: 2,003 passed, 81 conditional skips; generation, lint, typechecks and web build pass.
  • Desktop/mobile guided Git, common catalogue pickers and discard flows: 8 passed; screenshots inspected. The earlier isolated PostgreSQL identity/catalogue suite passed 56 tests; current CI also runs database and reload/tenant checks.
  • Targeted regressions cover capacity and explicit scope reduction, known Firewall HA boundaries, Audit root Plan review, Application Git and S3 coordination. Earlier functional failures prompted source corrections; their receipts remain retained.
  • Complete repeated real-model qualification is 256/256 passed; the subsequent continuous dialogue is 14/14 passed on knowledge hash 92bc9dac3cb4c1ccac2a835f0405d6be330363cec8164e3bb4fe569f706ce232, suite hash ceea8b581f812d39324e5f8479f29e9504e0a05ddcd26e2bffddf902d86659eb. The three changed root-review/VPN cases already pass twice each. All 16 normal CI checks for head ad8dbf385cf747ca4c10985eafdc909cd036d2b8 pass. The combined source is ready for the authorized merge and Dev-first rollout.
  • Previous full qualification completed 251/254 checks successfully and exposed misrouted Audit root-Plan review and one VPN response-schema failure. Their receipts remain retained. Current fixes address those routes; they do not retry away failed repetitions. An earlier HTTP 429 run overlapped an orphaned local test process, which was stopped; the source-bound rerun is isolated.
  • Earlier failed/interrupted receipts are retained, including the capacity-follow-up failure that prompted the independent workload guard. Oracles were not weakened. Older Git-only or PR feat: add Application Git and database coordination for managed State #274 qualification does not qualify this expanded source.

Curated v2.2.0 notes are included. Both PRs were merged after clean checks, followed by successful Dev verification and production promotion using the same immutable build. Normal protected deployment approvals were used.

Closes #272.

Rollout verification

Merged with the user-authorized admin merge and deployed successfully on 2026-11-18:

  • Combined release commit: 343aa89a8bbf7c31c5891b6081628078b6a0eee9.
  • Dev build and deployment: successful, including 256/256 repeated real-model checks, 14/14 continuous-dialogue steps, application/database/browser/native-runner verification and runtime connection tests. The public page and STACKIT-authenticated health endpoint pass.
  • Production release and deployment: successful. v2.2.0 reuses that exact immutable Dev build, with mode=qualified. All three production web/API replicas, public TLS/authentication/tenant boundary, service connections and isolated Runner checks pass. Independent post-deploy page and health checks also pass.
  • Knowledge SHA-256: 92bc9dac3cb4c1ccac2a835f0405d6be330363cec8164e3bb4fe569f706ce232; suite SHA-256: ceea8b581f812d39324e5f8479f29e9504e0a05ddcd26e2bffddf902d86659eb.
  • No model HTTP 400 occurred in the current local or release qualification. The historical intermittent issue fix(assistant): structured-output HTTP 400 and incorrect execution-upgrade routing #225 remains open; these passing receipts do not establish its root cause or guarantee that it cannot recur.

No customer infrastructure Plan/Apply was executed by this rollout.

@lweberru
lweberru marked this pull request as ready for review November 18, 2026 00:35
@lweberru
lweberru marked this pull request as draft November 18, 2026 08:28
@lweberru lweberru changed the title fix(configurator): guide Git setup and respect Assistant UI language feat(configurator): share service guidance and described Assistant catalogue choices Nov 18, 2026
@lweberru
lweberru marked this pull request as ready for review November 18, 2026 15:19
@lweberru
lweberru merged commit 343aa89 into main Nov 18, 2026
16 checks passed
@lweberru
lweberru deleted the fix/assistant-guided-git branch November 18, 2026 15:19
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.

Assistant: respect UI language and guide company-wide Git setup with concrete recommendations

1 participant