From 335c859e651c0f097a123aa3f49a065e0ab7b502 Mon Sep 17 00:00:00 2001 From: sstent Date: Fri, 20 Feb 2026 10:52:33 -0800 Subject: [PATCH] docs(conductor): Add Track Completion Protocol to workflow --- conductor/workflow.md | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/conductor/workflow.md b/conductor/workflow.md index 6f9cfd8..e9b3a11 100644 --- a/conductor/workflow.md +++ b/conductor/workflow.md @@ -134,6 +134,24 @@ All tasks follow a strict lifecycle: 10. **Announce Completion:** Inform the user that the phase is complete and the checkpoint has been created, with the detailed verification report attached as a git note. +### Track Completion Protocol + +**Trigger:** This protocol is executed when all phases and tasks in a track are complete. + +1. **Version Bump (Code Changes Only):** + - If the track involved code changes (i.e., not purely documentation), you **must** bump the project version number. + - Update `deno.json` and any other version-tracked files (e.g., `icalendar.ts`) with the new version. + - Commit the version bump with message: `chore: Bump version to `. + +2. **Push Changes (Code Changes Only):** + - If the track involved code changes, you **must** push the changes to the remote repository. + - **Command:** `git push` + +3. **Monitor CI/CD (Code Changes Only):** + - After pushing, you **must** monitor the resulting Gitea Action to ensure it completes successfully. + - Use the `gitea-push-watch` skill if available, or check the Gitea interface manually. + - **Requirement:** The track is NOT complete until the CI/CD pipeline passes. If it fails, you must investigate and fix the issue. + ### Quality Gates Before marking any task complete, verify: