Relaunch Packages as a modular distribution hub

[VolkerChristian]

What was built

Rendered distribution/meta hub, not a copied product README: installation routes, project package catalogs, platform overview, signing identity, troubleshooting and publication model.

• Dedicated SNode.C status and MQTTSuite status, with independent available-package / latest-attempt information.
• One project directory; retained legacy distribution/release status anchors are routes, not another matrix.
• Consistent 16 px button menus and 1/4-height supporting-page banners; complete install procedures and useful package/runtime details retained in authoritative guides/catalogs.
• Authored source is DistributionPackages site/; status projection has one implementation there. No workflow added to Packages. This branch contains only README/docs/status Markdown or assets; no package/state/installer/key blobs changed.

Rendered from Packages snapshot fe2cde6448cf832342e96c8a2e3b715d6cf4ae1d. It is a review snapshot, not an assertion of live deployment. Historical unavailable timestamps remain marked not recorded. Companion source PR must accompany cutover.

Change accounting

Documentation/SVG presentation: +784 / -1041 (no-renames accounting). Zero production/test code lines in this repository.

Scope and verification

• No licence, key/secret, installer, release tag, product workflow, package binary/feed, target matrix, build/signing adapter or dispatch-trigger changes.
• Local suite: 44 tests executed, 43 passed, one skipped (real OpenWrt signing-tools test: tools unavailable on PATH). Tests retain provenance, state ordering, feed/signing, concurrent-writer and lease-conflict coverage; added deterministic multi-project rendering, event attribution and actual docs-overlay shell coverage.
• 20 public pages rendered with GitHub's Markdown API: local links, image paths, banner/section anchors pass; both project status pages cover all 76 targets. This is structural/GFM verification, not a mobile/dark-theme browser visual review.
• One intermediate full-suite run failed when a concurrent-writer fixture Git clone returned exit 128, followed by fixture cleanup failure; the earlier full run passed. The final full rerun passed: 43 passed, one skipped. Both logs are retained. No tests were weakened.
• Workflow YAML parses; local actionlint reports the same diagnostics on base and modified workflows (queue and App input metadata); no new diagnostics.
• No manual Actions dispatch, tag movement or package rebuild.

Deployment / review gate

Do not merge during active package writers. Existing immutable release captures execute their original renderer: they cannot record the new timestamp fields and may still regenerate the legacy status layout. The currently running SNode.C capture is 38074650868 (attempt 2, observed in progress during preparation).

At a quiet point, merge the source change and refresh the rendered Packages snapshot against the latest live feed/state before merging its companion PR. Packages publications replace snapshot history, so its PR branch/base may need recreation from the current API-read default branch. Preserve all newer package/state data.

New timestamps/stage metadata arrive only from captures containing this updated tooling; historical unknowns remain explicitly not recorded, never guessed. Current authored-document overlay protects public prose for older recipe captures, but does not replace their capture-pinned executable renderer. These PRs do not make the relaunch live on their own.

Companion PRs

• DistributionPackages
• Packages
• .github

Preview: Packages hub · SNode.C status · MQTTSuite status

[VolkerChristian]

Cutover update: all product and publisher workflows are stopped. Regenerated all public pages from final Packages snapshot d82fa36fb40b4f371c891f506d7e2e29c2ac2fd6; preserved live status.json, all feed records/binaries, keys, installer and immutable badge bytes. All 20 rendered pages pass local link/image/anchor checks; 76 target rows per project. No CI or tag trigger requested.