docs: bring CURRENT_STATE up to date with 0.4.3 and the scenario corpus work - #146
Merged
Conversation
…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
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #145.
CURRENT_STATE.mddrifted through two paths that bypass a normal feature PR: therelease 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.3release all landed without a record here.
Releases
0.4.3, published 2026-07-28.0.3.2, published 2026-07-14, which was never logged either.0.3.1since the v0.4.0release.
New section: External Contribution Pipeline
Covers the second
good-first-issuecompleting, the patch-not-minor changesetdecision (#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
expectedFailuresturned out to be unsatisfiable, and the station IDallocation 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 thegood-first-issuelabeland Develop-KIM completed it in #114, which shipped in
0.3.1. Both the mergedline 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:checkandpnpm lintpass. Every version number and date in thediff was checked against npm and the changelog rather than carried over from
memory. Documentation only, no changeset: the file is not in the package
fileslist.