施工员andmultica-agent
3e8666e3e1
The shared shell hides .app-header .overview-strip (the market tape) for heavenView, which is intentional (the heaven page has its own dark header). But hiding the tape removes the flex-grow element that normally pushes .header-actions to the right edge, so on the heaven page the top-bar icon group was left-shifted by hundreds of pixels (rightGap 792px at 1920 vs 20px on reference pages). Give the heaven .header-actions margin-left:auto in the shared shell so the icon group stays flush right when the tape is gone, matching every other page. The heaven page body, business logic, data, API and frozen content are untouched. Also bump the shell stylesheet cache version. Co-authored-by: multica-agent <github@multica.ai>
Governance Registries
These registries describe the approved product surface of the standalone application.
pages.config.json: primary page identity, navigation group, access expectation, scrolling, and mobile composition policy.features.config.json: feature ownership, backend access class, data scope, and availability.api.config.json: current routes generated from the preservedserver.pyAPI surface, with one feature owner and backend access class per route. Its dispatcher implementation lives inbackend/application.py.architecture-inventory.json: generated inventory of current pages, routes, tables, providers, model entry points, CSS layers, and remaining code hotspots.data-fields.config.json: canonical data products, provider eligibility, intended use, and known blocked datasets.data-quality.config.json: freshness, coverage, units, adjustment, point-in-time, and fail-closed rules for every canonical data product.jobs.config.json: background schedules, dependencies, lock keys, retry policy, timeouts, and output versions.
The registries are governance contracts, not substitutes for runtime authorization. Backend
access in backend/http/routes.py is authoritative; frontend visibility is only a presentation
concern and never grants access.
Regenerate the transitional API inventory after a route change:
python tools/build_api_registry.py
python tools/build_api_registry.py --check
python tools/build_architecture_inventory.py
python tools/build_architecture_inventory.py --check