Finding
The tuna-os/docs repository (Docusaurus documentation site) has no test, lint, or validation infrastructure:
- No test files — no jest, playwright, or any test framework
- No build validation — CI does not verify the Docusaurus site builds successfully
- No link checking — no automated broken link detection
- No markdown linting — no markdownlint or equivalent
- CI workflows are limited — only
sync-org-docs.yml and update-iso-index.yml, neither validates site quality
This means:
- A broken build could be merged and deployed unnoticed
- Broken links in documentation accumulate silently
- Markdown formatting issues slip through
Recommendation
- Add a build validation workflow — run
npm ci && npm run build on PRs to catch TypeScript/build errors
- Add markdownlint — validate all
.md and .mdx files
- Add link checking — use
lychee or similar to check for broken URLs in built HTML
- Add TypeScript type checking —
tsc --noEmit as a CI step
Priority
- Impact: high — broken docs site degrades user trust and discoverability
- Effort: low — build validation is one GHA job addition
Filed by quality agent (ACMM L4/L6 — full mode)
Finding
The
tuna-os/docsrepository (Docusaurus documentation site) has no test, lint, or validation infrastructure:sync-org-docs.ymlandupdate-iso-index.yml, neither validates site qualityThis means:
Recommendation
npm ci && npm run buildon PRs to catch TypeScript/build errors.mdand.mdxfileslycheeor similar to check for broken URLs in built HTMLtsc --noEmitas a CI stepPriority
Filed by quality agent (ACMM L4/L6 — full mode)