chore: add chittytrack tail consumer to API worker

[chitcommit]

Summary

• Adds tail_consumers: [{ service: "chittytrack" }] to API worker wrangler config
• Adds observability: { enabled: true } (was missing)
• Closes observability gap identified during ecosystem-wide wrangler audit

Test plan

• Deploy and verify chittytrack receives tail events from chronicle API

🤖 Generated with Claude Code

Summary by CodeRabbit

• Documentation

  • Added README for ChittyChronicle service with details on capabilities (event logging, full-text search, timeline aggregation, audit retrieval) and deployment information.

• Chores

  • Enhanced Cloudflare configuration with observability and tail logging integration.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

[coderabbitai]

📝 Walkthrough

Walkthrough

Initial documentation and Cloudflare observability configuration added for the ChittyChronicle event logging service. README introduced with project details, capabilities, and technical stack. Wrangler configuration updated to enable observability and route logs to the chittytrack service.

Changes

Cohort / File(s)	Summary
Documentation README.md	Initial project documentation with service description, supported capabilities (full-text search, timeline aggregation, entity-scoped retrieval), technical stack (Neon PostgreSQL, Cloudflare Worker with Hono), and deployment details.
Cloudflare Configuration api/wrangler.jsonc	Enabled observability with tail consumer routing to chittytrack service for centralized log aggregation.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 A Chronicle Awakens

Through files we hop, docs in place,
The ChittyChronicle finds its space!
With logs now flowing, tails held high,
Our audit trail reaches for the sky. 🌟

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The PR title accurately describes the primary change: adding tail consumer configuration to the API worker's wrangler configuration file.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/add-chittytrack-tail-consumer

---

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.}

[coderabbitai]

🧹 Nitpick comments (1)

README.md (1)

4-10: Consider expanding documentation in follow-up PRs.

The README provides a solid foundation with clear service description, key features, and deployment details. For future iterations, consider adding:

• Installation/setup instructions
• API documentation or usage examples
• Local development setup
• Contribution guidelines
• Architecture diagrams or system context

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@README.md` around lines 4 - 10, Update the README for the ChittyChronicle
project to add the suggested follow-up sections: include an Installation/Setup
section with steps to deploy to Cloudflare Worker (chronicle.chitty.cc) and
connect to Neon PostgreSQL, an API Usage section with example requests and
responses for key endpoints, a Local Development section describing how to run
the Hono worker and local Neon/Postgres, a Contribution Guidelines section
(branching, PR/issue templates, coding style), and an Architecture/Diagrams
section showing system context and the tsvector search/indexing flow so readers
can quickly onboard and contribute.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In `@README.md`:
- Around line 4-10: Update the README for the ChittyChronicle project to add the
suggested follow-up sections: include an Installation/Setup section with steps
to deploy to Cloudflare Worker (chronicle.chitty.cc) and connect to Neon
PostgreSQL, an API Usage section with example requests and responses for key
endpoints, a Local Development section describing how to run the Hono worker and
local Neon/Postgres, a Contribution Guidelines section (branching, PR/issue
templates, coding style), and an Architecture/Diagrams section showing system
context and the tsvector search/indexing flow so readers can quickly onboard and
contribute.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: fa67d0bf-7217-449c-a783-b6a53bb34030

📥 Commits

Reviewing files that changed from the base of the PR and between 946242a and 7e64bae.

📒 Files selected for processing (2)

• README.md
• api/wrangler.jsonc