Collomia v0.2.2

Collomia v0.2.2

Collomia v0.2.2 adds safer Git write tooling, self-documenting configuration, smarter model-limit handling, and substantial shutdown and persistence hardening.

Highlights

Safer Git writes

• Added git_commit, which commits exactly the files explicitly named—without sweeping in unrelated edits, staged work, untracked files, or build output.
• Commit previews flow through the existing permission system, allowing credential-sensitive paths such as .env files and private keys to be caught before entering history.
• Added git_branch for creating and switching to a new branch without modifying the working tree.
• Neither tool pushes. Remote publication remains governed separately through run_command and permissions.publication.
• Both tools can be hidden with options.disabled_tools and are unavailable in planning mode.

Self-documenting configuration

• Added collo schema config, which generates a JSON Schema 2020-12 contract directly from Collomia’s configuration types.
• collo init and collo setup now create collomia.schema.json and add a corresponding $schema reference.
• Compatible editors now provide field completion, documentation on hover, valid-value suggestions, and inline validation.
• collo doctor detects missing or stale schema files.
• /config now shows applied configuration layers, effective safety settings, their origins, and any project-level weakening that was refused.
• /config all displays every effective setting while structurally redacting credentials.

Smarter provider setup and token limits

• Added collo setup --provider <name> to reverify an existing provider without replacing its credential.
• Setup now resolves both context_window and max_tokens, preferring endpoint-reported values, then conservative published limits, and clearly labeling assumptions.
• collo doctor warns when either limit is absent and explains the resulting behavior.
• collo config validate now rejects configurations where max_tokens >= context_window.
• OpenAI-compatible and Anthropic providers now recognize output-ceiling errors, retry at the provider-stated limit, warn, and remember that ceiling for the session.

Shutdown and durability hardening

• SIGHUP now triggers an orderly shutdown, covering closed terminal windows and dropped SSH connections.
• Background processes are stopped instead of being orphaned when the terminal disappears.
• Completed session turns are flushed to stable storage, with an additional flush during orderly shutdown.
• Audit entries are flushed individually so recent permission decisions survive a crash or power loss.
• Sync failures are latched like write failures, preventing later activity from making an incomplete record appear valid.
• Session recovery is now tested at every possible truncation point, including torn final records and lost trailing newlines.

Usability and observability

• Shell completion for Bash, Zsh, Fish, and PowerShell now derives from one validated command vocabulary and covers all supported subcommands.
• /context now explains that automatic compaction is disabled when context_window is missing.
• /context and the Session tab can report request gaps that exceeded the five-minute prompt-cache lifetime. This is measurement only; the cache lifetime remains unchanged.
• Debug-log redaction now covers errors, structs, slices, and other text-bearing values—not only plain strings.
• macOS credential operations now fail safely in service, container, or unusual HOME environments where no Keychain can be resolved, avoiding the system’s potentially destructive “Reset To Defaults” dialog.

Quality and platform improvements

• Added full-filesystem durability testing on macOS.
• Increased interruption and cancellation stress coverage from 5 to 20 iterations.
• Added dedicated durability and session-truncation sweeps to release CI.
• Fixed Windows test portability involving build tags, open file handles, Git autocrlf warnings, and clean-runner Git identity.
• Fixed a timing race in the macOS SIGHUP integration test.

Upgrade notes

No configuration migration is required. However:

• Configurations with max_tokens greater than or equal to context_window must be corrected before strict validation will pass.

• Regenerate an existing editor schema after upgrading:

  collo schema config > collomia.schema.json

  Re-running collo setup also refreshes the generated schema.

• /config has a new human-readable output format. Scripts should continue using collo config show, whose interface is unchanged.

• New Git tools are enabled by default but may be disabled through options.disabled_tools.

Full changelog: [v0.2.1...v0.2.2](v0.2.1...v0.2.2)