html2linklisted

# html2link Artifact Publishing Publish a finished local artifact and return the exact URL from the API. Treat every generated URL as public. ## Core workflow 1. Finish and verify the artifact before uploading it. 2. Package a multi-file static site as a ZIP containing `index.html`. 3. Check that the artifact contains no secrets, credentials, or unintended private data. 4. Prefer the `html2link` CLI when it is installed; otherwise use the anonymous curl fallback. 5. Parse the exit status and JSON response. Do not claim success unless it contains `url`. 6. Return the exact `url` value as a clickable link. Do not reconstruct it from `slug`. ## Publish a new artifact With the CLI: ```bash html2link publish /absolute/path/to/report.html ``` Anonymous curl fallback for files up to 1 MB: ```bash curl --fail-with-body -F "file=@/absolute/path/to/report.html" https://html2link.dev/api/upload ``` For larger files, use an API token from the signed-in home page: ```bash HTML2LINK_API_TOKEN="..." html2link publish /absolute/path/to/report.html ``` Keep authenticated operations in the CLI so credentials stay in the local process environment rather than being embedded in reusable shell commands. Use `--json` when another program needs the complete response: ```bash html2link publish /absolute/path/to/report.html --json ``` ## Handle a successful response ```json { "slug": "a1B2c3D4", "updateToken": "keep-this-private", "url": "https://html2link.dev/x/a1B2c3D4", "kind