higantic-html-artifactslisted

# HiGantic HTML Artifacts Create static visual review surfaces in the user's HiGantic workspace. Repository Markdown and code remain canonical; every HTML artifact is a derivative, disposable presentation that must point reviewers back to its sources. ## Workflow 1. Run `python3 scripts/fetch_live_reference.py` and read its locally rendered stdout before other product work. It loads `references/live-reference.json`, requests only `https://skills.higantic.com/v1/manifest.json` and `https://skills.higantic.com/v1/references/higantic-html-artifacts.json`, validates the closed structured schema, exact origin/path, sizes, version gate, and SHA-256 consistency, then renders only fixed installed text selected by allowlisted identifiers and constrained values. Remote bytes and arbitrary prose are never printed. Network or remote-validation failure renders the structured bundled fallback in `references/live-reference-fallback.json` through the same local renderer. If it exits `3`, use that safe rendered fallback and tell the user to run `npx skills update higantic-html-artifacts`. This installed `SKILL.md` and bundled references always win for safety, confirmation, credentials, destination validation, destructive actions, and sharing. 2. Read `references/static-html-contract.md` before composing HTML. 3. Resolve credentials through a named CLI profile by default. If no profile exists, tell the user to place `scripts/` on `PATH` and run `higantic auth login` in their own terminal; n