tachyon-sentrylisted

# Tachyon Sentry Use the local `tachyon` CLI for Sentry issue operations. ## Rules - Use `tachyon ops sentry issues ...`; do not bypass Tachyon with direct Sentry API calls. - Pass an explicit `--tenant-id` and `--profile` when known. Do not assume the active profile has the correct tenant. - Add `--json` so results can be parsed and summarized accurately. - Treat access tokens, auth headers, secret references, DSNs, and credential refresh output as secrets. Never echo them. - Default to read-only `list` and `view` operations. - Run `resolve` or `assign` only when the user explicitly requests the mutation and the issue ID is unambiguous. For assignment, require the exact Sentry user ID, username, or email. - Never use a host token to bypass a tenant-scoped write failure. ## Orientation Confirm the installed CLI and available subcommands: ```bash command -v tachyon tachyon --version tachyon ops sentry issues --help ``` If authentication or tenant selection is unclear, inspect profiles without exposing credentials: ```bash tachyon auth list ``` ## List Issues List unresolved issues for a project: ```bash tachyon ops sentry issues list \ --project <project_slug_or_id> \ --query 'is:unresolved' \ --limit 20 \ --tenant-id <tenant_id_or_alias> \ --profile <profile> \ --json ``` Use the Sentry project slug directly with `--project`; do not rewrite it into the search query. Report the relevant issue ID or short ID, title, status, count, last-seen time, and pe