Repository navigation
Conversation
Signed-off-by: EiffL <fr.eiffel@gmail.com>
EiffL
marked this pull request as draft
August 28, 2026 19:27
Member
Author
|
The parity implementation is complete and validated locally, but I am keeping this PR draft until the shared preview API is published. Dependency stack:
Current local verification is green: 33 theme tests, all workspace typechecks, article/book production builds, and a live DESI browser audit. The live article has 57 rich references, 5 output provenance drawers, 28/28 caption equations rendered as KaTeX, upstream |
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
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
astra-publication-bundle.v1carrier as the exact@astra-spec/sdkresolved bundle, then derive canonical record/analysis indexes with the SDK@astra-spec/uibuttons and record dialogs, scoped with the published@lightcone-research/brandadapteroutputPathandcacheToken, with bounded table/metric loading and safe figure policiesThis is the clean successor to #8. It keeps that PR's shared-UI direction while using the now-published SDK/UI/brand packages and deliberately avoids its page-chrome and broad renderer forks.
Companion producer change: LightconeResearch/MySTRA#25.
Publication boundary
The overlay accepts only this carrier version:
Carrier data is validated before indexing. Unsupported or malformed documents degrade to the neutral MyST output rather than breaking the page. Static resources are consumed only from the dedicated sibling carrier, require matching SDK cache tokens, and reject active/protocol-relative URL schemes.
Artifact previews are intentionally bounded:
Upstream maintenance
The copied MyST applications remain nearly untouched. The ASTRA-specific app-shell diff is limited to four files:
Article.tsx/ArticlePage.tsx: mount the DOM-transparent publication provider around rendered article surfacesroot.tsx: retain the overlay stylesheet seam and remove external font links now bundled by the brand packageThere are no local header, navigation, route, or upstream content-component forks. The renderer map overrides only canonical ASTRA inline spans; every block stays on the upstream renderer. Contract parsing, dialogs, artifacts, and styles live under
packages/astra, so futuremyst-themeupdates can be applied first and the small seams reapplied afterwards.Breaking alpha cleanup
No legacy compatibility layer is retained:
@astra-spec/store-typesand the old serialized-store/provider modelVerification
npm cinpm test— 21 testsnpm run typecheck— overlay, article, and book workspacesnpm run build— production article and book buildsgit diff --checkBuild note
The legacy Remix 1 compiler prints a non-fatal resolver warning for
@astra-spec/sdkbecause SDK 0.1.1 exposes an import-only conditional export while the server build targets CommonJS. Both production builds complete, and their metafiles contain the SDK implementation with no external SDK import. Adding a default export condition in a future SDK patch will remove the diagnostic without a theme change.