Release v0.1.1

[aisrael]

Summary

Prepare release v0.1.1 with dot-access syntax for maps, typeof builtin, and fixes for map/array literal evaluation.

See the v0.1.1 section in CHANGELOG.md for full release notes.

Changes since v0.1.0

• Dot-access syntax (u.foo) for map field reads
• typeof runtime type introspection
• Map and array literals now evaluate correctly
• 2 commits, 39 files changed (+1221 / −205)

Full diff vs main

Test plan

• cargo clippy --all-targets -- -D warnings
• cargo test (180 tests passing)

Made with Cursor

[aisrael]

@claude Review this PR

[claude]

Claude finished @aisrael's task in 1m 34s —— View job

---

Review: Release v0.1.1

• Gather context (read changed files, diff vs origin/main)
• Understand the request (code review of release PR)
• Review CHANGELOG.md, Cargo.toml/Cargo.lock version bump, features/cli.feature
• Post review feedback

This is a small, low-risk release-prep PR (+15/−4 across 4 files). Overall it's clean and internally consistent:

• Cargo.toml / Cargo.lock — version bumped 0.1.0 → 0.1.1 consistently in both files.
• features/cli.feature — expected flt version output updated to flt version 0.1.1. This correctly matches version() in src/bin/flt.rs:7, which derives from clap::crate_version!() (i.e., Cargo.toml), so the test assertion stays in sync with the actual binary output. ✅
• CHANGELOG.md — reorganized the v0.1.1 entry into Highlights / Improvements / Changelog Stats sections. Reads well and accurately reflects the PR description (dot-access syntax, typeof, map/array literal fixes).

Minor / non-blocking observations

1. Stale version references elsewhere in the repo weren't updated by this PR and now disagree with the new 0.1.1:

   • README.md:19 — flt = "0.1.0" (dependency example)
   • docs/README.md:17 — "...currently implemented parser and CLI evaluator for version 0.1.0."
   • docs/quickstart.md:14 — example output still shows flt version 0.1.0

   Worth a follow-up (can be this PR or a quick fast-follow) so docs don't drift from the released version.
   Fix this →

2. CHANGELOG.md's "2 commits since v0.1.0" stat is relative to the previous changelog section rather than an actual git ref — there's no v0.1.0 tag in the repo. Not a problem for this PR, but tagging releases (e.g. git tag v0.1.0, v0.1.1) would make that phrasing verifiable and make git diff/git log release comparisons easier going forward.

3. Test plan not independently verified: cargo build/cargo test/cargo clippy require network/build permissions that aren't available to me in this sandboxed run, so I could not independently confirm the checked-off "180 tests passing" / clippy-clean claims in the PR description. The diff itself touches no source logic (only metadata/docs/test-fixture strings), so risk is low, but flagging this limitation per the task instructions — if this matters, granting Bash(cargo build:*)/Bash(cargo test:*) to --allowedTools would let me verify directly next time.

No bugs or logic issues found — the substantive changes (typeof, dot-access, literal evaluation fixes) were already merged in #10; this PR is purely version/changelog bookkeeping and looks correct.