[deadp]

Adds CHANGELOG.md so 0.1.0 can be tagged and released. engine/version.py already says 0.1.0, but there is no tag or GitHub release yet, and SECURITY.md promises fixes for "every version currently published".

What's in it

• 0.1.0 in examiner-facing terms: evidence formats, filesystems, analysis, interface and cases, condensed from the README, with Add midnight, sepia and high-contrast themes #1, Replace theme toggle with a theme picker dialog #9 and CI, first tests and security policy (supersedes #7 and #8) #12 linked.
• Not implemented, carried over from the README.
• Known issues, pointing at Fuzzer findings: exFAT run-list memory exhaustion, jbd2 AttributeError, NTFS record-count hang #15.
• An empty Unreleased section. CONTRIBUTING.md gains one bullet asking PRs to add a line there.

The 0.1.0 heading says Unreleased rather than a date, because the date should be the day the tag is cut. If #13 or #14 merge first, they can go under Unreleased or into 0.1.0, whichever you prefer.

Releasing 0.1.0 (for the maintainer)

Once this is merged, from an up-to-date main:

1. In CHANGELOG.md, change ## [0.1.0] - Unreleased to today's date, e.g. ## [0.1.0] - 2026-09-17, and commit.
2. Tag and push:

   git tag -a v0.1.0 -m "Strata 0.1.0"
   git push origin v0.1.0

3. Create the release with the 0.1.0 section as its notes:

   awk '/^## \[0.1.0\]/{f=1;next} /^## \[/{f=0} f' CHANGELOG.md > notes.md
   gh release create v0.1.0 --title "Strata 0.1.0" --notes-file notes.md

The [0.1.0] link at the bottom of the changelog resolves once the tag exists.

🤖 Generated with Claude Code

[switch-nz]

Pushed eebdaa2 on top of your commit (maintainer edits were enabled — thanks), then merging.

• Known issues now links Parser bugs that return wrong results without warning (expected-failure tests from #13) #19 and lists its wrong-result bugs individually, since those — exFAT timestamps labelled UTC without the offset, sparse ext4 files at the wrong offsets, split raw sets loading as a partial disk, and so on — matter more to an examiner than the crashes in Fuzzer findings: exFAT run-list memory exhaustion, jbd2 AttributeError, NTFS record-count hang #15. Each one is still an expected failure on main (16 in total), so nothing listed is already fixed.
• 0.1.0 picks up what merged since you wrote this, as you suggested it could: EWF read bounds (Bound every size-driven read when opening EWF images #14), the exFAT run clamp (exfat: bound contiguous run expansion at cluster heap end #17), and tests/fuzzing/CodeQL (Add parser tests, fuzzing, request-gate tests and CodeQL #13).
• Raw/dd is now single-file, and split raw sets move to Not implemented, matching the README correction in Correct the README's claim that split raw sets are supported #20.

The release steps in your description still apply as written.