From 4c1a0c8b78c0f50b208a4222ec54ad3438257de8 Mon Sep 17 00:00:00 2001
From: Michael Dieringer <65093775+MichaelDieringer@users.noreply.github.com>
Date: Tue, 23 Jun 2026 19:38:53 +0200
Subject: [PATCH] Add CURABIS-BCMCP-008/009/010: git lifecycle must sync BC
 subtask dev status

---
 .../mcp/git-lifecycle-must-sync-bc-status.md  | 86 +++++++++++++++++++
 1 file changed, 86 insertions(+)
 create mode 100644 custom/knowledge/mcp/git-lifecycle-must-sync-bc-status.md

diff --git a/custom/knowledge/mcp/git-lifecycle-must-sync-bc-status.md b/custom/knowledge/mcp/git-lifecycle-must-sync-bc-status.md
new file mode 100644
index 0000000..02954b9
--- /dev/null
+++ b/custom/knowledge/mcp/git-lifecycle-must-sync-bc-status.md
@@ -0,0 +1,86 @@
+---
+rule: CURABIS-BCMCP-008
+title: Git lifecycle must sync BC subtask dev status
+severity: warning
+domain: git, mcp, bc-integration
+applies-to: [feature branches, bugfix branches, hotfix branches]
+---
+
+# Git lifecycle must sync BC subtask dev status
+
+Every AL feature branch is linked to a BC subtask. The `gitHubDevStatus` and
+`gitHubBranch` fields on the subtask must reflect the real state of the branch
+at all times — automatically, without manual steps.
+
+## Branch naming convention
+
+Branches must follow this pattern so automation can parse the BC task reference:
+
+```
+<type>/<projectNo>-<taskNo>[-optional-description]
+```
+
+| Segment | Format | Example |
+| --- | --- | --- |
+| type | `feature`, `bugfix`, `hotfix` | `feature` |
+| projectNo | `[A-Z]{2,4}\d{4}-\d{5}` | `DEV2023-00027` |
+| taskNo | zero-padded or plain integer | `004` or `4` |
+| description | optional, hyphen-separated | `bc-agent-semantic-tools` |
+
+**Valid examples:**
+```
+feature/DEV2023-00027-004-bc-agent-semantic-tools
+bugfix/DEV2023-00027-003-odata-string-key
+hotfix/DEV2023-00012-001-invoicing-crash
+feature/DEV2023-00027-4
+```
+
+**Invalid (no automation):**
+```
+my-feature
+fix-thing
+DEV2023-00027
+```
+
+## Status mapping
+
+| Git event | gitHubDevStatus | gitHubBranch |
+| --- | --- | --- |
+| New branch created (`git checkout -b`) | `In Progress` | `<branch-name>` |
+| Branch abandoned (switch to non-main without committing) | `Backlog` | `""` |
+| Merged/committed to main | `Done` | `main` |
+| Branch parked (manual) | `On Hold` | `<branch-name>` |
+
+## Implementation
+
+Automation is provided by two git hooks in `.githooks/` (activated via
+`git config core.hooksPath .githooks`) that call
+`Scripts/Invoke-BCGitSync.ps1`:
+
+- `post-checkout` — detects branch creation and branch abandonment
+- `post-commit` — detects commits/merges on main
+
+`Invoke-BCGitSync.ps1` calls the BC OData API directly (same credentials as
+`bc-agent.js`) and never blocks the git operation — all errors are swallowed
+with a warning.
+
+## Safety rules
+
+CURABIS-BCMCP-008 The sync script NEVER writes BC subtask `status`
+  (Created/Accepted/In progress/Finished/Invoiced). It only writes
+  `gitHubDevStatus` and `gitHubBranch`. These are the only two fields
+  the agent is allowed to modify (see CURABIS-BCMCP-001).
+
+CURABIS-BCMCP-009 The sync script exits 0 on all errors. It must never
+  block a git commit, checkout, or merge. BC sync is best-effort.
+
+CURABIS-BCMCP-010 Only tasks in `activeTasks` (status = Accepted or In progress)
+  are updated. A branch against a `Created` task is silently ignored until the
+  task is approved in BC.
+
+## BCApps reference
+
+Branch naming conventions and git workflow integration follow the patterns used
+in [microsoft/BCApps](https://github.com/microsoft/BCApps) — see
+`.github/CONTRIBUTING.md` for Microsoft's own conventions on feature branches
+and PR titles that reference work items.