Skip to content

fix(frontend): keep the dashboard served while a frontend build runs - #16217

Merged
chenmingwei23 merged 2 commits into
mainfrom
fix/prestage-dev-dist
Oct 4, 2026
Merged

chenmingwei23 merged 2 commits into
mainfrom
fix/prestage-dev-dist

Conversation

@bolichen97

@bolichen97 bolichen97 commented Oct 2, 2026 •

Copy link
Copy Markdown
Contributor

Problem / Motivation

Goal: A source-checkout dashboard keeps serving a complete bundle while the frontend is rebuilt, and picks up the new build without a gateway restart.

On a source checkout src/kiro_crew/static/dist is a link to website/dist. Every Vite build emptied website/dist and rewrote it in place, so for the whole npm run build a running gateway served no bundle: the dashboard went blank and the stale-asset watchdog read the gap as a vanished install. Every builder hits this: gateway auto-apply, POST /api/update, kirocrew update and Dev Fleet's Pull+Build. Separately, the /assets, /sprites, /fonts, /vendor and /app-assets routes were add_static mounts that resolve their directory once at start, and were registered only if a build existed then. So re-pointing static/dist left index.html referencing chunks the pinned routes could not serve, and a gateway started before the first build never served one.

Why it matters

Every frontend rebuild on a source checkout (the dev and Dev Fleet path, and every update that rebuilds the frontend) blanks the dashboard for the length of the build. A gateway started before the first build stays on the "not built" page until it is restarted. #13960's watchdog stand-down exists only to cover this gap.

Not a goal

  • A per-edition outDir. An edition bundle is still staged as a private copy.
  • Routing install.sh's own rm -rf + copy through the stager. That is documented as not covered.
  • Re-enumerating app-window entries at runtime. A window first built after start still needs a restart, as on main.
  • Changing what the build-pending badge reports.

What changed (motivation → approach → change)

Symptom → cause: the served tree was emptied and rewritten in place, and the build routes were pinned to whatever directory they resolved at start.

