@sniper.ai/core 3.3.0 → 3.3.1

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.
@@ -22,7 +22,7 @@ checks:
22
22
 
23
23
  - id: open_questions
24
24
  description: No unresolved open questions remain
25
- check: "!grep:.sniper/artifacts/{protocol_id}/:\\*\\*TBD\\*\\*|\\*\\*TODO\\*\\*|\\*\\*OPEN\\*\\*"
25
+ check: "!grep:.sniper/artifacts/{protocol_id}/plan.md:\\*\\*TBD\\*\\*|\\*\\*TODO\\*\\*|\\*\\*OPEN\\*\\*"
26
26
  blocking: false
27
27
 
28
28
  - id: token_budget
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@sniper.ai/core",
3
- "version": "3.3.0",
3
+ "version": "3.3.1",
4
4
  "description": "SNIPER framework core — agents, skills, protocols, checklists, templates, and hooks",
5
5
  "type": "module",
6
6
  "exports": {
@@ -4,11 +4,11 @@ budget: 2000000 # 2M tokens
4
4
 
5
5
  phases:
6
6
  - name: discover
7
- description: Research, analyze codebase, produce discovery spec and PRD
7
+ description: Research and analyze codebase to produce discovery spec
8
8
  agents:
9
9
  - analyst
10
10
  spawn_strategy: single # One agent, no team needed
11
- interactive_review: true # User reviews spec/PRD before architecture begins
11
+ interactive_review: true # User reviews spec before architecture begins
12
12
  gate:
13
13
  checklist: discover
14
14
  human_approval: true
@@ -63,10 +63,11 @@ For each phase in the protocol, execute these 5 steps:
63
63
  ### Execute
64
64
 
65
65
  1. Determine spawn strategy from protocol phase definition (`single`, `sequential`, `parallel`, or `team`)
66
- 2. Spawn agents per [Reference: Spawn Strategies](#reference-spawn-strategies)
67
- 3. Monitor via TaskList if an agent is blocked, investigate and guide via SendMessage
68
- 4. If an agent crashes: note the failure, continue with remaining agents
69
- 5. After all parallel agents complete: coordinate worktree merges per [Reference: Merge Coordination](#reference-merge-coordination)
66
+ 2. Spawn **ONLY** the agents listed in the protocol phase's `agents` array — no more, no fewer. Do NOT infer additional agents from the phase description or outputs. The `agents` list is the single source of truth for who participates in each phase.
67
+ 3. Spawn agents per [Reference: Spawn Strategies](#reference-spawn-strategies)
68
+ 4. Monitor via TaskList — if an agent is blocked, investigate and guide via SendMessage
69
+ 5. If an agent crashes: note the failure, continue with remaining agents
70
+ 6. After all parallel agents complete: coordinate worktree merges per [Reference: Merge Coordination](#reference-merge-coordination)
70
71
 
71
72
  ### Checkpoint
72
73