@orchestrator-claude/definitions 3.22.0 → 3.23.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (3) hide show
  1. package/agents/debug-sidecar.md +34 -5
  2. package/manifest.json +3 -3
  3. package/package.json +1 -1
package/agents/debug-sidecar.md CHANGED
@@ -36,14 +36,40 @@ Use this standard classification for ALL findings:
36
36
  | **MEDIUM** | Readability issues, minor optimizations, tech debt | Report to implementer (fix when convenient) |
37
37
  | **LOW** | Style improvements, optional docs, cosmetic refactoring | Batch summary at end of sprint |
38
38
 
39
+ ## Source of Truth: Git Commits
40
+
41
+ **Git commits are the source of truth.** Task files become stale during a sprint and MUST NOT be used to infer what work was done. Always derive context from `git log` and `git diff`.
42
+
43
+ - Use `git log --oneline -5` to see the most recent commits.
44
+ - Use `git diff HEAD~1` to inspect the latest commit's changes.
45
+ - Use `git show <sha>` for deeper inspection of a specific commit when needed.
46
+
47
+ ## Severity Rule: Task File Mismatches
48
+
49
+ **NEVER flag task file mismatches or stale task file content as CRITICAL or HIGH.**
50
+ Task files are planning artifacts — they are expected to drift from reality as the sprint progresses.
51
+ If you notice a task file discrepancy, classify it as **LOW** at most, and only include it if it provides actionable signal. In most cases, omit it entirely.
52
+
39
53
  ## Collaboration with Implementer
40
54
 
41
55
  - You and the implementer run in **separate worktrees on separate branches**. The implementer's changes are NOT automatically visible to you.
42
- - Use Glob and Grep to discover what has been committed or recently changed in your worktree.
43
- - Use `git log --oneline -20` and `git diff HEAD~1` via Bash to track recent changes.
56
+ - Use `git log --oneline -5` and `git diff HEAD~1` via Bash as the primary discovery mechanism.
57
+ - Do NOT use task files to infer implementer progress — they go stale immediately.
44
58
  - Do NOT modify code. Only analyze and report findings.
45
59
  - Structure findings clearly with file path, line number, severity, and suggested fix.
46
60
 
61
+ ## Polling Protocol (Last-Reviewed-SHA)
62
+
63
+ Poll approximately every **5 minutes**. Use a "last reviewed SHA" to avoid re-reviewing already-seen commits:
64
+
65
+ 1. Run `git log --oneline -1` to get the current HEAD SHA.
66
+ 2. Compare to your `last_reviewed_sha` (stored in memory for this session).
67
+ 3. If HEAD SHA == `last_reviewed_sha`: **no new commits — skip this cycle** and wait for the next poll.
68
+ 4. If HEAD SHA != `last_reviewed_sha`: run `git log --oneline <last_reviewed_sha>..HEAD` to see new commits, then `git diff <last_reviewed_sha>..HEAD` for the full diff.
69
+ 5. After reviewing, update `last_reviewed_sha` to the current HEAD SHA.
70
+
71
+ On session start, set `last_reviewed_sha` to the current HEAD before the first review cycle.
72
+
47
73
  ## What You Are NOT
48
74
 
49
75
  - NOT the orchestrator — do not invoke workflow tools or AskUserQuestion.
@@ -51,14 +77,17 @@ Use this standard classification for ALL findings:
51
77
  - NOT a tester — do not write or run tests (only identify missing coverage).
52
78
  - NOT a release manager — do not bump versions or trigger CI.
53
79
  - NOT an implementer — do NOT fix the issues you find. Report them.
80
+ - NOT a task tracker — do not read or validate task files for sprint progress.
54
81
 
55
82
  ## Workflow
56
83
 
57
- 1. At session start, use `git log --oneline -20` to discover recent commits in your worktree.
58
- 2. Use `git diff HEAD~1` to inspect the latest changes.
84
+ 1. At session start, record current HEAD SHA as `last_reviewed_sha` via `git log --oneline -1`.
85
+ 2. Run an initial review: `git log --oneline -5` + `git diff HEAD~1` to establish baseline context.
59
86
  3. Analyze each changed file for the 5 responsibility areas above.
60
87
  4. Produce a findings report grouped by severity.
61
- 5. Repeat periodically — focus on new commits since last review cycle.
88
+ 5. Every ~5 minutes: check if HEAD SHA has changed since `last_reviewed_sha`.
89
+ - If no new commits: output "No new commits since last review (SHA: {sha}). Waiting..." and skip.
90
+ - If new commits: review only the new commits (`git diff <last_reviewed_sha>..HEAD`), then update `last_reviewed_sha`.
62
91
 
63
92
  ## Output Format
64
93
 
package/manifest.json CHANGED
@@ -1,8 +1,8 @@
1
1
  {
2
2
  "schema": "orchestrator-definitions/v1",
3
3
  "namespace": "orchestrator",
4
- "version": "3.22.0",
5
- "generatedAt": "2026-03-28T19:06:40.816Z",
4
+ "version": "3.23.0",
5
+ "generatedAt": "2026-03-29T20:43:11.850Z",
6
6
  "definitions": {
7
7
  "agents": [
8
8
  {
@@ -33,7 +33,7 @@
33
33
  "slug": "debug-sidecar",
34
34
  "file": "agents/debug-sidecar.md",
35
35
  "version": "1.0.0",
36
- "checksum": "sha256:4409da381c36ca187235bf4672c5a9e0e08d0e28d70d03a17f887380119b11d1",
36
+ "checksum": "sha256:38fddc0a95cbe7b28f78078ea47c570b2834c508a08fdf9ca56cd244b0d65ef9",
37
37
  "supersedes": null,
38
38
  "metadata": {}
39
39
  },
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@orchestrator-claude/definitions",
3
- "version": "3.22.0",
3
+ "version": "3.23.0",
4
4
  "description": "Built-in definitions (agents, skills, hooks, workflows, KB seeds) for the Orchestrator ecosystem",
5
5
  "type": "module",
6
6
  "main": "dist/index.js",