T-MYD5-flowline-docs-site-build-in-no-ci-gate
State: closed/done · Impact: medium · Complexity: small
Register packages/ts/flowline/docs-site as a moon project so its build runs
in CI, closing the same gap as
T-QGYW-waypost-docs-site-build-in-no-ci-gate for this package.
| Location | Role today |
|---|---|
packages/ts/flowline/docs-site/ | Astro Starlight site with dev, build, preview, astro scripts. No moon.yml, so it is not a moon project. |
.moon/workspace.yml | Project globs stop at packages/ts/*. A nested docs-site needs an explicit sources: entry — every one of them is a directory of that name, so folder-derived ids would collide. |
.github/workflows/ci.yml | moon run :check :test --affected reaches registered projects only. |
The build is green: verified 2026-08-31, 11 pages in 2.98s after a cold
bun install. Its dependencies were not installed at all, which is what an
unbuilt, ungated site looks like from the outside.
Proposed
Section titled “Proposed”The site is a moon project, registered by the explicit sources: entry
T-QGYW-waypost-docs-site-build-in-no-ci-gate adds, and its build runs in CI
as an unconditional step beside that task’s.
Unconditional rather than affected-driven for the reason that task records: it
is layer: application, which CI’s affected step excludes outright, and a gate
that exists because something was silently skipped must not itself be
skippable.
Approach
Section titled “Approach”- Wait for the workspace registration and the CI-step pattern from T-QGYW-waypost-docs-site-build-in-no-ci-gate.
- Add
moon.ymlmodelled onsites/df-docs/moon.yml; project idflowline-docs. NodependsOn— moon’s javascript toolchain syncs project dependencies intopackage.jsonasworkspace:*, which cannot resolve from a directory outside the repo’s workspaces. Theinstalltask matters more here than for its siblings, since this site is its own Bun root and nothing else installs it. - Nothing to check about test files. That question came from a wrong premise
in T-QGYW-waypost-docs-site-build-in-no-ci-gate, corrected there: the
package tsconfigs already include
tests/**, somoon run <pkg>:checktypechecks them. This gate is a build check — the site is published and nothing builds it — which is the whole claim.
Files to touch
Section titled “Files to touch”| Location | Kind | Change |
|---|---|---|
packages/ts/flowline/docs-site/moon.yml | new | Register the site; install, build, dev tasks. |
Acceptance criteria
Section titled “Acceptance criteria”- AC-1:
moon run flowline-docs:buildsucceeds from a clean checkout, including the install step. - AC-2: The site’s build runs as its own CI step, and a failure in a sibling site’s step does not hide it.
Out of scope
Section titled “Out of scope”- The
.moon/workspace.ymlregistration and the CI-step shape, which T-QGYW-waypost-docs-site-build-in-no-ci-gate carries.
Dependencies
Section titled “Dependencies”- T-QGYW-waypost-docs-site-build-in-no-ci-gate for the registration and the CI-step pattern.
Discovery context
Section titled “Discovery context”Found while scoping T-QGYW-waypost-docs-site-build-in-no-ci-gate on
2026-08-31: three docs sites are unregistered, and only sites/df-docs is
gated.
Depends on
Section titled “Depends on”T-QGYW