fix: regenerate spec.html each build; remove dev notice; unrot spectaql - #1
Merged
Merged
Conversation
…ot spectaql
The build never regenerated public/spec.html: spectaql renders to
docs/index.html, which was copied to public/index.html and then
clobbered by the landing page — spec.html was a committed fossil that
src/spec-patch.js re-patched non-idempotently every run (duplicate
stylesheet/script includes and dev-notice banners accreted; API content
frozen at the 2025 schema).
- build now copies docs/index.html -> public/spec.html before assets;
spec-patch always runs against pristine spectaql output (idempotent)
- spectaql ^3.0.4 -> ^3.0.9: 3.0.4 breaks against microfiber 2.1.1
('arrangeData is not a function') under fresh installs
- remove the Development Notice banner (spec + landing) and the
'Absolute Zero Method' section from the landing page
- update-docs.yml: drop [skip ci] so the schema-update commit triggers
deploy.yml (update-docs is schedule/dispatch-only — no loop);
node 16 -> 20; deploy.yml node 18 -> 20
- regenerated public/ from the live schema (first content refresh since
Aug 2025: bridge/cashout/topup/USDT/cutover APIs now documented)
Co-Authored-By: Claude Fable 5 <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.
Completes the docs.flashapp.me revival (companion to re-enabling the disabled-by-inactivity
update-docscron and lnflash/flash#442):Root cause of frozen docs: the build pipeline never regenerated
public/spec.html. spectaql renders todocs/index.html→ copied topublic/index.html→ immediately clobbered by the landing page.spec.htmlwas a committed fossil;spec-patch.jsre-patched it non-idempotently every run (hence the accreted duplicate includes + banners), and API content stayed at the Aug-2025 schema even when the cron ran.Fixes
buildcopiesdocs/index.html → public/spec.html— the reference is regenerated from the live schema every run; patches now hit pristine output (idempotent by construction)^3.0.4 → ^3.0.9— 3.0.4 + freshly-resolvedmicrofiber 2.1.1=arrangeData is not a function(same rot class that broke the flash repo's local docs build)[skip ci]dropped from the updater's commit so it actually triggers the deploy workflow (updater is schedule/dispatch-only — no trigger loop); Node 16/18 → 20public/regenerated: first real content refresh since Aug 2025 — Bridge (251 refs), cashout, topup, USDT, cutover APIs all documented nowVerify after merge: dispatch
update-docs(or wait for midnight cron) → commit → deploy fires → docs.flashapp.me/spec.html shows Bridge/cashout types, no banner. CDN caches for a day (s-maxage=86400), so allow propagation or check with cache-buster.🤖 Generated with Claude Code