fix(cli): name the record a 404 could not find

[Goran Gajic (gorangajic)]

qawolf trigger get --trigger-id trg-1 on a trigger that does not exist answered "QA Wolf API could not find trigger.get (HTTP 404)" — the name of the endpoint, which reads as though the endpoint itself were gone. Issues, flows, agent sessions and files all said the same kind of thing.

Relates to WIZ-12150. Stacked on #1619, which fixed the same wording for runners, runs and environments; review that one first.

Overview of Changes

A 404 on one of these now names what was missing and the id it was asked for: QA Wolf has no trigger trg-1 (HTTP 404). A request that names no such record — a listing, a search — says it matched nothing rather than that it could not be found.

Where a record is looked up inside an environment, the record wins. Missing a trigger is not an environment problem, which is the thing this family of changes is about.

Testing

bun run typecheck
bun run lint
bun run format:check
bun run knip
bun run test
bun run build

Unit tests cover each named record, the case where a request scopes an environment as well, and the ids a route only takes as arguments (a workspace, a timezone) staying out of the message. Also run against a local stub answering 404 to check the real command output.

Checklist

• Changes follow the code style of this project
• Self-review completed
• Tests added/updated (or not applicable)
• No breaking changes (or described below)

🤖 Generated with Claude Code

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Essentials

Run ID: 2aedb83e-c3b9-40d2-955c-220bdfe9554e

📥 Commits

Reviewing files that changed from the base of the PR and between 8cf9c6d and 64c031b.

📒 Files selected for processing (7)

• .changeset/name-the-missing-record.md
• src/core/messages/authErrors.ts
• src/core/publicApi/notFoundSubject.test.ts
• src/core/publicApi/notFoundSubject.ts
• src/shell/platform/callPublicApi.notFound.test.ts
• src/shell/platform/describeNotFound.test.ts
• src/shell/platform/describeNotFound.ts

Included review availability: Your plan provides up to 8 included reviews per hour; 6 remain after this review.

---

Walkthrough

The change adds record-specific 404 subjects for sessions, triggers, issues, flows, and files. Record IDs take precedence over environment IDs. Requests without a recognized record or environment subject report an unmatched request. Shell formatting now uses the record noun and ID. Tests cover subject resolution and 404 output.

Priority: ⬇️ Low

Estimated code review effort: 2 (Simple) | ~10 minutes

Change: Bug fix

Suggested reviewers: theonly1me

Sequence Diagram(s)

sequenceDiagram
  participant PublicAPI
  participant notFoundSubject
  participant describeNotFound
  PublicAPI->>notFoundSubject: resolve record or environment subject
  notFoundSubject-->>PublicAPI: return 404 subject
  PublicAPI->>describeNotFound: provide not-found subject
  describeNotFound-->>PublicAPI: return record-specific or unmatched-request message

Loading

Merge Risk: ⚪ Minimal · up to 64c03

The CLI now provides clearer 404 messages for missing records and unmatched requests without identified compatibility or runtime risk. The change is ready to merge.

🚥 Pre-merge checks | ✅ 4

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title follows the Conventional Commits format, uses the allowed fix(cli) scope, uses imperative mood, describes the record-specific 404 change, and is under 72 characters.
Description check	✅ Passed	The description includes the required overview, testing, and checklist sections. It explains the record-specific 404 behavior, related issue, test coverage, validation commands, and confirms checklist…
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

---

_{Comment @coderabbitai help to get the list of available commands.}