staysfixed 0.3.1 → 0.6.0

package/CHANGELOG.md

@@ -4,9 +4,162 @@ All notable changes to this project are recorded here. The format follows
 [Keep a Changelog](https://keepachangelog.com/en/1.1.0/), and the version
 numbers follow [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
-## [Unreleased]
+## [0.6.0] — 2026-08-30
 
-Nothing yet.
+The second sweep for silences, done the same way as the first: read all of
+`src/v2` looking for anything that can drop something and then report nothing
+found. Five more were there, and two of them were in the safety machinery
+itself — the gate that decides what an agent may never wave through, and the
+proof that decides whether a change explains a break.
+
+Every fix below has a test that fails against yesterday's code and passes
+against today's. That was checked by putting the old behaviour back, one line at
+a time, in a copy of the repository, and watching each test go red.
+
+### Fixed — silences, second sweep
+
+- **Only the first 80 differences of a finding were read when deciding whether it
+  was one of the five things nobody may wave through.** A cluster can hold
+  hundreds of addresses; a refund sitting at address 150 of 300 was classified
+  ordinary, which means an agent could waive it and it would never reach a
+  person. Every difference is read now. A cap on the one gate that cannot have
+  one is not a performance decision, it is a hole.
+- **The causal proof re-checked five addresses and then spoke for all of them.**
+  A finding of three hundred where the first five went away came back "caused by
+  that change" — a machine-checked reason for an agent to close a break it had
+  only half explained. It re-checks every address now, and when a change explains
+  part of a finding and not the rest it says exactly that, with both numbers. It
+  costs nothing: the journeys were already re-walked and each extra address is one
+  lookup.
+- **A wobble big enough to swallow the comparison was still subtracted, and the
+  run came back clean.** If the second run of the new build falls over, or the
+  product writes hash-named files, or stamps a fresh id on every line, most of its
+  addresses are unsteady, nearly every difference is dropped before anything is
+  compared, and the verdict reads "nothing that already worked has changed". A
+  build that disagrees with itself about more than half of its own addresses now
+  gets **no verdict**: the summary opens with `NO ANSWER FROM THIS RUN`, the
+  reason is a named hole in the coverage, and `ok` is false. No number here
+  decides whether any difference is real — it decides only whether the run has
+  earned the word clean.
+- **Two facts written at one address lost one of them, silently.** Every index in
+  the engine keeps the first observation at a path, so a second one is never
+  compared with anything and a door that broke behind it is invisible. The
+  detector for this was written on the first day of v2 and nothing ever called it.
+  Every walk is checked now and each clash is named — which address, and what the
+  ignored answer was. Identical repeats are not reported, because they hide
+  nothing.
+- **The route reader skipped a folder it could not open, and every route behind
+  it, without a word.** This is the same bug as the one fixed yesterday in the
+  file walk, in a second function that the first fix did not touch. It names the
+  folder now.
+
+### Added
+
+- A twelfth case in the self-check corpus, and a third kind of expectation with
+  it: a product so unsteady that the comparison is thrown away before it happens,
+  where the only honest answer is that the run says nothing. Confirmed to fail
+  against 0.5.0 and pass against this. Measured after the change: twelve of
+  twelve, three times running, with the project's own suite in parallel and the
+  machine's load average between 208 and 343.
+- Six more tests in `test/v2/silences.test.js`, one per fix above, each confirmed
+  red against the previous code.
+
+### Changed
+
+- `readFileRoutes(root)` returns `{ doors, problems }` rather than an array. The
+  problems are folders it could not open, and they are reported as missing
+  coverage by every caller.
+
+### Known, and written down rather than fixed
+
+- What a normalisation rule rubbed out is not itemised per run. The receipt
+  exists in the code and nothing calls it. The rules are in your repository and
+  the capture is stamped with which set it used, so a comparison across a rule
+  change is announced — but a broad rule is still how you go blind on purpose.
+- Ranking reads up to 4,000 source files of up to 400KB. Past that a finding is
+  still reported and still counted; it may just not sort where it deserves to.
+  Nothing is dropped for being far from the change.
+
+## [0.5.0] — 2026-08-30
+
+The release about the one way this tool can be catastrophically wrong: reporting
+nothing while something is broken. Five separate places could do that, and one of
+them could do it permanently.
+
+### Fixed — silences
+
+Each of these produced a clean-looking run while something was invisible.
+
+- **A `git diff` too big to read was treated as no diff at all**, so a large
+  uncommitted change was fingerprinted as a clean checkout of the commit it sat
+  on. If that commit was the reference, the check was comparing the build against
+  itself, and a comparison of a build with itself can only ever come back clean.
+  The diff is now streamed into a hash with no ceiling, and a git command that
+  fails is refused loudly rather than read as "nothing has changed".
+- **A folder with no git in it** gave every build the same identity, with the same
+  consequence, quietly and for ever. It is now refused, with a sentence saying
+  why.
+- **The two ends of a huge output were kept with only a rough size**, so a break
+  in the middle that was thrown away left a byte-identical record. The exact byte
+  count is kept now, and a truncated value is reported as missing coverage rather
+  than passed over.
+- **An adapter that threw while listing what it would walk had its journeys
+  dropped in silence** — a whole surface disappearing from a run whose verdict
+  then read "nothing that worked has changed". It is recorded as a hole, by name.
+- **A folder the source reader could not open was skipped without a word**, taking
+  every door behind it. It is named now, along with any file still too big to read.
+- **The normalisation-rule stamp on a stored capture was written and never read.**
+  Comparing a record tidied up under one set of rules against a run tidied up
+  under another produces differences that are about the rules; the run now says so.
+
+### Changed — how long something took is recorded and never compared
+
+A stopwatch on a shared machine measures how busy the machine is at least as much
+as it measures the product. Measured on the corpus's own fixture: thirty runs of
+the same one-line program on an idle Mac took 48ms to 96ms, against a bucket
+boundary at 100ms — four milliseconds of headroom, so any load at all crossed it.
+That is what made the self-check come back "1 of 9 wrong" one busy evening and
+then pass five times in a row on a quiet machine.
+
+Durations are still measured and still shown, in the sentence beside the address,
+where a person can read them. They are no longer differenced, on any platform.
+**Stays Fixed will not tell you your product got slower.** A build that hangs is
+still caught, because it is stopped for taking too long and how it finished is
+compared exactly, and every counter that comes from the product rather than from
+the clock is compared exactly as before.
+
+### Added
+
+- **Two more cases in the self-check corpus**, eleven in total: a break buried in
+  the middle of an output too big to store, and a build ten times slower that must
+  stay silent. Both were confirmed to fail against the previous code and pass
+  against this one.
+- **The corpus re-runs a case before accusing the engine.** Fail twice and it is a
+  real failure. Behave the second time and it is reported as *could not tell* —
+  not a pass, not a failure, exit code 2 — with the machine's load beside it.
+  Measured after the change: eleven of eleven, three times running, with the
+  project's own test suite in parallel and load average between 227 and 334.
+- `test/v2/silences.test.js`, holding each of the above shut.
+
+## [0.4.0] — 2026-08-30
+
+The difference engine, published. Seven observation channels flattened into one
+address space; the new build run twice so the product's own wobble is measured
+and subtracted rather than guessed at; differences clustered, ranked by distance
+from the changed code, and their cause proven by reverting the suspect change and
+running again. The reference is cut by saying ship, and an agent may waive within
+four gates but can never decide what "working" means. Adapters for processes,
+HTTP, source reading, the web, Electron, Android, iOS and Windows, and a
+self-check corpus of deliberately broken builds.
+
+## [0.3.0] — 2026-08-29
+
+Checks tick off live as they run, and guards show what they assert.
+
+## [0.2.0] — 2026-08-29
+
+Pictures you can look at, motion, and a report that says what was checked rather
+than only how long it took.
 
 ## [0.1.0] — 2026-08-29
 
@@ -57,5 +210,8 @@ not been used by many people yet.
 - No phone or tablet simulators.
 - No hosted service, no dashboard, no accounts.
 
-[Unreleased]: https://github.com/asadev/staysfixed/compare/v0.1.0...HEAD
+[0.5.0]: https://github.com/asadev/staysfixed/compare/v0.4.0...v0.5.0
+[0.4.0]: https://github.com/asadev/staysfixed/compare/v0.3.1...v0.4.0
+[0.3.0]: https://github.com/asadev/staysfixed/compare/v0.2.3...v0.3.0
+[0.2.0]: https://github.com/asadev/staysfixed/compare/v0.1.1...v0.2.0
 [0.1.0]: https://github.com/asadev/staysfixed/releases/tag/v0.1.0