Add boundary-preserving request path source (#358)

Tell agents not to rebuild setup by hand on a builder that blocks the…

… CLI (#357)

On a hosted builder that refuses the CLI, an agent can install the
package, read its source, and write its own build plugin that sets the
live-site flag on every build. The builder serves that build at its
preview address too, so the widget reads the preview as the live site
and hides the claim panel from the owner.

Say plainly that build plugins, a hand-set marker and direct API calls
are routing around the block, and that the Connector-only choice is the
tag alone.

Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

[NO-TICKET] Keep the egress category test off the network (#356)

The egress case resolved a made-up hostname through real DNS before its
hostname rule matched, so a slow resolver on the runner timed the test out
and failed the Publish workflow. The case now sets screenDns: false, as the
other hostname-rule egress tests do.

Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

[NO-TICKET] Stop map --upload crashing the build on a map with an und…

…efined field (#355)

The input-map identity refused any property whose value is undefined, while
the upload's JSON.stringify simply omits it. The identity now omits it too, so
the digest names the document the server receives. An identity failure no
longer fails the build: the map uploads unbound, as detect-only.

Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

test(config): isolate hosting signals from the release runner (#352)

Complete setup with map upload and live rule retrieval (#350)

* feat(setup): upload the map and retrieve rules in one command

* fix(setup): run build hooks across package managers

* test(setup): initialize the offline Yarn fixture on CI

[NO-TICKET] Keep the production marker on production builds, and stam…

…p sandbox builds (#344)

* Keep the production marker on production builds and off everything else

A committed "environment": "sandbox" in .patchstackrc.json no longer
outranks a build its platform identifies as production. The file reaches
production with the rest of the source, so it used to ship the live site
without its marker, which shows visitors the owner panel. scan and
mark-build now print a warning naming the file. PATCHSTACK_ENVIRONMENT
still wins outright.

mark-build also removes, from non-production output, an inline script
whose only content sets the marker globals, so a marker pasted by hand
no longer survives a sandbox rebuild. Scripts that do anything else are
left alone.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

* Stamp sandbox builds as sandbox

mark-build now writes window.__PATCHSTACK_ENV__="sandbox" into a sandbox
build where a production build gets the production marker. The widget
treats a page with neither as the live site, so this is what lets a
preview on a host it cannot recognise by name keep the owner's panel.
A local build still gets nothing. Each build replaces the other's stamp.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

Improve deployment environment detection and local CLI setup (#343)

Compose Next.js middleware and App Router protection (#340)

* feat(protect): compose Next middleware and App Router protection

* test: expand Next.js integration coverage and reject proxy conflicts

Compose Next.js middleware and App Router protection (#340)

* feat(protect): compose Next middleware and App Router protection

* test: expand Next.js integration coverage and reject proxy conflicts