Skip to content

docs: bring CURRENT_STATE up to date with 0.4.3 and the scenario corpus work - #146

Merged
sepehr-safari merged 1 commit into
mainfrom
docs/current-state-0-4-3
Jul 28, 2026
Merged

docs: bring CURRENT_STATE up to date with 0.4.3 and the scenario corpus work#146
sepehr-safari merged 1 commit into
mainfrom
docs/current-state-0-4-3

Conversation

@sepehr-safari

Copy link
Copy Markdown
Member

Closes #145.

CURRENT_STATE.md drifted through two paths that bypass a normal feature PR: the
release PR is created by the changesets action and never touches this file, and
issue-only work leaves no PR at all. #137 through #140, #144 and the 0.4.3
release all landed without a record here.

Releases

  • Records 0.4.3, published 2026-07-28.
  • Records 0.3.2, published 2026-07-14, which was never logged either.
  • Corrects the package status table, which had read 0.3.1 since the v0.4.0
    release.

New section: External Contribution Pipeline

Covers the second good-first-issue completing, the patch-not-minor changeset
decision (#142, #143), the detection-rule coverage audit that found 3 of 16 rules
with no scenario, the three issues opened to close that gap, the retarget of #108
after its expectedFailures turned out to be unsatisfiable, and the station ID
allocation across in-flight issues.

It closes with the arithmetic to the v1.0 target: 16 scenarios today, and #108,
#137, #138 and #139 take it to 20, at which point every detection rule is
covered.

A correction

#135 described PR #133 as the first external contribution to a
good-first-issue. It is the second. #105 carried the good-first-issue label
and Develop-KIM completed it in #114, which shipped in 0.3.1. Both the merged
line and the new section now say second.

Pending decisions

"None currently. All design decisions resolved in ADRs" is no longer true. #144
carries four open questions, so they are named here with the note that the rule
most likely wants the per-connector model arriving in v0.5.0.

Verification

pnpm format:check and pnpm lint pass. Every version number and date in the
diff was checked against npm and the changelog rather than carried over from
memory. Documentation only, no changeset: the file is not in the package files
list.

…us work

The living document drifted through two paths that bypass a normal feature PR:
the release PR is created by the changesets action and never touches this file,
and issue-only work leaves no PR at all.

Records the 0.4.3 release, and the 0.3.2 release from 2026-07-14 that was never
logged either. Corrects the package status table, which had said 0.3.1 since
the v0.4.0 release.

Adds a section covering the external contribution pipeline: the second
good-first-issue completing, the patch-not-minor changeset decision, the
detection-rule coverage audit that found 3 of 16 rules with no scenario, the
three issues opened to close it, the retarget of #108, and the station ID
allocation.

Also corrects an overclaim introduced in #135. PR #133 was described as the
first external contribution to a good-first-issue. It is the second: #105 was
labelled good-first-issue and Develop-KIM completed it in #114, shipped in
0.3.1.

Notes the open design questions on #144 under pending decisions, which had
claimed nothing was outstanding.

Closes #145
@sepehr-safari sepehr-safari added type:docs Documentation improvements package:repo Repository-level changes labels Jul 28, 2026
@sepehr-safari
sepehr-safari merged commit 450b5be into main Jul 28, 2026
2 checks passed
@sepehr-safari
sepehr-safari deleted the docs/current-state-0-4-3 branch July 28, 2026 16:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

package:repo Repository-level changes type:docs Documentation improvements

Projects

None yet

Development

Successfully merging this pull request may close these issues.

docs: bring CURRENT_STATE up to date with 0.4.3 and the scenario corpus work

1 participant