Skip to content

fix(configurator): keep a single template drafts editor - #171

Merged
lweberru merged 2 commits into
mainfrom
fix/single-template-drafts-entry
Oct 27, 2026
Merged

lweberru merged 2 commits into
mainfrom
fix/single-template-drafts-entry

Conversation

@lweberru

@lweberru lweberru commented Oct 27, 2026 •

Copy link
Copy Markdown
Collaborator

Template drafts appeared both in configuration step 5 and under Application Landing Zones. Platform drafts now have one template editor under Application Landing Zones, with the existing Assistant, structure preview and network associations. Configuration navigation runs directly from Platform to Operations; a contextual link opens the shared template draft. Existing combined configurations retain their concrete-project editor.

Old platform draft project-step links redirect with history replacement, preserving unsaved configuration/template edits and browser Back/Forward. Draft storage, saved configuration IDs, publication snapshots, authorization and State are unchanged. Local guest template editing remains available without authenticated publication/ordering. The same scoped technical catalogue remains accessible while editing templates; Application Owners gain no platform access.

Validation: full npm run check passed (1,258 tests, 76 existing gated skips), independent review completed without open findings. The complete desktop/mobile browser suite passed against the final build (380/380); navigation helpers and explicit GET-only empty catalogue fixtures follow the new sole entry point while retaining existing selection, save, authorization and network checks. English/German user and developer documentation updated. No cloud Plan, Apply or State mutation.

@lweberru

Copy link
Copy Markdown
Collaborator Author

Independent review completed on the final scope (6ea07ba plus 34be826), with no open findings. Checked the role/session/workspace boundaries, guest-local editing without private catalogue reads, unchanged saved configuration binding and root draft, legacy concrete-project preservation, history replacement for old template routes, shared template selection across editor/structure/network previews, explicit save/publication boundaries, and persistence of the same catalogue panel while its visibility follows the selected Application tab. Existing assertions remain exact; new list fixtures allow only GET requests.

Local verification: npm run check passed (1,258 tests; 76 existing gated skips); final source builds/typechecks; all 380 desktop/mobile browser tests passed. The previous whole-suite run exposed eight ambiguous status locators caused by showing the catalogue panel on non-editing tabs. The source fix limits visibility to the drafts tab; no assertion was weakened or test skipped. No customer Plan/Apply, State write or lock change was performed.

@lweberru
lweberru merged commit 3f0cbe1 into main Oct 27, 2026
14 checks passed
@lweberru
lweberru deleted the fix/single-template-drafts-entry branch October 27, 2026 09:47
@lweberru

Copy link
Copy Markdown
Collaborator Author

Dev acceptance for PR #171: Configurator Release #40483441681 completed successfully from exact merge source 3f0cbe13297ee8e9a3013f7ad73a5b958fa5f90c. Mode: dev-skip-assistant-qualification, runner_pool_size=1, build_only=false; the runtime Assistant remains enabled. All applicable PR checks, independent review and source-bound release gates passed. The release's full browser suite passed 380/380; unit checks passed 1,258 with 76 existing gated skips.

The running Dev UI was verified separately with a fresh guest browser: six platform configuration steps, no duplicate template step, exactly one template editor under Applications, and unsaved template edits preserved across view changes. All API mutations were blocked during this browser check; none were attempted. Authenticated Platform Owner editing/save/Assistant and Application Owner isolation were covered by the complete browser suite.

The independent runtime verification confirmed the active App/droplet/buildpack source, matching Runner source and one live ready pool slot, enabled Assistant, protected endpoints, installed guards and preserved successful recovery evidence. The temporary route-free read-only diagnostic App was removed. A separate read-only double-read confirmed the original recovered test State is unchanged (serial 7, 12 resources, identities retained, lock free). No customer Plan, Apply, State write or lock change was performed.

Build: 10m29s; Dev deployment: 17m41s. Template storage, publication snapshots, order/State identities and legacy concrete-project management are preserved. Only the template editor entry point moved out of the configuration steps.

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