Repository navigation
fix: preserve authored library content before roadmaps - #151
Merged
Alexandre-T merged 4 commits intoOct 29, 2026
Conversation
13 tasks
Alexandre-T
commented
Oct 29, 2026
Alexandre-T
left a comment
Contributor
Author
There was a problem hiding this comment.
READY FOR MERGE
Targeted independent re-review of 4a60162 confirms that the previously reported inconsistencies are resolved:
- The WKB landing page correctly describes Well-Known Binary (WKB).
- Both WKB and WKT landing pages state security support until 31 December 2027, matching their 3.x JSON configurations and generated support tables.
- A fresh
npm run build:localsucceeded, including publication verification (0 errors, 0 warnings). Assertions against all four rebuilt HTML/Markdown pages confirmed the corrected terminology, matching dates, absence of the superseded 2028 prose, and authored content before the generated timeline. - Markdown lint passed for 103 source files;
git diff --checkpassed. - Current PR checks all pass: documentation-check, apache-negotiation, markdownlint and GitGuardian Security Checks.
The prior review verified the Story #149 implementation and independently ran 97 focused tests successfully. This latest commit only corrects the two landing pages. Reviewing the existing PR scope as requested, no blocking finding or unresolved decision remains. Applicable pre-merge Definition of Done requirements are satisfied. Merge and post-merge completion remain subject to Alexandre's decision.
Alexandre-T
deleted the
149-story-preserve-authored-library-landing-page-content-before-generated-roadmaps
branch
October 29, 2026 07:43
This branch was successfully deployed
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.
Pull Request
Summary
Library landing pages now retain their full authored body before generated roadmap content in HTML and portable Markdown. Regeneration refreshes only build-owned nodes without duplicating either part.
Related issue
Closes #149
Changes
Standards and references
No normative spatial behavior or architecture/API boundary is affected. The existing portable Markdown publication contract remains applicable.
Source and generated content
Validation
Additional validation:
npm test: 451 passed, 1 optional Apache integration test skipped.npm run build:local: passed; this invokesnpm run buildwith the repository's fictional local legal configuration. Direct production build correctly refuses missingLEGAL_PUBLISHER_NAME.PATH="$PWD/node_modules/.bin:$PATH" sh .githooks/pre-commit: 103 files, no issues.git diff --check: passed.composer test-localandcomposer quality: not applicable; this Node.js repository has no Composer configuration.Documentation impact
Maintainer instructions now describe preservation and generated-content placement. Existing library landing page bodies become visible before their roadmap, fallback message and documentation-version links. No URLs or version landing page behavior change. Generated resources remain build outputs and source pages are never rewritten.
Checklist