Repository navigation
Plan v1.3 rendering engine and document navigation - #24
Merged
Merged
Conversation
Zburgers
marked this pull request as ready for review
October 5, 2026 11:40
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.
Planning only
This PR contains no runtime implementation. It defines the proposed v1.3 rendering-engine architecture and the Shipyard execution plan.
Proposed v1.3 boundary
Explicitly not v1.3
No graph view, backlinks, vault/workspace indexing, global search, transclusion, plugin system, or Agent Context Inspector.
Architecture decision
ADR-0002 proposes keeping the hardened v1.2.5 parser/security stack and introducing a structured
src/rendering/subsystem instead of migrating to unified/remark or MDX/React rendering.Review gates before implementation
Please approve the product boundary, ADR-0002, parent-relative local-image policy, dependency choices, and 19-task Shipyard plan.
After this planning PR is approved/merged, implementation should start on a fresh feature branch from the merged planning commit. This PR does not authorize a v1.3 release or version/tag change.