v0.2.5

v0.2.5 — Telegram‑first RC → GA

Highlights

• Telegram summaries now preserve line breaks (multiline) with configurable caps:
  • max_msg_lines / max_msg_chars (general summaries)
  • peer_message_max_lines / peer_message_max_chars (Peer↔Peer)
• Bridge cwd fixed: logs write to .cccc/state/bridge-telegram.log; status validates live PID.
• CLI additions: cccc bridge restart / logs / version.
• Telegram‑first README: install → init → doctor → token → run；Minimal “First Landing Checklist”；Typical Session (Explore→Decide→Build)。
• Prompt upgrades (lightweight): human‑like rhythm with short templates (IDEA / Decision ≤6 lines / Reflect 2 lines)。No hard quotas.

Changes

• Packaging: single‑source scaffold with build‑time sync（scripts/sync_scaffold.py）；clean repo ignores (state/logs/work/mailbox/docs/tests/venv)。
• Workflow: .github/workflows/release.yml auto‑publishes TestPyPI for rc tags and PyPI for stable tags。
• Inbound suffix guidance（sample in README）：nudges peers to explore first, avoid pure ACK, capture reflect。

Upgrade Notes

• After upgrading:
  • cccc init --force # refresh scaffold from package resources
  • Review .cccc/settings/telegram.yaml: new keys
  • max_msg_lines, peer_message_max_lines
• Optional: update inbound_suffix in .cccc/settings/cli_profiles.yaml（see README samples）
• cccc bridge restart
• For first‑time users:
  • Copy PEERA.md → CLAUDE.md；PEERB.md → AGENTS.md；put brief in PROJECT.md
  • Ensure CLI commands (claude/codex) are on PATH or set commands.peer*/env vars