docs(planning): defer Zensical cutover with beta/1.0 revisit trigger#36
Merged
Conversation
Record the Zensical evaluation as a deferred item so the "wait for beta/1.0" decision and its concrete re-check list (page.is_homepage exposure, validation parity for strict docs repos, classic-variant fidelity) survive on main. The 0.0.46 feasibility spike was validated on 2026-07-05 but not kept as a branch; redo the port from mkdocs.yml when revisiting. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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
1 participant
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.
What
Records the Zensical evaluation as a
planning/deferred.mditem so the "wait for beta/1.0" decision and its concrete re-check list survive onmain, independent of any spike branch.Why
We revisited the old
spike/zensicalreference. Findings:0.0.46(2026-06-21, latest release); no beta/1.0.zensical.tomlmirror ofmkdocs.yml+ a one-blockoverrides/main.htmltweak (dedupe the homepage<title>by title text, since Zensical alpha leavespage.is_homepageundefined) builds cleanly under bothuvx zensical@0.0.46 buildandmkdocs build --strict, with identical title/og:titleoutput.page.is_homepage(+ siblings) not exposed to custom templates.validationparity for strict docs repos (e.g.faststream-outbox):omitted_files/orphaned-page detection andabsolute_linkshave no documented Zensical equivalent; several Zensical validation keys are still deprecated.--strict,invalid_links,invalid_link_anchorsdo map.classicvariant fidelity after the theme rewrite stabilizes.The feasibility spike branch was not kept;
mkdocsremains the live builder.Verification
just check-planning— OK