Merge pull request #42 from iamriajul/vk/0018-browser-push-not

feat: add browser notification support

Author: iamriajul

AGENTS.md

@@ -31,6 +31,7 @@ Downstream deployment and integration layer for Vibe Kanban. Owns the Helm chart
 - GitHub Actions own the checked-in release automation.
 - `remote-v*` tags build Remote and Relay images, publish them to GHCR, optionally mirror them to Docker Hub, and publish the Helm chart to GHCR as an OCI artifact.
 - `v*` tags publish the `vibe-kanban-team` npm package via `scripts/publish-npm.sh`.
+- Canonical releases must be tagged from `main` after the feature PR is merged. Do not release directly from feature branches.
 - `nightly-release-check.yml` runs on schedule for `frontend` and `remote`, compares upstream tags, verifies patch applicability, updates submodule + patch metadata, and pushes commit/tag for release workflows.
 - Manual workflow dispatch must target an existing `git_ref`; versions are derived from that ref.
 - Keep tag naming stable:
@@ -49,6 +50,8 @@ Downstream deployment and integration layer for Vibe Kanban. Owns the Helm chart
 
 Closed loop: **Edit → Verify → Commit**. Never commit unverified changes.
 
+Release flow: **Branch -> PR -> Merge to `main` -> Tag on `main` -> Release**.
+
 ### Prerequisites
 
 ```bash

CLAUDE.md

@@ -31,6 +31,7 @@ Downstream deployment and integration layer for Vibe Kanban. Owns the Helm chart
 - GitHub Actions own the checked-in release automation.
 - `remote-v*` tags build Remote and Relay images, publish them to GHCR, optionally mirror them to Docker Hub, and publish the Helm chart to GHCR as an OCI artifact.
 - `v*` tags publish the `vibe-kanban-team` npm package via `scripts/publish-npm.sh`.
+- Canonical releases must be tagged from `main` after the feature PR is merged. Do not release directly from feature branches.
 - `nightly-release-check.yml` runs on schedule for `frontend` and `remote`, compares upstream tags, verifies patch applicability, updates submodule + patch metadata, and pushes commit/tag for release workflows.
 - Manual workflow dispatch must target an existing `git_ref`; versions are derived from that ref.
 - Keep tag naming stable:
@@ -49,6 +50,8 @@ Downstream deployment and integration layer for Vibe Kanban. Owns the Helm chart
 
 Closed loop: **Edit → Verify → Commit**. Never commit unverified changes.
 
+Release flow: **Branch -> PR -> Merge to `main` -> Tag on `main` -> Release**.
+
 ### Prerequisites
 
 ```bash

RELEASE.md

@@ -48,8 +48,9 @@ NPM publishes through trusted publishing / OIDC in GitHub Actions. `scripts/publ
 
 1. Update the tracked upstream ref with `scripts/update-vibe-kanban.sh`.
 2. Apply and verify the downstream patch stack with `scripts/apply-patches.sh`.
-3. Commit and push the submodule or patch changes.
-4. Push the release tag for the workflow you want to run.
+3. Commit and push the submodule or patch changes on a feature branch.
+4. Open and merge a PR into `main`.
+5. Create and push the release tag from `main` for the workflow you want to run.
 
 Manual workflow dispatch is supported for existing release refs only. Pass `git_ref`, let the workflow derive the version from that ref, and avoid free-form version-only publishes.