Layout Manager: fe_mode, mount routes, facade CDN 1.0.25#49
Merged
Conversation
New `fe_mode` requirement (default: `compat`) picks which Web Host entry file the facade loads: - `compat` — module.js, full Wippy chrome (unchanged behavior) - `managed` — managed-layout.js, declarative multi-panel host driven by hostConfig.layout (HostLayoutDeclaration) Both entries expose the same `window.initWippyApp(config)` symbol, so index.html does not branch on mode beyond the module file path. Unknown values of fe_mode normalize to `compat`. Requires Web Host >= 1.0.24.
Skipped 1.0.24 — last reference here was 1.0.23. Updates the fe_facade_url default in _index.yaml plus the Makefile WEB_HOST_CDN, README example, and config_handler_test fixture. Re-ran `make sync` against the new URL — loading.js content is unchanged across 1.0.23 → 1.0.25 (the loading component didn't move this window), so no vendored-file delta to commit. Verified: wippy lint clean for src/facade and src/facade/test (0 issues, 2 entries each). Test runner blocked by a pre-existing Windows-symlink issue (src/facade/test/public stored as text "../public" because Git on Windows uses core.symlinks=false). Unrelated to this bump.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Brings the full layout-manager release track into master. This PR is the framework-side counterpart to the
gen-2-chat1.0.25 web-host release and theapp-templateconsumer PR. Six commits, all on the facade + views modules.Headline changes
fe_moderequirement (compat / managed) — picks which Web Host entry the facade loads.compat(default) →module.js, full Wippy chrome (unchanged behavior).managed→managed-layout.js, declarative multi-panel host driven byhostConfig.layout.window.initWippyApp(config). Unknown values normalize tocompat.c359259. Requires Web Host >= 1.0.24.c93c280) — pages can claim top-level URL prefixes; the host honorsapiRoutesoverrides at the config root. The views module gains a page registry and updated render path._index.yaml,Makefile, README, and the test fixture. Skipped 1.0.24 (no consumer ever picked it up).customVariabledtypo fix in views render (was emitted with a stray `d`; renamed everywhere — wire format + TS interface + dev overlay + types). Any external consumer reading the old key now sees the corrected spelling — match this rename downstream.loading.jsrefresh (a3bd18d) — pulled fresh from the CDN with source map.Commits in this PR
Verification
Cross-repo coordination
feature/layout-manager) titledDraft: needs wippy facade publishthat depends on this PR landing + a facade module republish before it can be marked ready.Test plan
🤖 Generated with Claude Code