Repository navigation
Conversation
… reading it - status labels the claim link as a connect link and shows it only while the site has no owner - status says its environment is the machine running the command, not the live app - the guard no longer warns about stale rules while next build prerenders - the summary's deploy step asks the person to say done instead of naming a CLI command - the widget reload line says which page to reload
|
🎯 Elite quality (90%) — Clarifies status and setup summary wording with thorough end-to-end status tests and a parallelized fetch. 📦 Medium 🟠 Elevated risk — the author's first change to this repository. ✅ Reviewed — approved by @daniloradovic. |
- status prints the claim link for connected sites too, labelled as the dashboard link - no link for a removed site or an endpoint only a committed file names - the environment note is left off a production label - status checks the claim state and site status in parallel - AGENT-INSTALL.md, GETTING-STARTED.md and README.md describe the link status prints - the deploy-step rule in AGENT-INSTALL.md names the exact lines to replace - the widget command uses the same reload wording as the summary - the NEXT_PHASE test stub is cleared in afterEach
Author
|
/review |
daniloradovic
approved these changes
Nov 19, 2026
This branch has not been deployed
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
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.
Closes ENG-4589
Several lines that Connect prints, and that an assistant passes on to the person, were unclear or wrong.
status.patchstackrc.jsonnames. Other commands already hide the link in that second case.localorsandboxlabel now says it is where the command runs, not the live app. Aproductionlabel is printed as it is.Guard during
next buildnext buildloads route modules to prerender them and refuses their network requests, so the guard printed "the guard's rules are not current". That guard serves no traffic, and the running server builds its own. The warning is now skipped whenNEXT_PHASEisphase-production-build. Next.js sets this before it starts the build workers, and the workers inherit it.Setup summary
nextalready answers "done" with those steps.widgetcommand uses the same wording.AGENT-INSTALL.mddescribes the summary andstatus, so it changes with them, as do thestatuslines inGETTING-STARTED.mdandREADME.md. That file is audited from the published tarball, so the hostile field run (node field-test/run.mjs --persona hostile --rounds 3) is still outstanding and has to run after the release that carries this.Tests:
npm testpasses (4758). New tests cover thestatusoutput (no owner, connected, unverifiable, removed, untrusted endpoint, production label), the quiet warning duringnext build, and the deploy step in the summary.