From 4524a94887f72c8c2a573bfee710eff638ae765e Mon Sep 17 00:00:00 2001
From: Ben Senescu <44480372+bensenescu@users.noreply.github.com>
Date: Mon, 16 Mar 2026 14:39:41 -0400
Subject: [PATCH] chore: prepare 0.0.2 release notes (#28)

* fix: cap per-user audit capacity

Block new audits before a user exceeds the temporary 100k audit footprint cap. Surface a clear delete-old-audits message in the audit launch UI.

* fix: reserve audit capacity with Drizzle

* chore: prepare 0.0.2 release notes
---
 .opencode/command/release-notes.md | 1 +
 package.json                       | 2 +-
 2 files changed, 2 insertions(+), 1 deletion(-)

diff --git a/.opencode/command/release-notes.md b/.opencode/command/release-notes.md
index 0180207..c2e4f30 100644
--- a/.opencode/command/release-notes.md
+++ b/.opencode/command/release-notes.md
@@ -8,6 +8,7 @@ Draft user-facing release notes for this repository.
 Rules:
 
 - Check `package.json` first. If the branch has not already bumped the version, update the `version` field before drafting release notes.
+- Prefer a patch version bump for now, since the project is still in rapid early development. Only choose a minor or major bump when the existing version change in `package.json` already does so or the user explicitly asks for it.
 - Treat an existing version change in `package.json` as the source of truth and do not overwrite it.
 - Use the generated notes as the source of truth; do not invent features or fixes.
 - Keep the tone concise and user-facing.
diff --git a/package.json b/package.json
index 0c026df..aef7d73 100644
--- a/package.json
+++ b/package.json
@@ -2,7 +2,7 @@
   "name": "open-seo",
   "private": true,
   "sideEffects": false,
-  "version": "0.0.1",
+  "version": "0.0.2",
   "type": "module",
   "scripts": {
     "dev": "AUTH_MODE=local_noauth vite dev",