Approach: the served tree is never rewritten. A build publishes into website/dist by rename, and staging only re-points a link. Every build route resolves static/dist per request, so a running gateway follows either change at once. An alternative was to copy the current bundle aside before each build (#15834's proposal). That still leaves the routes pinned, so it was not taken.

Change, in two commits:

  • Dashboard (dashboard/server.py). Each build prefix and each app-window entry is now a GET route, registered whether or not a build exists, that resolves static/dist on every request off the event loop. It applies the same confinement as add_static: the resolved file must sit inside the resolved subdirectory, and a rooted, drive or share tail is refused before any lookup. A miss is a no-store 404. FileResponse still serves precompressed siblings, ranges and conditional requests. security.md's /vendor paragraph is updated in this commit.
  • Frontend (frontend.py, website/scripts/publish-dist.mjs).
    • A Vite plugin, registered last, builds every mode except --watch into a scratch sibling. It renames that over website/dist only after its post-order writeBundle has run, so a failed build leaves website/dist alone. precompress.mjs and the sw.js stamp follow the resolved outDir.
    • Staging re-points static/dist: at website/dist for a stock build that publishes this way, otherwise at a fresh immutable static/.dist.<id> copy. An older target revision that still builds in place has its served bundle moved to such a copy before it builds. The tree-rename swap and its rollback are removed. A build counts as published only if it replaced index.html, compared by (st_mtime_ns, st_ino).
    • A stock checkout whose gateway starts before anything is built links static/dist to its unbuilt website/dist, so the first build is served once it lands.
    • An edition gateway stages its copy at start, through cli_server.py, off the event loop. It waits at most 5 s for the lock, and otherwise serves what it found with a warning.
    • python -m kiro_crew.frontend stage [REPO] is the one stage entry point. make/make.ps1 run it in build and wheel after the backend install.
    • setup.py's warning, the clean targets (scripts/clean.sh), MANIFEST.in, .gitignore, website/.gitignore, jscpd, scripts/docs_lint.py, Dev Fleet (runtime.py, worktree_ops.py comments) and kirocrew-worktree-dev/SKILL.md all cover the new names. No dependency changes: website/package.json only extends its clean script.

Specs and docs updated in the same commits: docs/system-specs/modules/dev-fleet.md, learn-cron-dashboard.md, security.md, docs/guides/install.md, docs/guides/windows-install.md, docs/build/gui-user-test.md, CONTRIBUTING.md, website/README.md.

Case Before After
Gateway serving through the dev link during npm run build 🟥 blank until the build ends 🟩 old bundle, then the new one
Gateway started before the first build 🟥 "not built" page until restart 🟩 served once the build lands
Stage re-points static/dist 🟥 chunks 404 until restart 🟩 followed on the next request
Failed build 🟥 website/dist left half-written 🟩 website/dist untouched
Edition bundle staged 🟦 private copy 🟨 immutable copy, link re-pointed

🟩 added · 🟨 changed · 🟥 removed · 🟦 unchanged

Backwards compatibility

Compatible: nothing main accepts is rejected. static/dist is still a directory or a link to one, and every route still answers at the same prefix. A gateway still running pre-PR code across the transition from a real static/dist to a link is told in the stage log to restart (documented in dev-fleet.md and install.md).

Reader: src/kiro_crew/dashboard/server.py:_register_dist_static_routes -- entry: crew page -- the removed add_static mounts are replaced by per-request routes at the same prefixes | test_every_build_prefix_is_registered_whatever_the_build_holds
Reader: src/kiro_crew/frontend.py:_stage_dist_locked (removed tree swap / .dist.staging.* / .dist.previous.*) -- entry: release -- residue of the old names is swept by _sweep_staged_locked | test_stage_built_dist_sweeps_abandoned_staging_dirs
Reader: Makefile:frontend (no longer stages) -- entry: release -- build and wheel stage after backend; install.md says so | test_documented_target_table_covers_every_target
Reader: make.ps1:Invoke-Frontend (no longer stages) -- entry: release -- Invoke-Build/Invoke-Wheel call Invoke-StageDashboard | test_makefile_and_powershell_expose_the_same_targets

Tests

  • test/integration/test_route_sweep.py: /assets, /fonts and /vendor, public by design (token_auth bypass), are listed as unguarded 404s now that they are registered with no build.
  • test/test_dashboard_static_routes.py: every prefix is registered with no build. A build that lands after start is served. A re-pointed link is followed on the next request. Traversal, an escaping link and anchored tails are refused before any lookup. The /assets root fallback and precompressed siblings still work.
  • test/test_dashboard_asset_404_cache.py: a file swept after it was resolved is a no-store 404.
  • test/test_frontend_dist_resolve.py: link versus copy staging, re-pointing any occupant, sweeps by identity, failed re-points leave the served tree, the restart notice, .gitignore in copies, the build-exits-0-without-publishing guard, the link made before the first build, an in-place target copied before it builds, gateway-start lock budgets, the stage CLI (relative REPO, non-checkout refusal, held lock), and _print_safe on narrow or absent consoles. Shared completeness fixtures pin the Python and JS rules equal.
  • test/test_frontend_edition_build.py and test/test_cli_server_more_coverage.py: the edition stage runs off the event loop.
  • website/src/test/publishDist.test.ts: the swap, a first build, an incomplete build refused, the in-place fallback, the rollback budget, Windows retry, and the plugin publishing last and never after a failed writeBundle.
  • website/src/test/publishDistBuild.test.ts: a real Vite build publishes on success. A failure in transform, writeBundle, an enforce: 'post' plugin or an order: 'post' hook publishes nothing and keeps its own error.

Manual verification

  • A real Vite build (publishDistBuild.test.ts, a real Vite run rather than a mock) publishes only on success, and each injected failure keeps its own error in Vite's output.
  • A bind-mount spelling of the checkout (unshare -rm, mount --bind): the served copy survives a re-stage and is still served.

Related Issues

Fixes #15834

Pattern harvest

Rule candidate: review-prompt
Pattern: "a route or handle resolved once at startup over a path that is re-pointed at runtime"

Checklist

  • At most two commits (one is the norm), with a Conventional Commits title (feat|fix|docs|style|refactor|perf|test|chore|ci|build|revert: ...)
  • Existing tests pass and new tests added for new functionality
  • Self-review completed; code follows project style guidelines
  • Documentation updated (if applicable)
  • No secrets, credentials, or internal references in the diff

@bolichen97
bolichen97 requested a review from a team as a code owner October 2, 2026 17:52
@github-actions github-actions Bot added the readiness: checking Automated validation is still running label Oct 2, 2026
@github-actions

github-actions Bot commented Oct 2, 2026 •

Copy link
Copy Markdown
Contributor

UX Review (Opus 5.5) — ✅ PASS

UX-level review of 8c600e974d747d67d9c8c8288fb8b6b448b41ae6 — updated in place on each push. A BLOCK verdict blocks PR readiness; PASS/CONCERNS are advisory.

UX-Verdict: PASS

Check by hand that an open dashboard keeps rendering through npm run build and loads the new bundle on reload without a gateway restart.

[UX-REVIEWED] 8c600e9

Description read

[DESCRIPTION-READ] 91c21c4d9400a705a2783190f8bf5651e06973d5e3dd4a10d378af6ca10b556c

That sha256 names everything this verdict read: the PR description, plus the 3 evidence file(s) the workflow collected from it and handed this review. It covers that evidence because the media strip replaces every attachment URL with the same placeholder, so an edit swapping one attachment for another would leave the description's captured text identical while what this review judged changed. Recompute it with .github/scripts/pr-description-capture.sh over the same inputs; if it differs, the description or that evidence changed after this verdict was formed and any finding drawn from either is unproven.

@github-actions github-actions Bot added readiness: action required A blocking check or review needs attention and removed readiness: checking Automated validation is still running labels Oct 2, 2026
@github-actions

github-actions Bot commented Oct 2, 2026 •

Copy link
Copy Markdown
Contributor

Design Review (Opus 5.5) — 🟡 CONCERNS

Design-level review of 8c600e974d747d67d9c8c8288fb8b6b448b41ae6 — updated in place on each push. A BLOCK verdict blocks PR readiness; PASS/CONCERNS are advisory.

Design-Verdict: CONCERNS

On Windows every Vite build now depends on renaming website/dist while a running gateway may have files open in it, and nothing in the PR shows that path working on Windows.

Watch

  • Windows publish. publishDist renames the live tree aside, then puts the new tree in its place. Windows refuses a rename while any handle is open in the tree. A gateway serving /assets through the junction holds such handles, and so do antivirus and the search indexer, which RENAME_RETRY_BUDGET_MS itself names. The second rename gets only IN_GAP_BUDGET_MS = 1_500. If it misses, the old tree goes back and the build fails, so kirocrew update, POST /api/update and Pull+Build fail on exactly the case this PR targets: a live dashboard during a rebuild. The fake-rename unit tests check the retry logic, not real Windows behaviour.
    Clears when: a Windows run (CI job or a manual log in the PR) shows npm run build publishing while a gateway serves through the junction, or the build falls back to in-place output on Windows when the swap is refused.

[DESIGN-REVIEWED] 8c600e9

Description read

[DESCRIPTION-READ] 4f931afad8cb45717c20cc5368bf8cebd417935e72e73f7d355a158b65973357

That sha256 names everything this verdict read: the PR description, plus the 1 evidence file(s) the workflow collected from it and handed this review. It covers that evidence because the media strip replaces every attachment URL with the same placeholder, so an edit swapping one attachment for another would leave the description's captured text identical while what this review judged changed. Recompute it with .github/scripts/pr-description-capture.sh over the same inputs; if it differs, the description or that evidence changed after this verdict was formed and any finding drawn from either is unproven.

@github-actions

github-actions Bot commented Oct 2, 2026 •

Copy link
Copy Markdown
Contributor

First Principles Review (Opus 5.5) — 🟡 CONCERNS

Premise-level review of 8c600e974d747d67d9c8c8288fb8b6b448b41ae6 — why this exists and whether the shipped surface is the smallest honest version. Updated in place on each push. A BLOCK verdict blocks PR readiness; PASS/CONCERNS are advisory.

First-Principles-Verdict: CONCERNS

The edition gateway now copies the whole bundle at boot, waiting up to 5 s for the lock. The fix doesn't need this, and no reported edition defect backs it.

Not justified as shipped

  • Item 6 — rides along, inherited: the code's only stated reason is "so a later stock build in the same checkout cannot replace the edition dashboard". Base ensure_dev_dist_symlink had the same link-to-website/dist exposure, and Dev Fleet already skips the build on an edition (_sync_start_locked). No issue or failing-on-base test names this harm.
    Subtraction: delete the edition_configured() stage branch in ensure_dev_dist_symlink and _GATEWAY_START_LOCK_TIMEOUT. Editions then link at start exactly as on main.
    Clears when: a linked issue or failing-on-base test shows an edition gateway serving a stock bundle, or the branch is removed.

What this change ships

Inventory (10 items) — 8 justified

Intent: keep a source-checkout dashboard served through a frontend rebuild, and pick up new builds without a restart. This is a FIX.

  1. Dashboard keeps serving the old bundle during npm run build (atomic publish plugin) — justified
  2. A failed build leaves website/dist untouched — justified
  3. Build routes are always registered and resolved on every request, so a gateway started before the first build serves it — justified
  4. Staging re-points a link instead of rm + copy; static/dist becomes a link — justified
  5. An older target revision's served bundle is copied aside before its in-place build — justified
  6. An edition gateway copies the bundle at start, waiting up to 5 s for the lock — rides along, inherited
  7. New python -m kiro_crew.frontend stage CLI, used by the Makefile and make.ps1 — justified
  8. make frontend no longer stages; build/wheel stage after the backend install — justified
  9. A mount point or EBUSY live tree is rewritten in place file by file — justified
  10. Log output can no longer raise (_print_safe); the unreadable-index message now shows only the errno code — rides along

[FIRST-PRINCIPLES-REVIEWED] 8c600e9

Description read

[DESCRIPTION-READ] e616b7b18bd027b4e551e09d6e720ef92b9e80fa4b7066a622771663a69f04d9

That sha256 names the PR description this verdict read. Recompute it with .github/scripts/pr-description-capture.sh; if it differs, the description changed after this verdict was formed and any finding drawn from the description is unproven.

@github-actions

github-actions Bot commented Oct 2, 2026 •

Copy link
Copy Markdown
Contributor

GPT 6.1 Review — ✅ no blocking findings

GPT 6.1 completed its review of 8c600e974d747d67d9c8c8288fb8b6b448b41ae6 and found no blocking issues.

This comment is updated in place on each push.

Review details

No findings.
[GPT-REVIEWED] 8c600e9

False positive or not applicable? A repository writer can comment:
/ai-review override gpt 8c600e974d747d67d9c8c8288fb8b6b448b41ae6: <one-sentence reason>

@github-actions

github-actions Bot commented Oct 2, 2026 •

Copy link
Copy Markdown
Contributor

Opus 5.5 Review — ✅ no blocking findings

Reviewed 8c600e974d747d67d9c8c8288fb8b6b448b41ae6 — this comment is updated in place on each push.

Review details

No findings.

[OPUS-REVIEWED] 8c600e9

Verdict parsed from the review's SHA-scoped output markers for commit 8c600e974d747d67d9c8c8288fb8b6b448b41ae6.

False positive or not applicable? A repository writer can comment:
/ai-review override fable 8c600e974d747d67d9c8c8288fb8b6b448b41ae6: <one-sentence reason>

@bolichen97
bolichen97 force-pushed the fix/prestage-dev-dist branch from 474cf4c to fdead1f Compare October 2, 2026 21:27
@github-actions github-actions Bot added readiness: checking Automated validation is still running and removed readiness: action required A blocking check or review needs attention labels Oct 2, 2026
@bolichen97

Copy link
Copy Markdown
Contributor Author
  • Removing the prior bundle breaks in-flight page loads (span=f4c4c8e65134)

rebutted, not a defect of this change: on main every Vite build empties website/dist (emptyOutDir) before writing, so the prior generation's hashed assets are gone for the whole build and after it; this PR keeps them served until the cutover and removes them only after it, so the retention window strictly grows.
The anchored line removes a tree the cutover rename (publish-dist.mjs:192) already took off the served path; carrying assets forward would be a new cross-generation retention and GC mechanism, outside this PR's frozen goal (serve a complete bundle during a rebuild).
No data is written, lost or corrupted: a tab holding an older index recovers through the purpose-built vite:preloadError reload (website/src/main.tsx:94-127, cooldown plus a three-reload cap) or the shell's boot-failure panel (website/index.html), as it does after any update on main.
Override reason a maintainer may verify and paste: old-tab chunk 404s after a rebuild are pre-existing on main (emptyOutDir) and self-heal via main.tsx's preloadError reload; this PR only lengthens how long the prior bundle stays served.

@bolichen97

Copy link
Copy Markdown
Contributor Author
  • static/dist left absent when nothing is built at start (span=083ada710bf8)

fixed in fdead1f: when nothing is built, a stock checkout's gateway start now links static/dist to its unbuilt website/dist (the same link a start keeps once website/dist was removed), and still returns None so the "not built" warning is logged. No link under an edition, outside a checkout, or where the platform cannot link a missing directory.
Tests: test_a_gateway_started_before_the_first_build_serves_it_once_it_lands[nothing|an-empty-real-dir], test_an_unbuilt_checkout_that_cannot_be_linked_starts_as_before, test_an_edition_does_not_link_an_unbuilt_website_dist; dev-fleet.md updated.

@bolichen97

Copy link
Copy Markdown
Contributor Author
  • make backend PY-precedence flip rides along (span=8726f124f0e3)

fixed in fdead1f by the stated subtraction: RESOLVE_PY and PY_GE_312 are gone and make backend resolves the interpreter exactly as main does (recorded interpreter, then $(PY)). Staging runs through $(VENV)/bin/python, so nothing in the fix needed the flip; the body and commit message no longer claim it.

@github-actions github-actions Bot added readiness: action required A blocking check or review needs attention merge conflict Branch has merge conflicts with its base — author must resolve before merge and removed readiness: checking Automated validation is still running labels Oct 2, 2026
@bolichen97
bolichen97 enabled auto-merge (squash) October 3, 2026 20:44
@bolichen97
bolichen97 force-pushed the fix/prestage-dev-dist branch from fdead1f to 7393d4b Compare October 4, 2026 07:08
@bolichen97

bolichen97 commented Oct 4, 2026 •

Copy link
Copy Markdown
Contributor Author
  • span=f4c4c8e65134 In-place fallback can corrupt the served bundle

fixed in 7393d4b: rewriteInPlace now copies the new build into a staging dir inside the live tree first; a copy failure (ENOSPC/EIO) leaves every live file unchanged.
The merge is per-file rename within one filesystem, with the top-level index.html last, then extras are removed.
Tests: publishDist.test.ts snapshots the whole live tree across EBUSY/EXDEV x ENOSPC/EIO copy failures.

@bolichen97

bolichen97 commented Oct 4, 2026 •

Copy link
Copy Markdown
Contributor Author
  • span=04a5b3eeddaf git init without cwd= in test_frontend_dist_resolve.py

fixed in 7393d4b: subprocess.run([git, "init", "-q"], cwd=str(tmp_path), check=True). No other child in the file creates files without cwd=.

@bolichen97

bolichen97 commented Oct 4, 2026 •

Copy link
Copy Markdown
Contributor Author
  • span=953f59806157 edition stage failure falls back to linking static/dist at the source

rebutted: the fallback is deliberate and logged ("Could not stage the edition bundle; serving %s through the link"); main links static/dist the same way under an edition today.
Returning None would turn a transient 5 s lock timeout at gateway start into a blank "not built" dashboard, which is the failure this PR exists to remove.
The next successful stage replaces the link with a private copy, so the window ends at the next build.

@github-actions github-actions Bot added readiness: checking Automated validation is still running and removed readiness: action required A blocking check or review needs attention labels Oct 4, 2026
@bolichen97

bolichen97 commented Oct 4, 2026 •

Copy link
Copy Markdown
Contributor Author
  • span=f4c4c8e65134 Abandoned sweep deletes both recoverable bundles

rebutted (not a data-loss defect): the loss needs a SIGKILL between two adjacent POSIX renames (no retry widens it off Windows) AND a later build that itself fails.
What is lost is a regenerable build artifact, not user data; re-running the build restores it.
The absence is loud: the stale-asset watchdog logs CRITICAL and the stager logs "Built dist not found".
The proposed fix turns the sweep into a promotion path with its own ordering contract against concurrent builds, for this one window.

@github-actions github-actions Bot added readiness: action required A blocking check or review needs attention and removed merge conflict Branch has merge conflicts with its base — author must resolve before merge readiness: checking Automated validation is still running labels Oct 4, 2026
The /assets, /sprites, /fonts, /vendor and /app-assets mounts were
add_static routes, which resolve their directory once at registration,
and they were registered only when static/dist existed at start. On a
source checkout static/dist is a link, and index.html, the PWA files
and the stale-asset watchdog read through it on every request. So
once anything re-pointed the link, index.html referenced chunks the
pinned routes could not serve, a blank dashboard until a restart, and
a gateway started before the first build never served one at all.

Each build prefix is now a GET route registered whether or not a build
exists, which resolves static/dist on every request, off the event
loop as aiohttp's own static handler does. A resolved file must sit
inside the resolved subdirectory, the same confinement add_static
applies without follow_symlinks; a tail that names a root, a drive or
a share is refused before any lookup, as add_static refuses it; and a
miss is a no-store 404. App window entries are still enumerated at
start but resolved per request the same way, so a window first built
after start needs a restart. FileResponse keeps the precompressed
siblings, ranges and conditional requests.
On a source checkout static/dist links to website/dist, and every
Vite build emptied website/dist and rewrote it in place, so for the
whole build a running gateway served no bundle and the stale-asset
watchdog read the gap as a vanished install.

A Vite plugin (website/scripts/publish-dist.mjs), registered last,
builds every mode except --watch into a per-build scratch sibling and,
in the last closeBundle hook and only once its post-order writeBundle
has run, renames the live tree aside and the new one over it. A failed
build, wherever it fails, leaves website/dist as it was and keeps its
own error. Scratch a killed build strands is swept at the next build;
a live tree that cannot be renamed (a mount point) is rewritten in
place, copying before it removes. The sw.js stamp and precompression
follow the resolved outDir.

Staging only ever re-points static/dist, which the dashboard now
resolves per request: at website/dist for a stock build that publishes
this way, otherwise at a fresh immutable copy in static/.dist.<id> (an
edition bundle, an older target revision that still builds in place,
which is moved to such a copy before it builds). On POSIX that is one
rename of a link over a link; on Windows the old junction is removed
first, which touches no tree. The link always carries an absolute
target, copies are matched to the served one by file identity rather
than path spelling, and nothing is swept while static/dist resolves
nowhere. A stage that retires the directory an older gateway resolved
at start (a real static/dist turned into the link, or the copy an
in-place target's gateway started on) says to restart that gateway, and
every copy carries its own "*" .gitignore, so a target whose .gitignore
predates the copies' names still reads clean. The tree-rename swap,
its rollback and its retry budgets are gone, and so is gateway start's
wait for a dangling link: outside an edition, a dangling link to this
checkout's website/dist is kept and serves the build once it lands. An
edition start stages its private copy off the event loop, waits at most
5 s for the staging lock, and otherwise serves what it found through the
link with a warning. A build counts as published only if it replaced
website/dist/index.html, compared by mtime_ns and inode rather than
against the wall clock.

make and make.ps1 stage through python -m kiro_crew.frontend stage in
build and wheel, after the backend install, so backend-bin needs no
Python for it. A stock checkout started before anything is built links
static/dist to its unbuilt website/dist, so the first build is served
without a restart.
The stage command refuses a directory that is not a checkout before
creating anything in it.

This removes the build-time asset gap that #13960's watchdog
stand-down otherwise has to cover.

Link-screen gate: _live_link_target, _point_static_dist_at and
_sweep_staged_locked are recorded, not held. They follow or replace
the operator's own link beside static/dist on purpose; the no-follow
hold would refuse that link, a sweep only ever unlinks a link it
finds, and a link planted between screen and use chooses only what is
served, which a planted link already does.
@bolichen97
bolichen97 force-pushed the fix/prestage-dev-dist branch from 7393d4b to 8c600e9 Compare October 4, 2026 08:20
@bolichen97

Copy link
Copy Markdown
Contributor Author

Rebased: main was red at b2060d6 in test/test_chat_handlers_composition_contract.py (fixed on main by #16695); 7393d4b -> 8c600e9 on 3f960a1, CI re-running.

@github-actions github-actions Bot added readiness: checking Automated validation is still running readiness: passed Eligible automated validation passed for the current revision and removed readiness: action required A blocking check or review needs attention readiness: checking Automated validation is still running labels Oct 4, 2026
@chenmingwei23
chenmingwei23 merged commit 2945573 into main Oct 4, 2026
102 checks passed
@chenmingwei23
chenmingwei23 deleted the fix/prestage-dev-dist branch October 4, 2026 09:30
@github-actions github-actions Bot removed the readiness: passed Eligible automated validation passed for the current revision label Oct 4, 2026
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.

fix(frontend): pre-stage static/dist before a build on a linked source checkout

2 participants