Skip to content

History / Component Status

Revisions

  • Legacy bridge removed; status note

    @YadeWira YadeWira committed Sep 3, 2026
  • param15 pre-post-filter stream fix (65a00a5); v0.6.0-pre pending list corrected

    @YadeWira YadeWira committed Sep 2, 2026
  • Image model ported: decr_param 3 = NzImageModel, wide corpus 1240/1240; two new -co/-cO open items

    @YadeWira YadeWira committed Sep 2, 2026
  • docs: BMP image model scoped

    @YadeWira YadeWira committed Sep 2, 2026
  • docs: -cd/-cD cluster fully closed; 1233/1240

    @YadeWira YadeWira committed Sep 2, 2026
  • docs: -cd/-cD cluster resolved into three causes, two closed

    @YadeWira YadeWira committed Sep 2, 2026
  • docs: the -cO ring-lifetime bugs, and the two decode gaps left

    @YadeWira YadeWira committed Sep 2, 2026
  • docs: the last failure is ours, not NanoZip's; repro shrunk and two hypotheses refuted

    @YadeWira YadeWira committed Sep 2, 2026
  • docs: -cc declined by default for every user; the suites could not see it

    @YadeWira YadeWira committed Sep 2, 2026
  • docs: fuzzing corrupt input found an OOB write, a crash and a DoS

    @YadeWira YadeWira committed Sep 2, 2026
  • docs: four decode gaps closed; one failure left

    @YadeWira YadeWira committed Sep 2, 2026
  • docs: multi-file metadata records, and what closing them fixed

    @YadeWira YadeWira committed Sep 2, 2026
  • docs: audited inventory of what the decode still misses Measured rather than recited. Headline: -co/-cO MULTI-FILE archives decode to wrong bytes and are written out without being declined, because multi-file metadata parsing yields no per-entry checksum and the per-entry verification is guarded by exactly that flag. Both test suites use single-file archives only, so neither sees it. Also records the clean declines (-p<n>, a large multi-file archive), the metadata still not extracted, what is unimplemented on purpose, what is latent and therefore unverifiable, and the coverage gaps behind the suite numbers.

    @YadeWira YadeWira committed Sep 2, 2026
  • docs: retract two conclusions about the last failure; it is not inherited state Classifying every differing word shows the "580 bytes of model divergence at block-2 entry" is almost entirely pointer fields baked into the captured cold blob plus a per-slot statistic counter. The state effectively matches, so the divergence is introduced inside block 2 and the next step is a chunk-boundary comparison -- which needs the real chunk-loop address, since the real engine does not copy per chunk. Adds two method notes: classify differing words before reading a memory diff as drift, and a data watchpoint only fires when the value changes.

    @YadeWira YadeWira committed Sep 1, 2026
  • docs: reframe the last failure -- it is an address-mapping question, not a value one Measured the model memory against the binary's: 580 differing bytes of 17.3M at block-2 entry, 474 of them from the cold state. But overwriting the cold state with the binary's values breaks block 1, and the tier2 align table's apparent mismatch is an artefact of a port-invented address. So the question is which cells this port places where the original does not. Adds two method notes, including: a port-invented address is not evidence about the original, and run the suite before believing a measured fix.

    @YadeWira YadeWira committed Sep 1, 2026
  • docs: synthetic suite 88/88 (100%); the audio defect is fully closed FUN_0809bdc0 is ported, which closes decr_param==2 audio for all three codecs. Every synthetic fixture now decodes natively for all eight methods with zero bridge, and the real corpus is 479/480 -- one file left in the whole project, the already-localised -cO literal bit. Also records that the notes' "Fenwick tree" description of FUN_0809bdc0 did not survive reading it, and how the initial tables were derived when the builder had no decompile either.

    @YadeWira YadeWira committed Sep 1, 2026
  • docs: -cc at 60/60; open work down to two defects The last -cc failure was our own verification gate declining a byte-exact decode, because the entry's checksum is a type-5 chunk record that need not sit in the front metadata run. Seven of eight codecs are now perfect on the real corpus and the three leftovers are two independent defects. Adds two method notes: check whether the decode is actually wrong before investigating the decoder, and a correct decode is its own oracle for locating metadata in the container.

    @YadeWira YadeWira committed Sep 1, 2026
  • docs: audio defect closed for -cc/-cO -- it was per-codec constants, not algorithm The largest open item is resolved for two of its three codecs, and the cause was three constants hardcoded to -cO's values rather than any missing algorithm. Open work is down to four corpus failures across three independent defects, with -co's unported bit-count decoder class the only genuinely unported code left. Adds three method notes, the sharpest being: a hand-derivation that contradicts a measurement is wrong, even twice in a row.

    @YadeWira YadeWira committed Sep 1, 2026
  • docs: audio split into its two real causes; one is a genuinely unported class -co and -cc do not share a defect. -co's bit-count decoder is a different class selected by vtable and never ported (FUN_0809bdc0, a Fenwick-tree coder with no decompile) -- the one genuinely unported piece left. -cc's entropy layer is byte-exact and its defect is one predictor stage, localised to the element. Also retracts the previous revision's plan to replace the residual front end.

    @YadeWira YadeWira committed Sep 1, 2026
  • docs: audio inter-channel branch fixed; the remaining difference named One of the two audio differences is closed (the -co inter-channel branch). The other is now named precisely -- the residual front end, where the port uses the community reference's bespoke bit-count decoder instead of the binary's generic arith decoder + stereo residual decoder. Also retracts the "missing FUN_080958d0" claim from the previous revision and records why the heuristic behind it was wrong.

    @YadeWira YadeWira committed Sep 1, 2026
  • docs: GDB ground truth for the audio defect -- it is not a new algorithm family The page had this down as needing GDB with no further detail. It now carries the per-codec stage sequence, the three primitives already byte-exact in-tree (one of which is documented in-tree as "never the real path" -- true for lzpf, false here), the two that are missing, and the measured facts that localise the defect to residual production only. Plus three more refuted hypotheses.

    @YadeWira YadeWira committed Sep 1, 2026
  • docs: stored-LZ-block fix, and re-classify the remaining failures by trace The open-work list had grouped the leftovers by filename. Tracing each one shows they are three defects, not eleven failures: the decr_param==2 audio gap accounts for 9 of 11 (this page had it down as "the last 2 synthetic failures"), plus one -cc BWT wrong-bytes file and one -cO model divergence. The -cO case is now localised to a single wrong literal bit at a known offset, with the ring-position measuring trap that produced a false lead written down, so it is a warm start rather than a fresh investigation.

    @YadeWira YadeWira committed Sep 1, 2026
  • docs: -cd/-cD both 60/60; rewrite open work after 7a4d4c5 Two cross-chunk state fixes close the top TWO items of the previous open-work list, and neither had the cause this page attributed to it -- the "order-32 predictor" lead was empty (the file was already in the tree) and the "-cd residuals / LMS detail" were the same stale ring cursor. Recorded both misdiagnoses explicitly, plus six new method notes, the biggest being: verify a stored diagnosis before spending a session on it, and group failures by WHERE they diverge rather than by which file they are. Open work is now one class: the -co/-cO/-cc wrong-bytes bugs, with four byte-exact oracles per file that did not exist before.

    @YadeWira YadeWira committed Sep 1, 2026
  • docs: record cd5e3f3 and add a detailed open-work list Captures the full pending state (per-file deltas, where to start, refuted hypotheses, and the method notes) so it survives independently of any one session's context. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

    @YadeWira YadeWira committed Sep 1, 2026
  • docs: record the prefilter hash-backfill fix (eb66e8c), -cf/-cF now 60/60 Also notes that the "shared hard set" of four files was one defect, and the stale-dump measurement error made while diagnosing it. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

    @YadeWira YadeWira committed Sep 1, 2026
  • docs: record the -cf/-cF exe-filter fix (f885e1c) and refresh the standing Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

    @YadeWira YadeWira committed Sep 1, 2026
  • docs: record the -cD stage-index fix (c831c31) and the 8-codec standing -cD 34 -> 52/60, the biggest single fix of the session. Adds a real-corpus standing table so codecs are compared on one corpus rather than across differently-generated ones. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

    @YadeWira YadeWira committed Aug 31, 2026
  • docs: record the dece state-model correction (491a54d) Reference resets the filter per block; correct model persists across a run of consecutive dece blocks. Fourth instance of the "shared state the original advances across blocks" bug shape. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

    @YadeWira YadeWira committed Aug 31, 2026
  • docs: record the dece port and the fuzz-found OOB write (648df9e) Post-filter chain fully native. Notes the lesson: fuzz on corrupt input, since byte-exactness testing cannot find memory-safety bugs in a decompressor. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

    @YadeWira YadeWira committed Aug 31, 2026
  • docs: record tt 0x04/0x01 ports and the UB they exposed (fe07c69) Text-transform gap closed. Notes the recurring pattern: closing a coverage gap exposes latent UB in newly-reached code, so re-run ASAN after every gap fix. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

    @YadeWira YadeWira committed Aug 31, 2026