Configurator MVP: operational acceptance and feature-branch merge readiness #95

Current Status (2026-10-04)

Readiness, runtime limits and current MVP issue status are documented. A green local build does not establish product acceptance or approve merge/release. Current extensions are in an uncommitted worktree; there was no automatic commit, release, customer Apply or merge.

• Maintain a current capability/acceptance checklist linked to implementation issues and clearly distinguish implementation, mocked/native and real customer evidence.
• Freeze the final revision and verify CI build/unit/browser/PostgreSQL isolation, native OpenTofu contracts and source-catalogue consistency for that revision.
• Accept two users/two organisations, revocation, interrupted runner and recovery paths; retain untested live paths explicitly.
• Verify PostgreSQL/Secrets Manager/artifact backup/restore, credential rotation and secret-safe operator diagnostics.
• Review capacity, job cleanup, migration rollback/forward recovery and release rollback compatibility.
• Verify CODEOWNERS, main branch protection and CI/CD transition. Automatic app release currently targets feature/landing-zone-configurator; manual main dispatch exists. Decide deployment policy explicitly before changing triggers.
• Prepare a reviewable PR/diff against current main, secret scan and appropriate clean status excluding unrelated private/local files.
• Obtain the user's separate merge decision; no automatic merge or customer Apply.

Evidence and Next Step

landing-zone-configurator/docs/mvp-readiness.md contains the current #89-#95 matrix; runtime details are in docs/runtime-validation-report.md. Current baseline: 310 unit tests and 148 mocked desktop/mobile browser cases passed, with TypeScript/lint/build. The new #89 guard additionally passed 23 real isolated PostgreSQL Plan/Apply/state tests and TypeScript/build. These are local revision evidence, not final CI or live acceptance.

The UI has separated configuration/preparation/Plan/Apply/read-only history and German/English browser preference with persistent explicit header selection. Navigation/language changes do not start execution. The running API and native runner artifact remain unchanged.

Local repository access also reported a corrupt Git index during diff verification. No automatic index reset/repair was attempted and no user changes were reverted. Resolve this before final Git/PR validation; it does not invalidate the independently executed code tests.

Next: continue remaining #89-#94 criteria in bounded slices, then collect the final-revision operational/CI/PR evidence. GitHub/STACKIT IdP registration and private-network/provider limits remain explicit. Drift automation is optional and follows stable Apply; required chat is not deferred.

Dependencies

Product acceptance requires #89, #90, #91, #92, #93 and #94. Native application contracts run in release CI through npm run test:plan; mandatory PR/main wiring and merge approval remain open.