Skip to content

DeltaSignal on beta, from #757's review: docs and the toggle test - #758

Closed
adamjohnwright wants to merge 1 commit into
mainfrom
deltasignal-on-beta-docs
Closed

adamjohnwright wants to merge 1 commit into
mainfrom
deltasignal-on-beta-docs

Conversation

@adamjohnwright

Copy link
Copy Markdown
Contributor

This follows up #757 (DeltaSignal's Perturb button on beta) with the low findings from its review.

Changes

  • deploy/nginx/README.md no longer says DeltaSignal cannot work on beta. It says:
    • that /api/ is DeltaSignal's route;
    • that the service runs from DeltaSignal's own repository on the same host, published on loopback 8090;
    • that if the service stops, the button's calls fail, so /api/pathways is checked with the rest of beta.
  • e2e/deltasignal-toggle.spec.ts: its header no longer says /api is only the dev server's. The "offers it" case now runs for both development and beta.
  • environments.ts: the search-answer flag's comment said only development had it. Beta has had it for a while, and the comment now says so.

Noted from the review, not changed here:

  • The Perturb button shows on every pathway, but DeltaSignal's catalogue holds 11 pathways. On any other pathway the panel says no network has been generated yet. That is a product call.
  • /api/solve has no rate limit of its own beyond beta's site-wide one. The route was already reachable before Offer DeltaSignal's Perturb button on beta #757.

Spec: none.

🤖 Generated with Claude Code

…gle test checks it

The nginx README and the e2e toggle test's header no longer say
DeltaSignal cannot work on beta; the README says where its service runs
and that beta's checks cover it. The toggle test now checks the button
on beta as well as under the dev server. The search-answer flag's
comment, also stale, names beta too.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@adamjohnwright

Copy link
Copy Markdown
Contributor Author

Replaced by the next PR, which keeps the toggle test's recorded name.

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.

1 participant