docs(agents): note Studio stale-dist trap under Functional Testing#1042
Merged
docs(agents): note Studio stale-dist trap under Functional Testing#1042
Conversation
Running `bun apps/cli/src/cli.ts studio` only live-reloads the CLI and backend routes. The Studio web UI is served as a static bundle from `apps/studio/dist/`, which is build output and does not recompile on source changes. Without a manual `bun run build` in `apps/studio`, `agentv studio` silently serves whatever JS/CSS was last built — which may be from a different branch, before the merge you just pulled, or simply stale. This bit the post-merge UAT on #1040: the TagsEditor component was correctly in the source but not in the dist, so the driven-browser session kept rendering an older Compare tab and looked like a feature regression. Cost ~15 minutes of confusion to diagnose. Adds a paragraph under the existing "Functional Testing (CLI)" section so the next agent (or human) knows to rebuild the Studio dist before screenshotting or driving `agent-browser` against Studio.
Deploying agentv with
|
| Latest commit: |
b3faf28
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://72ebc01b.agentv.pages.dev |
| Branch Preview URL: | https://docs-studio-stale-dist.agentv.pages.dev |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Why
During the post-merge UAT on #1040, my first attempt to verify the new `TagsEditor` rendered an older version of the Compare tab entirely — no mode toggle, wrong cell styling, no `PassRatePill`. Spent time convincing myself the merge had broken something before realizing `apps/studio/dist/` was from 2026-04-09 (before the work) and my source-mode invocation never touched it. The component code was correct all along; the bundle just hadn't been rebuilt.
This is the kind of thing that's easy to miss on the first run and obvious in hindsight. One paragraph in `AGENTS.md` prevents the next agent / contributor from the same confusion.
Test plan
Related
🤖 Generated with Claude Code