Skip to content

docs(spec): add the api-extractor state-of-the-art spec - #14

Closed
systemfsoftware-maker wants to merge 1 commit into
mainfrom
docs/api-extractor-sota-spec
Closed

systemfsoftware-maker wants to merge 1 commit into
mainfrom
docs/api-extractor-sota-spec

Conversation

@systemfsoftware-maker

Copy link
Copy Markdown
Contributor

What

Adds the scrubbed spec for bringing @systemfsoftware/api-extractor to the state of the art and making the judge-facing change report the first deliverable:

  • requirements.md — the outcome, the research basis and the keep/replace/delete decisions, the requirements and the acceptance examples.
  • design.md — the model v3/v4, source index, report and change report, importer index, CLI, CI, changeset check, performance and the delivery sequence.
  • tasks.md — eleven ordered units, one PR each, with the judge-facing change report first.

Scrub

No private repository, package or product names, no local paths and no people. The three documents pass the private-reference scrub with 0 matches.

Order

The implementation starts with the review and merge of PR #7, then the model, report, change report and reusable consumer workflow. The corpus job, changeset check, benchmark and TypeScript 7.1 adapter follow.

Notes

The commit is unsigned because the authoring environment does not hold the configured GPG secret key; the repository's main ruleset does not require signed commits.

🤖 Generated with Claude Code

Requirements, design and tasks for the Effect-aware public-API report tool: the judge-facing change report first, then the model extensions, corpus job, changeset check, benchmark and TypeScript 7.1 adapter.

Co-Authored-By: Claude Code <noreply@anthropic.com>
@ryanleecode

Copy link
Copy Markdown
Contributor

Closed: Kiro specs are planning artifacts and stay out of the repository. The work lands as the unit PRs the spec plans.

@ryanleecode
ryanleecode deleted the docs/api-extractor-sota-spec branch October 24, 2026 06:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants