chore(release): prepare v0.2.0

[nao1215]

Added

• qrkit/render/ascii: AsciiOptions opaque type plus default_options/0, with_margin/2, with_inverse_option/2, to_string_with/2, and to_string_compact_with/2 — mirroring the builder-style options shape qrkit/render/svg already exposes (svg.default_options |> svg.with_margin(2)). The new functions let terminal callers tighten the quiet zone for debug dumps, fixture diffs, and inline-doc panels without giving up the ISO/IEC 18004 4-module default for camera-scannable output. Existing to_string/1, with_inverse/1, and to_string_compact/1 keep the 4-module default and are unchanged at the API level. (feat(render/ascii): expose with_margin (and/or options builder) like the SVG renderer #8)

Fixed

• qrkit/content: comprehensive RFC compliance pass for the iCalendar and vCard renderers (issues content.event_to_string produces malformed iCal for negative start_unix / end_unix #9–content.email leaves to parameter unescaped, producing broken mailto URIs for ?/&/#/space in addr-spec #17).
  • vcard_to_string and event_to_string now terminate lines with CRLF (\r\n) per RFC 5545 §3.1 / RFC 2426 §2.1, not LF-only — strict consumers (Apple iOS Calendar in MIME contexts, Outlook drag-and-drop, python-icalendar, node-vcard) accept the output. (content uses LF (not CRLF) line terminator for iCal & vCard payloads (RFC 5545 §3.1 / RFC 2426 §2.1) #12)
  • Both renderers fold long content lines at 75 octets with CRLF<space> continuation per RFC 5545 §3.1 / RFC 2426 §2.6. Folding is grapheme-aware so multi-byte UTF-8 sequences are never split. (content does not fold long iCal & vCard content lines at 75 octets (RFC 5545 §3.1 / RFC 2426 §2.6) #13)
  • escape_ical / escape_vcard strip raw \r and NUL from TEXT values (RFC 5545 §3.3.11 / RFC 2426 §2.4.2 forbid raw control characters; CR in particular emulated CRLF and broke the document). (content escape helpers leave raw CR / NUL in iCal & vCard values (RFC 5545 §3.3.11 / RFC 2426 §2.4.2) #11)
  • event_to_string now emits the RFC-required PRODID (VCALENDAR §3.7.3), UID, and DTSTAMP (VEVENT §3.6.1). UID is a deterministic synthesis of the event's title hash + start + end so the same event produces the same UID across runs; DTSTAMP defaults to start_unix since no clock is available in a pure rendering function. (content.event_to_string omits RFC 5545-required UID, DTSTAMP, and PRODID properties #14)
  • vcard_to_string always emits the RFC 2426 MANDATORY N and FN properties (§3.1.1 / §3.1.2) — when the caller did not call with_name, both are emitted with empty values (N:;;;; and FN:) so the structure is still spec-conformant. (content.vcard_to_string omits RFC 2426-required N and FN properties #15)
  • event_to_string in all_day mode now bumps DTEND to start + 1 day when the caller passed end_unix == start_unix, matching RFC 5545 §3.6.1's non-inclusive-end requirement for DATE-valued events. (content.event_to_string in all_day mode allows DTEND == DTSTART (RFC 5545 §3.6.1 non-inclusive-end violation) #16)
  • event_to_string handles pre-epoch unix values correctly by floor-dividing into days / seconds-of-day (Gleam's / and % truncate toward zero, which had let negative sub-day components leak into the formatted output). (content.event_to_string produces malformed iCal for negative start_unix / end_unix #9)
  • event_to_string clamps year to [1, 9999] so values beyond Y10K cannot break the RFC 5545 fixed-width YYYYMMDDTHHMMSSZ format. (content.event_to_string emits 5-digit year for unix beyond Y10K (RFC 5545 §3.3.5 format break) #10)
  • Final BEGIN/END boundary line is now terminated with CRLF (RFC 5545 §3.1 / RFC 2426 §2.1 require every content line — including the last — to end with CRLF).
  • content.email now percent-encodes the to addr-spec along with subject and body, so reserved characters (?, &, #, space) in to no longer produce a malformed mailto: URI. (content.email leaves to parameter unescaped, producing broken mailto URIs for ?/&/#/space in addr-spec #17)

[coderabbitai]

Warning

Rate limit exceeded

@nao1215 has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 31 minutes and 26 seconds before requesting another review.

You’ve run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 27f160b0-cab5-4f6d-a5e4-7a372e739605

📥 Commits

Reviewing files that changed from the base of the PR and between dd3fe1d and f71ef71.

📒 Files selected for processing (3)

• CHANGELOG.md
• gleam.toml
• src/qrkit.gleam

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch release/v0.2.0

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}