You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
docs: unify BugBot audit fixes and stop AGENTS.md tree drift (#1050)
## Summary
Consolidates the four recurring Cursor BugBot **"docs:"** audit PRs into
a single set of verified fixes, and removes the *root cause* of the
repeated audits.
Supersedes and closes:
- #972 — comprehensive documentation gap audit report
- #946 — fix documentation gaps identified by automated audit
- #1043 — fix stale architecture tree and phantom `--cause` flag
- #909 — fix documentation gaps identified in comprehensive audit
## Root cause: AGENTS.md tree drift
Every one of those PRs re-fixed the **hand-maintained architecture tree
in `AGENTS.md`**. That tree drifts whenever a command or API module is
added, so the weekly audit keeps re-filing it.
The repo already generates an always-current project-structure tree into
`docs/src/content/docs/contributing.md` via
`script/generate-docs-sections.ts`. This PR **removes the duplicated
tree from `AGENTS.md`** and replaces it with a concise pointer to the
generated tree (plus `ls src/commands/` / `sentry --help`). This
eliminates the recurring audit target permanently.
## Verified fixes harvested from the audits
Each change was verified against current `main` source, not blindly
cherry-picked:
- **`issue.md`** — removed the phantom `sentry issue plan --cause 0`
example. The `--cause` flag does not exist in `plan.ts`; `plan`
automatically runs root-cause analysis (`ensureRootCauseAnalysis`) when
needed. Requirements text updated accordingly. *(from #1043)*
- **`src/lib/env-registry.ts`** — registered `SENTRY_INIT_TUI` (read at
`src/lib/init/ui/factory.ts`) so it surfaces in the generated
`configuration.md`. *(from #946)*
- **`cli.md`** — documented `sentry cli defaults headers` and `sentry
cli defaults ca-cert` (both implemented in `defaults.ts`). *(from #946)*
- **`self-hosted.md`** — documented `auth login --url` as the
recommended, trust-anchoring login method, and added a **TLS / Corporate
Proxies** section (`NODE_EXTRA_CA_CERTS` + `cli defaults
ca-cert`/`headers`). *(from #909)*
- **`getting-started.mdx` / `README.md`** — noted the **Node.js 22.15+**
requirement for npm/pnpm/yarn packages (matches `package.json` engines);
added `yarn` install + `pnpm dlx`/`yarn dlx`/`bunx` run options to the
README. *(from #909/#946)*
Regenerated skill references (`references/issue.md`,
`references/cli.md`) via `pnpm run generate:docs`.
## Discarded
- The throwaway `DOCUMENTATION_GAPS.md` / `docs/DOCUMENTATION_GAPS.md` /
`DOCUMENTATION_GAP_REPORT.md` audit artifacts are **not** committed, and
are now gitignored so future bot audits don't accidentally commit them.
- Skipped items already landed on `main` since the PRs opened (dashboard
`revisions`/`restore` examples, `configuration.md` cross-refs) and the
unverified Cursor `~/.agents` claim that #972 itself flagged as
inaccurate.
## Verification
- `pnpm run typecheck` ✅
- `pnpm run lint` ✅ (only pre-existing unrelated warning in
`formatters/local.ts`)
- `pnpm run check:fragments` ✅ (all 22 fragments valid)
- `pnpm exec vitest run test/lib test/commands test/types` ✅ (5529
passed, 9 skipped)
- Confirmed `SENTRY_INIT_TUI` appears in generated `configuration.md`.
The `--url` flag is the most secure way to authenticate with a new host — it is the only way to register a trust anchor for that host. Without it, the CLI refuses to log in to an instance URL that was picked up from an untrusted channel (e.g. a `.sentryclirc` file), protecting you from credential leaks and OAuth phishing.
50
+
:::
51
+
42
52
### With an API Token
43
53
44
54
If your instance is on an older version or you prefer not to create an OAuth application, you can use an API token instead:
@@ -65,6 +75,26 @@ sentry org list
65
75
66
76
If you pass a self-hosted Sentry URL as a command argument (e.g., an issue or event URL), the CLI detects the instance automatically.
67
77
78
+
## TLS / Corporate Proxies
79
+
80
+
If your self-hosted instance sits behind a private CA certificate (common with corporate TLS-intercepting proxies like Zscaler or Netskope), point `NODE_EXTRA_CA_CERTS` at your CA bundle:
"Control the TUI (terminal user interface) for `sentry init`. Set to `0` to disable the interactive TUI and use plain text logging output instead. Useful in CI/CD pipelines or environments without full terminal support.",
0 commit comments