Files

T

Tianyi Cui 25dcd7293c docs: purge chain-of-thought leakage from prose

Delete design-session citations (decision/audit/plan ordinals, stack
positions), change narration, review choreography, and reviewer-addressed
justification from comments, JSDoc, docs, READMEs, Agent Notes, tests, and
generator templates; restate every affected fact as current-state contract
prose. Fix generated docs at their sources and regenerate the catalogs and
cordis-surface regions; re-paste type-equiv blocks; update every bilingual
counterpart and re-record the pairs. Record the citation rule in the
committed-artifact-citations Agent Note.

2026-08-09 21:10:59 +08:00

1.8 KiB

Raw Blame History

Agent Note: API extractor reports

Status: proposed

English | 中文

The doc-block-typechecking and event-taxonomy parts shipped (doc-sync enforcement); this remaining API-report part is deferred as a standalone proposal.

Problem

Public API changes are invisible — nothing makes "this commit changed the public surface" an explicit, reviewable fact. A reviewer reading a diff can miss that an exported type gained a field or a method signature shifted.

Proposal

api-extractor (or tsc --emitDeclarationOnly + a normalized public-surface dump) producing a checked-in etc/<pkg>.api.md per package; CI fails if regeneration differs. Every public-API change becomes a diff line a reviewer (or review agent) must see.

Alternatives considered

tsc --emitDeclarationOnly plus a normalized public-surface dump — the lighter mechanism if api-extractor proves too heavy; either satisfies the checked-in, diffable report shape the proposal needs.

Acceptance criteria

Every package has a checked-in etc/<pkg>.api.md; CI fails when regeneration differs from the committed report.
A public-API change (a new export, a widened field, a shifted signature) is visible as a report diff line in review.

Risks

The dependency is heavy and finicky — the reason this was deferred — and the report format churns with compiler upgrades, adding a maintenance surface that buys little while the packages stay unpublished.

Why deferred

Deferred when doc-sync landed: low value for an internal monorepo where reviewers already see the source diff, and a heavy, finicky dependency. Revisit if the packages are ever published externally — at that point a stable, diffable public surface earns its keep.

1.8 KiB Raw Blame History