docs: OSS community docs — Code of Conduct, Contributing, Changelog (#3)

- CODE_OF_CONDUCT.md: Contributor Covenant 2.1, BitByBit (B3) / prdai as
  community leaders, enforcement contacts.
- CONTRIBUTING.md: adapted to our setup — fork from main, bun + Biome +
  Lefthook + tests, dev workflow and hook behavior.
- CHANGELOG.md: Keep a Changelog format with the initial Unreleased set.
- README: add Contributing section linking the above.

Co-authored-by: prdai <prdai@users.noreply.github.com>
Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Author: prdai

CHANGELOG.md

@@ -0,0 +1,22 @@
+# Changelog
+
+All notable changes to this project are documented in this file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [Unreleased]
+
+### Added
+
+- `cloudflareKVCache(kv, options?)` factory and `CloudflareKVCache` class — a
+  Cloudflare KV-backed implementation of Drizzle ORM's query cache interface.
+- `explicit` (default) and `all` caching strategies.
+- Per-table reverse index for invalidation on mutation, storing full storage keys.
+- Tag-based caching and invalidation: `.$withCache({ tag })` entries are stored
+  under `{prefix}:t:{tag}` and dropped via `invalidate({ tags })`.
+- TTL resolution from `ex` (seconds) and `px` (milliseconds), clamped to KV's
+  60-second minimum; configurable `defaultTtlSeconds` and key `prefix`.
+- Documentation site (Astro + Starlight) deployed to Cloudflare Workers.
+
+[Unreleased]: https://github.com/BitByBit-B3/drizzle-cloudflare-kv-cache-adapter/commits/main

CODE_OF_CONDUCT.md

@@ -0,0 +1,75 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our community include:
+
+- Demonstrating empathy and kindness toward other people
+- Being respectful of differing opinions, viewpoints, and experiences
+- Giving and gracefully accepting constructive feedback
+- Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
+- Focusing on what is best not just for us as individuals, but for the overall community
+
+Examples of unacceptable behavior include:
+
+- The use of sexualized language or imagery, and sexual attention or advances of any kind
+- Trolling, insulting or derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others’ private information, such as a physical or email address, without their explicit permission
+- Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
+
+## Enforcement
+
+This project is maintained by the **BitByBit (B3)** organization, with **prdai** as the lead maintainer.
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at [bitbybit0123@gmail.com](mailto:bitbybit0123@gmail.com), or directly to the lead maintainer at [go2ranuga@gmail.com](mailto:go2ranuga@gmail.com). All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org), version 2.1, available at https://www.contributor-covenant.org/version/2/1/code_of_conduct.html.
+
+For answers to common questions about this code of conduct, see https://www.contributor-covenant.org/faq.

CONTRIBUTING.md

@@ -0,0 +1,86 @@
+# Contributing to drizzle-cloudflare-kv-cache-adapter
+
+Thank you for considering contributing! This project is maintained by the **BitByBit (B3)** organization (lead maintainer: **prdai**), and we welcome contributions from the community.
+
+## How to Contribute
+
+### Reporting Bugs
+
+If you encounter a bug, please [open an issue](https://github.com/BitByBit-B3/drizzle-cloudflare-kv-cache-adapter/issues) with:
+
+- A clear and descriptive title
+- A detailed description of the bug
+- Steps to reproduce it (ideally a minimal repro)
+- Your `drizzle-orm` version and runtime (Workers, Node, etc.)
+- Any relevant logs or code snippets
+
+### Suggesting Enhancements
+
+Have an idea to improve the project? Open an issue with:
+
+- A clear and descriptive title
+- A detailed description of the enhancement and the problem it solves
+- Any relevant examples or API sketches
+
+### Submitting Pull Requests
+
+1. Fork the repository and create your branch from `main`.
+2. Make your change. If you add or change behavior, **add tests**.
+3. Run the full check suite locally (see below) and make sure it passes.
+4. Open a pull request with a clear description and reference any related issues.
+
+## Development Setup
+
+This project uses [Bun](https://bun.sh) as the package manager.
+
+```sh
+# install dependencies (also installs the git hooks via lefthook)
+bun install
+
+# run the test suite
+bun test
+
+# type-check
+bun run typecheck
+
+# lint + format check
+bun run lint
+
+# auto-fix formatting and safe lint issues
+bun run format
+
+# build the library (ESM + types)
+bun run build
+```
+
+The documentation site lives in [`docs/`](./docs) and is a separate package:
+
+```sh
+cd docs
+bun install
+bun run dev      # local preview
+bun run build    # static build
+```
+
+## Git Hooks
+
+[Lefthook](https://lefthook.dev) is installed automatically on `bun install`:
+
+- **pre-commit** — runs [Biome](https://biomejs.dev) on staged files (lint + format, auto-fixing where safe).
+- **pre-push** — runs `typecheck`, `test`, and `build`.
+
+If you ever need to bypass a hook in an emergency, use `git commit --no-verify` (please don't make a habit of it).
+
+## Code Style
+
+Code style is enforced by Biome (single quotes, no semicolons, 2-space indent). Run `bun run format` before committing — the pre-commit hook will also handle it. Match the conventions already present in the surrounding code.
+
+## Changelog
+
+User-facing changes should be noted in [`CHANGELOG.md`](./CHANGELOG.md) under the `[Unreleased]` section, following the [Keep a Changelog](https://keepachangelog.com/en/1.1.0/) format.
+
+## Code of Conduct
+
+This project adheres to a [Code of Conduct](CODE_OF_CONDUCT.md). By participating, you are expected to uphold it.
+
+Thank you for contributing! 🙌

README.md

@@ -132,6 +132,10 @@ bun run typecheck
 bun run build
 ```
 
+## Contributing
+
+Contributions are welcome! Please read [CONTRIBUTING.md](./CONTRIBUTING.md) for the dev setup and PR workflow, and our [Code of Conduct](./CODE_OF_CONDUCT.md). Notable changes are tracked in [CHANGELOG.md](./CHANGELOG.md).
+
 ## License
 
 [MIT](./LICENSE) © BitByBit-B3