Skip to content

docs: Match README, TELEMETRY, and AGENTS to the code of 0.3.0 - #59

Merged
dcramer merged 2 commits into
fix/tunnel-idlefrom
docs/cleanup
Nov 5, 2026
Merged

dcramer merged 2 commits into
fix/tunnel-idlefrom
docs/cleanup

Conversation

@sentry-junior

@sentry-junior sentry-junior Bot commented Nov 5, 2026

Copy link
Copy Markdown
Contributor

Stacked on the tunnel idle PR (fix/tunnel-idle). Merge that first.

Every path, limit, status code, metric, attribute and deploy step was checked against the code:

  • action url input, rule-name limits, the 16 Ki secret length, and the full list of credential names
  • what a recording keeps, the 500-miss cap, http.request.method on spans, and the 10 s PROXY header limit
  • POST /__roach/runs: 201/400/401/413/429, including 400 for a body that is not JSON; 404 for a wrong run token
  • the deploy section is now the steady-state order: deploy the image, apply the config secret with -target, reset the VM, then the full apply. The warning that a client can send its own PROXY header between step 3 and step 4 is kept.
  • CI runs the tests only with coverage
  • TELEMETRY.md: roach.written is also on roach.run.end; a call without a request model has gen_ai.response.model, so the cost query groups by both
  • the test list, and AGENTS.md now says the Image workflow runs terraform validate
  • removed the cache list that TELEMETRY.md already has, and a repeated miss rule

server.ts and service.ts change only in comments. An independent review checked each claim against the code. pnpm check passes.

via @dcramer.

--

View Session [Sentry]

sentry-junior Bot and others added 2 commits November 5, 2026 19:19
Check each path, limit, metric, attribute, and section against the code
after the service split (#55) and the client tidy (#57):

- README: name the `url` input of the action, the rule name limits, the
  length limit of run secrets, the full list of credential header names,
  what a recording keeps (method, redacted URL, `content-type` and
  `location`), the 500 misses that the stats keep, `http.request.method`
  on `roach.request` and `roach.upstream`, the 10 s limit of a PROXY
  header, the 201/400/401/429 answers of `POST /__roach/runs`, and the
  404 for a wrong run token.
- README: the service log gets the class, the code, and the GCS status of
  an error.
- README: shorten the one-time PROXY protocol rollout to the steady-state
  order: deploy the image, apply the config secret with `-target`, reset
  the VM, apply the rest.
- README: drop the cache list of "Sentry" that TELEMETRY.md repeats, and
  the repeat of the miss rule of "Misses" in "Service". Move the
  changing-keys query to TELEMETRY.md.
- README: list redaction.test.ts and packages/roach/tests/package.test.ts,
  and say that CI also runs coverage and packs the package.
- TELEMETRY: name server.ts as a source, add `roach.recordings`,
  `roach.written`, and `http.request.method`, and the log fields.
- AGENTS: the Image workflow runs `terraform validate`, not CI.
- service.ts and server.ts comments: the key worker is a process, and
  the keep-alive time is 5 s and 1 s more.

Only docs and comments change. The tunnel limits bullet stays as on
main, because the fix of the tunnel idle limit changes it.

Co-Authored-By: David Cramer <23610+dcramer@users.noreply.github.com>
CI runs the tests only with coverage. POST /runs also answers 400 for a
body that is not JSON and 413 over 1 MiB. Put back the warning about a
false PROXY header from step 3 to step 4. roach.written is also on
roach.run.end, and a call without a request model has
gen_ai.response.model, so the cost query groups by both.

Co-Authored-By: David Cramer <23610+dcramer@users.noreply.github.com>
@sentry-junior
sentry-junior Bot added this pull request to stack #60 November 5, 2026 19:30
@dcramer
dcramer marked this pull request as ready for review November 5, 2026 19:33
@dcramer
dcramer merged commit f36d3a5 into main Nov 5, 2026
17 checks passed
@dcramer
dcramer deleted the docs/cleanup branch November 5, 2026 19:36
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