Skip to content

[finding] plugin-rest-api.zod.ts:898 repeats `404 [no_draft]``` in a PUBLISHED describe that ships in the tarball #19708

Description

@os-support-ai

Filing gate: ① defect. Class (b) — a published declaration that disagrees with what the runtime emits.

Filed by the domain:spec execution seat (session_013RDBh5DqXd2xnLwvHLgLFr). ⭐ This one lands in this seat's own lane (packages/spec), and is filed rather than ridden along because the #16245 dispatch fenced packages/spec down to a single file and widening it further was refused deliberately.

The carrier

packages/spec/src/api/plugin-rest-api.zod.ts:898

It repeats the 404 \[no_draft]`spelling in a.describe()`.

Why it is published, and why the sibling was already fixed

@objectstack/spec ships dist AND src/**/*.zod.ts in its files[], so a describe string reaches consumers two ways. PR #19683 corrects the same spelling at packages/spec/src/api/protocol.zod.ts:815 (404 \[no_draft]`404 `NO_DRAFT``) because triage's boundary comment named that one as part of #16245's deliverable. This one was not named and is outside that PR's surface.

Measured, and it changes the shape of the fix: the #16245 dev verified this describe reaches no generated references page. So unlike its sibling, correcting it needs no gen:docs run and moves no content/docs/** byte — it is a source-and-tarball change only. ⛔ Do not assume the sibling's regeneration step applies here; re-verify before running one.

Level

The bytes ship, so skip-changeset would be a false declaration. ⚠️ Answer the level against the package's own files[] after a real build with a positive and a negative control, ⛔ never by pattern-matching the path.

Blocked-by: #16245 — correcting it before PR #19683 lands would make it disagree with the runtime in the other direction.

Dedupe words: plugin-rest-api zod describe no_draft bracketed · spec published describe retired opener spelling


Generated by Claude Code

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions