Skip to content

v0.2.8

Choose a tag to compare

View all tags
@ChesterRa ChesterRa released this 09 Sep 12:35
· 802 commits to main since this release
v0.2.8
444c9de

Release Notes (0.2.8, Stable)

  • Encoding & I18N
    • Harden mailbox decoding for non‑ASCII: try UTF‑8 (BOM/strict), then UTF‑16 (BOM and NUL‑heuristic LE→BE) before GB18030; fallback Latin‑1 only as last resort. Prevents mojibake when peers write UTF‑16.
    • Add Encoding Discipline to prompts and peer guides: always write .cccc/mailbox/**/{to_user.md,to_peer.md,patch.diff} as UTF‑8 (no BOM); avoid binary/unknown encodings or escaping that alters non‑ASCII text.
  • Delivery & Outbox
    • Unified Outbox (.cccc/state/outbox.jsonl) as the single source for outbound events.
    • Bridges read Outbox and send summaries; orchestrator clears mailbox files after logging to avoid repeats.
  • Telegram Bridge
    • Switch API calls to JSON/UTF‑8 (application/json; charset=utf-8) for sendMessage, etc., fixing non‑ASCII corruption.
    • Add outbound file ACK sidecar .sent.json; avoid re‑sending already delivered files.
  • Preamble & Startup
    • Lazy preamble: merge one lean SYSTEM block into the first user message per peer; no startup SYSTEM spam.
    • Reset preamble state on orchestrator start; log lazy-preamble-sent in ledger.
  • Insight & REV Governance
    • Enforce one trailing fenced ```insight block on to_peer (intercept if missing); insight is meta‑only by guidance (no runtime novelty caps).
    • Lightweight REV habit: track review/revise; gentle reminders only (non‑blocking).
  • Mailbox & NUDGE
    • Inbox pull flow with [NUDGE] guidance; ACK by file move or explicit token, reducing paste races.
    • Robust read/write with explicit UTF‑8 for internal state files.
  • Weekly Diary
    • Path clarified to .cccc/work/docs/weekly/YYYY-Www.md (non‑authoritative, light‑touch habit).
  • Housekeeping
    • Multiple RCs (rc1–rc4) validated the UTF‑8 JSON transport and decoding changes end‑to‑end.
    • Documentation refined to keep rules crisp (mailbox/outbox, insight, encoding, RFD).
  • Known Issues
    • If a peer writes non‑text/binary‑mangled content, the orchestrator cannot reconstruct valid Unicode. The prompt now instructs peers to emit UTF‑8; we can add a quiet ledger warning for non‑text writes if desired.
  • Upgrade Notes
    • Restart orchestrator and Telegram bridge after upgrading to load new prompt and decoder.
    • Ensure environment locales are UTF‑8 (e.g., LANG=en_US.UTF-8) for external tools invoked by peers.
Assets 2
Loading