Skip to content

docs(corral): quote the incus tag key so the site builds again - #119

Merged
hanthor merged 5 commits into
mainfrom
claude/github-open-issues-prs-bmqn8j
Aug 8, 2026
Merged

docs(corral): quote the incus tag key so the site builds again#119
hanthor merged 5 commits into
mainfrom
claude/github-open-issues-prs-bmqn8j

Conversation

@hanthor

@hanthor hanthor commented Aug 8, 2026

Copy link
Copy Markdown
Member

The outage

main is red and tunaos.org has not been deploying. Both bootstrap jobs and the Cloudflare Workers Builds: tunaos-org check fail on the same root cause — Cloudflare runs the same docusaurus build, so this is a real build failure, not a disconnected integration.

Docusaurus parses .md as MDX, and line 172 of docs/corral/backend-parity.md contains a bare <name>:

- **tags** — instance config user.corral.tag.<name>

MDX reads that as an unclosed JSX element and aborts the whole client bundle:

[ERROR] Client bundle compiled with errors therefore further build is impossible.
╰─▶ × Error: MDX compilation failed for file ".../docs/corral/backend-parity.md"
    │ Cause: Expected a closing tag for `<name>` (172:46-172:52) before the end of `paragraph`
    │ "ruleId": "end-tag-mismatch"

The file arrived via the org doc sync, so the site has been down since that sync landed.

The change

One line — wrap the config key in backticks. Backticks over HTML-escaping so the source stays readable and renders identically on GitHub; it's also more correct, since the string is a config key.

Verified, not assumed

Ran the real build locally both ways:

$ npm ci && npm run build
# WITHOUT the fix:
  × Error: MDX compilation failed for file "/home/user/docs/docs/corral/backend-parity.md"
    Cause: Expected a closing tag for `<name>` (172:46-172:52) before the end of `paragraph`
  exit 1

# WITH the fix:
  [SUCCESS] Generated static files in "build".

So the failure and the fix are both confirmed by execution, not inference.

Scope — deliberately one line

I scanned every .md/.mdx under docs/ for bare angle brackets outside code fences. The other hits are all fine and are left untouched:

  • <details>, <summary>, <div>, <Tabs>, <code> — real, properly-closed HTML/JSX that MDX handles.
  • docs/corral/SPEC.md <image>/<uuid> — inside a multi-line inline-code span, which MDX does not parse.

The successful build above confirms none of those needed changing.

Durability

This file is generated by the doc sync, so a fix here alone would be overwritten on the next sync run. The same one-line fix is going in at the source: tuna-os/corral#173. This PR is the immediate unblock so the site can deploy now; that one stops it recurring.

Assisted-by: Claude Code


Generated by Claude Code


View with [code]smith
Need help on this PR? Tag @codesmith-bot with what you need. Autofix is enabled.

hanthor added 5 commits August 8, 2026 07:29
`main` has been failing since the org doc sync landed this file: Docusaurus
parses `.md` as MDX, and the bare `<name>` in the incus tags bullet reads as
an unclosed JSX element.

    Error: MDX compilation failed for file ".../docs/corral/backend-parity.md"
    Cause: Expected a closing tag for `<name>` (172:46-172:52) before the end
    of `paragraph` — "ruleId": "end-tag-mismatch"

This takes down the whole build, so it is not a lint failure — both
`bootstrap` jobs and the Cloudflare Workers build fail, and tunaos.org has
not deployed since.

Verified locally with `npm ci && npm run build`: fails with exactly the above
without this change, and reports `[SUCCESS] Generated static files` with it.

This file is generated by the doc sync, so the same fix is going in upstream
at tuna-os/corral (PR #173) to stop the next sync reintroducing it; this
commit is the immediate unblock. Only the one occurrence is touched — the
other bare angle brackets in these docs are either real closed HTML
(`<details>`, `<summary>`) or sit inside code spans, which MDX does not parse.

Assisted-by: Claude Code
@cloudflare-workers-and-pages

Copy link
Copy Markdown

Deploying with  Cloudflare Workers  Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status Name Latest Commit Preview URL Updated (UTC)
✅ Deployment successful!
View logs
tunaos-org 2817f94 Commit Preview URL

Branch Preview URL
Aug 08 2026, 07:30 AM

@hanthor
hanthor merged commit a60e14c into main Aug 8, 2026
8 checks passed
hanthor-hive-agent Bot added a commit that referenced this pull request Aug 10, 2026
The repo tuna-os/bootc-migrate-composefs was renamed to tuna-os/bootc-migrate
(2026-07-24, bootc-migrate#97), but the docs site's project surface still
uses the pre-rename name:

- src/data/projects.ts: project id/name 'bootc-migrate-composefs', repo URL
  and docs path pointing at the old names
- src/pages/bootc-migrate-composefs.tsx: landing page slug
- docs/dakota/migration.md: install/run commands use the bootc-migrate-composefs
  binary name and old repo URLs

Update the project entry to 'bootc-migrate' (id, name, repo, docs, install
snippets), rename the landing page to /bootc-migrate, and align the Dakota
migration guide with the canonical binary name. Release artifacts still
carry the pre-rename bootc-migrate-composefs asset/binary name (v0.2.0
predates the rename), so the install commands keep that name but install it
as bootc-migrate, matching the merged bootc-migrate README fix (#119).

Signed-off-by: hanthor-hive-agent[bot] <hanthor-hive-agent[bot]@users.noreply.github.com>
Co-authored-by: hanthor-hive-agent[bot] <hanthor-hive-agent[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant