@yanlinglabs/winter-conformance 0.0.14 → 0.0.16

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 (33) hide show
  1. package/README.md +2 -2
  2. package/dist/official/differential-harness.d.ts +90 -0
  3. package/dist/official/task-frames-script.d.ts +95 -0
  4. package/goldens/advertised-set-round.trace.json +9 -3
  5. package/goldens/background-task-round.trace.json +7 -1
  6. package/goldens/bash-background-round.trace.json +11 -3
  7. package/goldens/canusetool-approved-round.trace.json +7 -1
  8. package/goldens/compaction-auto-round.trace.json +7 -1
  9. package/goldens/compaction-manual-round.trace.json +7 -1
  10. package/goldens/denied-tool-round.trace.json +7 -1
  11. package/goldens/hook-denied-round.trace.json +7 -1
  12. package/goldens/hooked-tool-round.trace.json +7 -1
  13. package/goldens/interrupt.trace.json +7 -1
  14. package/goldens/mcp-tool-round.trace.json +6 -0
  15. package/goldens/messaging-facet-round.trace.json +7 -1
  16. package/goldens/mode-switch-mid-session.trace.json +7 -1
  17. package/goldens/multi-turn.trace.json +11 -5
  18. package/goldens/p6-anthropic-fake.trace.json +9 -2
  19. package/goldens/p6-gemini-fake.trace.json +9 -2
  20. package/goldens/p6-openai-chat-fake.trace.json +9 -2
  21. package/goldens/p6-openai-responses-fake.trace.json +9 -2
  22. package/goldens/p6-resolution-failure.trace.json +7 -1
  23. package/goldens/plain-query.trace.json +9 -3
  24. package/goldens/resume.trace.json +18 -6
  25. package/goldens/sendmessage-child-round.trace.json +63 -7
  26. package/goldens/skill-invocation-round.trace.json +7 -1
  27. package/goldens/structured-exhaustion-round.trace.json +7 -1
  28. package/goldens/structured-output-round.trace.json +7 -1
  29. package/goldens/subagent-permission-round.trace.json +84 -10
  30. package/goldens/subagent-spawn-round.trace.json +61 -5
  31. package/goldens/tool-round.trace.json +7 -1
  32. package/goldens/toolsearch-select-round.trace.json +6 -0
  33. package/package.json +1 -1
@@ -57,7 +57,13 @@
57
57
  ],
58
58
  "output_style": "default",
59
59
  "skills": [],
60
- "plugins": []
60
+ "plugins": [],
61
+ "agents": [
62
+ "claude",
63
+ "Explore",
64
+ "general-purpose",
65
+ "Plan"
66
+ ]
61
67
  }
62
68
  },
63
69
  {
@@ -95,7 +101,8 @@
95
101
  {
96
102
  "type": "tool_result",
97
103
  "tool_use_id": "call_p6",
98
- "content": "Error: path not found: /winter-fixture"
104
+ "content": "Error: path not found: /winter-fixture",
105
+ "is_error": true
99
106
  }
100
107
  ]
101
108
  }
@@ -48,7 +48,13 @@
48
48
  ],
49
49
  "output_style": "default",
50
50
  "skills": [],
51
- "plugins": []
51
+ "plugins": [],
52
+ "agents": [
53
+ "claude",
54
+ "Explore",
55
+ "general-purpose",
56
+ "Plan"
57
+ ]
52
58
  }
53
59
  },
54
60
  {
@@ -48,7 +48,13 @@
48
48
  ],
49
49
  "output_style": "default",
50
50
  "skills": [],
51
- "plugins": []
51
+ "plugins": [],
52
+ "agents": [
53
+ "claude",
54
+ "Explore",
55
+ "general-purpose",
56
+ "Plan"
57
+ ]
52
58
  }
53
59
  },
54
60
  {
@@ -61,7 +67,7 @@
61
67
  "content": [
62
68
  {
63
69
  "type": "text",
64
- "text": "echo: <system-reminder>\nAuto-memory (injected by the runtime, not typed by the user):\nAuto-memory for this project lives at /winter-home/projects/-winter-fixture/memory. The directory is created on demand and there are no memory tools: read and write it with the ordinary file tools, exactly like any other directory.\n\n/winter-home/projects/-winter-fixture/memory/MEMORY.md is the INDEX, and only its first 200 lines / 25 KB are loaded into a session. Keep every index entry to one line; the substance belongs in the topic file it points at, which you can read on demand when it turns out to matter.\n\nTo record something worth having in a LATER session -- a standing preference, a correction you were given, a durable constraint of this project -- write it to its own `<slug>.md` in that directory and add a one-line pointer to the index: `- [<slug>](<slug>.md) — <one-line summary>`.\n\nRevise a fact by rewriting its file and its index line, never by adding a near-duplicate under a new name; remove both once it stops being true. An index full of stale near-duplicates is worse than an empty one, because it costs the same and misleads.\n\nDo not record what the repository already records. Code, configuration, documentation and WINTER.md are durable on their own; memory is for what is true about this project or this user and lives nowhere in the tree.\n</system-reminder>\n\nhi"
70
+ "text": "echo: <system-reminder>\nAvailable agent types for the Agent tool:\n- claude: Catch-all for any task that doesn't fit a more specific agent. (Tools: *)\n- Explore: Fast read-only search agent for locating code. Use it to find files by pattern (eg. \"src/components/**/*.tsx\"), grep for symbols or keywords (eg. \"API endpoints\"), or answer \"where is X defined / which files reference Y.\" Do NOT use it for code review, design-doc auditing, cross-file consistency checks, or open-ended analysis — it reads excerpts rather than whole files and will miss content past its read window. When calling, specify search breadth: \"quick\" for a single targeted lookup, \"medium\" for moderate exploration, or \"very thorough\" to search across multiple locations and naming conventions. (Tools: All tools except Agent, Artifact, ExitPlanMode, Edit, Write, NotebookEdit)\n- general-purpose: General-purpose agent for researching complex questions, searching for code, and executing multi-step tasks. When you are searching for a keyword or file and are not confident that you will find the right match in the first few tries use this agent to perform the search for you. (Tools: *)\n- Plan: Software architect agent for designing implementation plans. Use this when you need to plan the implementation strategy for a task. Returns step-by-step plans, identifies critical files, and considers architectural trade-offs. (Tools: All tools except Agent, Artifact, ExitPlanMode, Edit, Write, NotebookEdit)\n\nWhen you launch multiple agents for independent work, send them in a single message with multiple tool uses so they run concurrently.\n</system-reminder>\n\n<system-reminder>\nAs you answer the user's questions, you can use the following context:\n# currentDate\nToday's date is <FIXTURE-DATE>.\n\n IMPORTANT: this context may or may not be relevant to your tasks. You should not respond to this context unless it is highly relevant to your task.\n</system-reminder>\n\n\nhi"
65
71
  }
66
72
  ]
67
73
  }
@@ -75,7 +81,7 @@
75
81
  "type": "result",
76
82
  "subtype": "success",
77
83
  "is_error": false,
78
- "result": "echo: <system-reminder>\nAuto-memory (injected by the runtime, not typed by the user):\nAuto-memory for this project lives at /winter-home/projects/-winter-fixture/memory. The directory is created on demand and there are no memory tools: read and write it with the ordinary file tools, exactly like any other directory.\n\n/winter-home/projects/-winter-fixture/memory/MEMORY.md is the INDEX, and only its first 200 lines / 25 KB are loaded into a session. Keep every index entry to one line; the substance belongs in the topic file it points at, which you can read on demand when it turns out to matter.\n\nTo record something worth having in a LATER session -- a standing preference, a correction you were given, a durable constraint of this project -- write it to its own `<slug>.md` in that directory and add a one-line pointer to the index: `- [<slug>](<slug>.md) — <one-line summary>`.\n\nRevise a fact by rewriting its file and its index line, never by adding a near-duplicate under a new name; remove both once it stops being true. An index full of stale near-duplicates is worse than an empty one, because it costs the same and misleads.\n\nDo not record what the repository already records. Code, configuration, documentation and WINTER.md are durable on their own; memory is for what is true about this project or this user and lives nowhere in the tree.\n</system-reminder>\n\nhi",
84
+ "result": "echo: <system-reminder>\nAvailable agent types for the Agent tool:\n- claude: Catch-all for any task that doesn't fit a more specific agent. (Tools: *)\n- Explore: Fast read-only search agent for locating code. Use it to find files by pattern (eg. \"src/components/**/*.tsx\"), grep for symbols or keywords (eg. \"API endpoints\"), or answer \"where is X defined / which files reference Y.\" Do NOT use it for code review, design-doc auditing, cross-file consistency checks, or open-ended analysis — it reads excerpts rather than whole files and will miss content past its read window. When calling, specify search breadth: \"quick\" for a single targeted lookup, \"medium\" for moderate exploration, or \"very thorough\" to search across multiple locations and naming conventions. (Tools: All tools except Agent, Artifact, ExitPlanMode, Edit, Write, NotebookEdit)\n- general-purpose: General-purpose agent for researching complex questions, searching for code, and executing multi-step tasks. When you are searching for a keyword or file and are not confident that you will find the right match in the first few tries use this agent to perform the search for you. (Tools: *)\n- Plan: Software architect agent for designing implementation plans. Use this when you need to plan the implementation strategy for a task. Returns step-by-step plans, identifies critical files, and considers architectural trade-offs. (Tools: All tools except Agent, Artifact, ExitPlanMode, Edit, Write, NotebookEdit)\n\nWhen you launch multiple agents for independent work, send them in a single message with multiple tool uses so they run concurrently.\n</system-reminder>\n\n<system-reminder>\nAs you answer the user's questions, you can use the following context:\n# currentDate\nToday's date is <FIXTURE-DATE>.\n\n IMPORTANT: this context may or may not be relevant to your tasks. You should not respond to this context unless it is highly relevant to your task.\n</system-reminder>\n\n\nhi",
79
85
  "permission_denials": []
80
86
  }
81
87
  }
@@ -48,7 +48,13 @@
48
48
  ],
49
49
  "output_style": "default",
50
50
  "skills": [],
51
- "plugins": []
51
+ "plugins": [],
52
+ "agents": [
53
+ "claude",
54
+ "Explore",
55
+ "general-purpose",
56
+ "Plan"
57
+ ]
52
58
  }
53
59
  },
54
60
  {
@@ -61,7 +67,7 @@
61
67
  "content": [
62
68
  {
63
69
  "type": "text",
64
- "text": "[{\"role\":\"user\",\"content\":\"<system-reminder>\\nAuto-memory (injected by the runtime, not typed by the user):\\nAuto-memory for this project lives at /winter-home/projects/-winter-fixture/memory. The directory is created on demand and there are no memory tools: read and write it with the ordinary file tools, exactly like any other directory.\\n\\n/winter-home/projects/-winter-fixture/memory/MEMORY.md is the INDEX, and only its first 200 lines / 25 KB are loaded into a session. Keep every index entry to one line; the substance belongs in the topic file it points at, which you can read on demand when it turns out to matter.\\n\\nTo record something worth having in a LATER session -- a standing preference, a correction you were given, a durable constraint of this project -- write it to its own `<slug>.md` in that directory and add a one-line pointer to the index: `- [<slug>](<slug>.md) — <one-line summary>`.\\n\\nRevise a fact by rewriting its file and its index line, never by adding a near-duplicate under a new name; remove both once it stops being true. An index full of stale near-duplicates is worse than an empty one, because it costs the same and misleads.\\n\\nDo not record what the repository already records. Code, configuration, documentation and WINTER.md are durable on their own; memory is for what is true about this project or this user and lives nowhere in the tree.\\n</system-reminder>\\n\\nfirst\"}]"
70
+ "text": "[{\"role\":\"user\",\"content\":[{\"type\":\"text\",\"text\":\"<system-reminder>\\nAvailable agent types for the Agent tool:\\n- claude: Catch-all for any task that doesn't fit a more specific agent. (Tools: *)\\n- Explore: Fast read-only search agent for locating code. Use it to find files by pattern (eg. \\\"src/components/**/*.tsx\\\"), grep for symbols or keywords (eg. \\\"API endpoints\\\"), or answer \\\"where is X defined / which files reference Y.\\\" Do NOT use it for code review, design-doc auditing, cross-file consistency checks, or open-ended analysis — it reads excerpts rather than whole files and will miss content past its read window. When calling, specify search breadth: \\\"quick\\\" for a single targeted lookup, \\\"medium\\\" for moderate exploration, or \\\"very thorough\\\" to search across multiple locations and naming conventions. (Tools: All tools except Agent, Artifact, ExitPlanMode, Edit, Write, NotebookEdit)\\n- general-purpose: General-purpose agent for researching complex questions, searching for code, and executing multi-step tasks. When you are searching for a keyword or file and are not confident that you will find the right match in the first few tries use this agent to perform the search for you. (Tools: *)\\n- Plan: Software architect agent for designing implementation plans. Use this when you need to plan the implementation strategy for a task. Returns step-by-step plans, identifies critical files, and considers architectural trade-offs. (Tools: All tools except Agent, Artifact, ExitPlanMode, Edit, Write, NotebookEdit)\\n\\nWhen you launch multiple agents for independent work, send them in a single message with multiple tool uses so they run concurrently.\\n</system-reminder>\\n\"},{\"type\":\"text\",\"text\":\"<system-reminder>\\nAs you answer the user's questions, you can use the following context:\\n# currentDate\\nToday's date is <FIXTURE-DATE>.\\n\\n IMPORTANT: this context may or may not be relevant to your tasks. You should not respond to this context unless it is highly relevant to your task.\\n</system-reminder>\\n\\n\"},{\"type\":\"text\",\"text\":\"first\"}]}]"
65
71
  }
66
72
  ]
67
73
  }
@@ -75,7 +81,7 @@
75
81
  "type": "result",
76
82
  "subtype": "success",
77
83
  "is_error": false,
78
- "result": "[{\"role\":\"user\",\"content\":\"<system-reminder>\\nAuto-memory (injected by the runtime, not typed by the user):\\nAuto-memory for this project lives at /winter-home/projects/-winter-fixture/memory. The directory is created on demand and there are no memory tools: read and write it with the ordinary file tools, exactly like any other directory.\\n\\n/winter-home/projects/-winter-fixture/memory/MEMORY.md is the INDEX, and only its first 200 lines / 25 KB are loaded into a session. Keep every index entry to one line; the substance belongs in the topic file it points at, which you can read on demand when it turns out to matter.\\n\\nTo record something worth having in a LATER session -- a standing preference, a correction you were given, a durable constraint of this project -- write it to its own `<slug>.md` in that directory and add a one-line pointer to the index: `- [<slug>](<slug>.md) — <one-line summary>`.\\n\\nRevise a fact by rewriting its file and its index line, never by adding a near-duplicate under a new name; remove both once it stops being true. An index full of stale near-duplicates is worse than an empty one, because it costs the same and misleads.\\n\\nDo not record what the repository already records. Code, configuration, documentation and WINTER.md are durable on their own; memory is for what is true about this project or this user and lives nowhere in the tree.\\n</system-reminder>\\n\\nfirst\"}]",
84
+ "result": "[{\"role\":\"user\",\"content\":[{\"type\":\"text\",\"text\":\"<system-reminder>\\nAvailable agent types for the Agent tool:\\n- claude: Catch-all for any task that doesn't fit a more specific agent. (Tools: *)\\n- Explore: Fast read-only search agent for locating code. Use it to find files by pattern (eg. \\\"src/components/**/*.tsx\\\"), grep for symbols or keywords (eg. \\\"API endpoints\\\"), or answer \\\"where is X defined / which files reference Y.\\\" Do NOT use it for code review, design-doc auditing, cross-file consistency checks, or open-ended analysis — it reads excerpts rather than whole files and will miss content past its read window. When calling, specify search breadth: \\\"quick\\\" for a single targeted lookup, \\\"medium\\\" for moderate exploration, or \\\"very thorough\\\" to search across multiple locations and naming conventions. (Tools: All tools except Agent, Artifact, ExitPlanMode, Edit, Write, NotebookEdit)\\n- general-purpose: General-purpose agent for researching complex questions, searching for code, and executing multi-step tasks. When you are searching for a keyword or file and are not confident that you will find the right match in the first few tries use this agent to perform the search for you. (Tools: *)\\n- Plan: Software architect agent for designing implementation plans. Use this when you need to plan the implementation strategy for a task. Returns step-by-step plans, identifies critical files, and considers architectural trade-offs. (Tools: All tools except Agent, Artifact, ExitPlanMode, Edit, Write, NotebookEdit)\\n\\nWhen you launch multiple agents for independent work, send them in a single message with multiple tool uses so they run concurrently.\\n</system-reminder>\\n\"},{\"type\":\"text\",\"text\":\"<system-reminder>\\nAs you answer the user's questions, you can use the following context:\\n# currentDate\\nToday's date is <FIXTURE-DATE>.\\n\\n IMPORTANT: this context may or may not be relevant to your tasks. You should not respond to this context unless it is highly relevant to your task.\\n</system-reminder>\\n\\n\"},{\"type\":\"text\",\"text\":\"first\"}]}]",
79
85
  "permission_denials": []
80
86
  }
81
87
  },
@@ -128,7 +134,13 @@
128
134
  ],
129
135
  "output_style": "default",
130
136
  "skills": [],
131
- "plugins": []
137
+ "plugins": [],
138
+ "agents": [
139
+ "claude",
140
+ "Explore",
141
+ "general-purpose",
142
+ "Plan"
143
+ ]
132
144
  }
133
145
  },
134
146
  {
@@ -141,7 +153,7 @@
141
153
  "content": [
142
154
  {
143
155
  "type": "text",
144
- "text": "[{\"role\":\"user\",\"content\":\"first\"},{\"role\":\"assistant\",\"content\":\"[{\\\"role\\\":\\\"user\\\",\\\"content\\\":\\\"<system-reminder>\\\\nAuto-memory (injected by the runtime, not typed by the user):\\\\nAuto-memory for this project lives at /winter-home/projects/-winter-fixture/memory. The directory is created on demand and there are no memory tools: read and write it with the ordinary file tools, exactly like any other directory.\\\\n\\\\n/winter-home/projects/-winter-fixture/memory/MEMORY.md is the INDEX, and only its first 200 lines / 25 KB are loaded into a session. Keep every index entry to one line; the substance belongs in the topic file it points at, which you can read on demand when it turns out to matter.\\\\n\\\\nTo record something worth having in a LATER session -- a standing preference, a correction you were given, a durable constraint of this project -- write it to its own `<slug>.md` in that directory and add a one-line pointer to the index: `- [<slug>](<slug>.md) — <one-line summary>`.\\\\n\\\\nRevise a fact by rewriting its file and its index line, never by adding a near-duplicate under a new name; remove both once it stops being true. An index full of stale near-duplicates is worse than an empty one, because it costs the same and misleads.\\\\n\\\\nDo not record what the repository already records. Code, configuration, documentation and WINTER.md are durable on their own; memory is for what is true about this project or this user and lives nowhere in the tree.\\\\n</system-reminder>\\\\n\\\\nfirst\\\"}]\"},{\"role\":\"user\",\"content\":\"<system-reminder>\\nAuto-memory (injected by the runtime, not typed by the user):\\nAuto-memory for this project lives at /winter-home/projects/-winter-fixture/memory. The directory is created on demand and there are no memory tools: read and write it with the ordinary file tools, exactly like any other directory.\\n\\n/winter-home/projects/-winter-fixture/memory/MEMORY.md is the INDEX, and only its first 200 lines / 25 KB are loaded into a session. Keep every index entry to one line; the substance belongs in the topic file it points at, which you can read on demand when it turns out to matter.\\n\\nTo record something worth having in a LATER session -- a standing preference, a correction you were given, a durable constraint of this project -- write it to its own `<slug>.md` in that directory and add a one-line pointer to the index: `- [<slug>](<slug>.md) — <one-line summary>`.\\n\\nRevise a fact by rewriting its file and its index line, never by adding a near-duplicate under a new name; remove both once it stops being true. An index full of stale near-duplicates is worse than an empty one, because it costs the same and misleads.\\n\\nDo not record what the repository already records. Code, configuration, documentation and WINTER.md are durable on their own; memory is for what is true about this project or this user and lives nowhere in the tree.\\n</system-reminder>\\n\\nsecond\"}]"
156
+ "text": "[{\"role\":\"user\",\"content\":[{\"type\":\"text\",\"text\":\"<system-reminder>\\nAvailable agent types for the Agent tool:\\n- claude: Catch-all for any task that doesn't fit a more specific agent. (Tools: *)\\n- Explore: Fast read-only search agent for locating code. Use it to find files by pattern (eg. \\\"src/components/**/*.tsx\\\"), grep for symbols or keywords (eg. \\\"API endpoints\\\"), or answer \\\"where is X defined / which files reference Y.\\\" Do NOT use it for code review, design-doc auditing, cross-file consistency checks, or open-ended analysis — it reads excerpts rather than whole files and will miss content past its read window. When calling, specify search breadth: \\\"quick\\\" for a single targeted lookup, \\\"medium\\\" for moderate exploration, or \\\"very thorough\\\" to search across multiple locations and naming conventions. (Tools: All tools except Agent, Artifact, ExitPlanMode, Edit, Write, NotebookEdit)\\n- general-purpose: General-purpose agent for researching complex questions, searching for code, and executing multi-step tasks. When you are searching for a keyword or file and are not confident that you will find the right match in the first few tries use this agent to perform the search for you. (Tools: *)\\n- Plan: Software architect agent for designing implementation plans. Use this when you need to plan the implementation strategy for a task. Returns step-by-step plans, identifies critical files, and considers architectural trade-offs. (Tools: All tools except Agent, Artifact, ExitPlanMode, Edit, Write, NotebookEdit)\\n\\nWhen you launch multiple agents for independent work, send them in a single message with multiple tool uses so they run concurrently.\\n</system-reminder>\\n\"},{\"type\":\"text\",\"text\":\"<system-reminder>\\nAs you answer the user's questions, you can use the following context:\\n# currentDate\\nToday's date is <FIXTURE-DATE>.\\n\\n IMPORTANT: this context may or may not be relevant to your tasks. You should not respond to this context unless it is highly relevant to your task.\\n</system-reminder>\\n\\n\"},{\"type\":\"text\",\"text\":\"first\"}]},{\"role\":\"assistant\",\"content\":\"[{\\\"role\\\":\\\"user\\\",\\\"content\\\":[{\\\"type\\\":\\\"text\\\",\\\"text\\\":\\\"<system-reminder>\\\\nAvailable agent types for the Agent tool:\\\\n- claude: Catch-all for any task that doesn't fit a more specific agent. (Tools: *)\\\\n- Explore: Fast read-only search agent for locating code. Use it to find files by pattern (eg. \\\\\\\"src/components/**/*.tsx\\\\\\\"), grep for symbols or keywords (eg. \\\\\\\"API endpoints\\\\\\\"), or answer \\\\\\\"where is X defined / which files reference Y.\\\\\\\" Do NOT use it for code review, design-doc auditing, cross-file consistency checks, or open-ended analysis — it reads excerpts rather than whole files and will miss content past its read window. When calling, specify search breadth: \\\\\\\"quick\\\\\\\" for a single targeted lookup, \\\\\\\"medium\\\\\\\" for moderate exploration, or \\\\\\\"very thorough\\\\\\\" to search across multiple locations and naming conventions. (Tools: All tools except Agent, Artifact, ExitPlanMode, Edit, Write, NotebookEdit)\\\\n- general-purpose: General-purpose agent for researching complex questions, searching for code, and executing multi-step tasks. When you are searching for a keyword or file and are not confident that you will find the right match in the first few tries use this agent to perform the search for you. (Tools: *)\\\\n- Plan: Software architect agent for designing implementation plans. Use this when you need to plan the implementation strategy for a task. Returns step-by-step plans, identifies critical files, and considers architectural trade-offs. (Tools: All tools except Agent, Artifact, ExitPlanMode, Edit, Write, NotebookEdit)\\\\n\\\\nWhen you launch multiple agents for independent work, send them in a single message with multiple tool uses so they run concurrently.\\\\n</system-reminder>\\\\n\\\"},{\\\"type\\\":\\\"text\\\",\\\"text\\\":\\\"<system-reminder>\\\\nAs you answer the user's questions, you can use the following context:\\\\n# currentDate\\\\nToday's date is <FIXTURE-DATE>.\\\\n\\\\n IMPORTANT: this context may or may not be relevant to your tasks. You should not respond to this context unless it is highly relevant to your task.\\\\n</system-reminder>\\\\n\\\\n\\\"},{\\\"type\\\":\\\"text\\\",\\\"text\\\":\\\"first\\\"}]}]\"},{\"role\":\"user\",\"content\":\"second\"}]"
145
157
  }
146
158
  ]
147
159
  }
@@ -155,7 +167,7 @@
155
167
  "type": "result",
156
168
  "subtype": "success",
157
169
  "is_error": false,
158
- "result": "[{\"role\":\"user\",\"content\":\"first\"},{\"role\":\"assistant\",\"content\":\"[{\\\"role\\\":\\\"user\\\",\\\"content\\\":\\\"<system-reminder>\\\\nAuto-memory (injected by the runtime, not typed by the user):\\\\nAuto-memory for this project lives at /winter-home/projects/-winter-fixture/memory. The directory is created on demand and there are no memory tools: read and write it with the ordinary file tools, exactly like any other directory.\\\\n\\\\n/winter-home/projects/-winter-fixture/memory/MEMORY.md is the INDEX, and only its first 200 lines / 25 KB are loaded into a session. Keep every index entry to one line; the substance belongs in the topic file it points at, which you can read on demand when it turns out to matter.\\\\n\\\\nTo record something worth having in a LATER session -- a standing preference, a correction you were given, a durable constraint of this project -- write it to its own `<slug>.md` in that directory and add a one-line pointer to the index: `- [<slug>](<slug>.md) — <one-line summary>`.\\\\n\\\\nRevise a fact by rewriting its file and its index line, never by adding a near-duplicate under a new name; remove both once it stops being true. An index full of stale near-duplicates is worse than an empty one, because it costs the same and misleads.\\\\n\\\\nDo not record what the repository already records. Code, configuration, documentation and WINTER.md are durable on their own; memory is for what is true about this project or this user and lives nowhere in the tree.\\\\n</system-reminder>\\\\n\\\\nfirst\\\"}]\"},{\"role\":\"user\",\"content\":\"<system-reminder>\\nAuto-memory (injected by the runtime, not typed by the user):\\nAuto-memory for this project lives at /winter-home/projects/-winter-fixture/memory. The directory is created on demand and there are no memory tools: read and write it with the ordinary file tools, exactly like any other directory.\\n\\n/winter-home/projects/-winter-fixture/memory/MEMORY.md is the INDEX, and only its first 200 lines / 25 KB are loaded into a session. Keep every index entry to one line; the substance belongs in the topic file it points at, which you can read on demand when it turns out to matter.\\n\\nTo record something worth having in a LATER session -- a standing preference, a correction you were given, a durable constraint of this project -- write it to its own `<slug>.md` in that directory and add a one-line pointer to the index: `- [<slug>](<slug>.md) — <one-line summary>`.\\n\\nRevise a fact by rewriting its file and its index line, never by adding a near-duplicate under a new name; remove both once it stops being true. An index full of stale near-duplicates is worse than an empty one, because it costs the same and misleads.\\n\\nDo not record what the repository already records. Code, configuration, documentation and WINTER.md are durable on their own; memory is for what is true about this project or this user and lives nowhere in the tree.\\n</system-reminder>\\n\\nsecond\"}]",
170
+ "result": "[{\"role\":\"user\",\"content\":[{\"type\":\"text\",\"text\":\"<system-reminder>\\nAvailable agent types for the Agent tool:\\n- claude: Catch-all for any task that doesn't fit a more specific agent. (Tools: *)\\n- Explore: Fast read-only search agent for locating code. Use it to find files by pattern (eg. \\\"src/components/**/*.tsx\\\"), grep for symbols or keywords (eg. \\\"API endpoints\\\"), or answer \\\"where is X defined / which files reference Y.\\\" Do NOT use it for code review, design-doc auditing, cross-file consistency checks, or open-ended analysis — it reads excerpts rather than whole files and will miss content past its read window. When calling, specify search breadth: \\\"quick\\\" for a single targeted lookup, \\\"medium\\\" for moderate exploration, or \\\"very thorough\\\" to search across multiple locations and naming conventions. (Tools: All tools except Agent, Artifact, ExitPlanMode, Edit, Write, NotebookEdit)\\n- general-purpose: General-purpose agent for researching complex questions, searching for code, and executing multi-step tasks. When you are searching for a keyword or file and are not confident that you will find the right match in the first few tries use this agent to perform the search for you. (Tools: *)\\n- Plan: Software architect agent for designing implementation plans. Use this when you need to plan the implementation strategy for a task. Returns step-by-step plans, identifies critical files, and considers architectural trade-offs. (Tools: All tools except Agent, Artifact, ExitPlanMode, Edit, Write, NotebookEdit)\\n\\nWhen you launch multiple agents for independent work, send them in a single message with multiple tool uses so they run concurrently.\\n</system-reminder>\\n\"},{\"type\":\"text\",\"text\":\"<system-reminder>\\nAs you answer the user's questions, you can use the following context:\\n# currentDate\\nToday's date is <FIXTURE-DATE>.\\n\\n IMPORTANT: this context may or may not be relevant to your tasks. You should not respond to this context unless it is highly relevant to your task.\\n</system-reminder>\\n\\n\"},{\"type\":\"text\",\"text\":\"first\"}]},{\"role\":\"assistant\",\"content\":\"[{\\\"role\\\":\\\"user\\\",\\\"content\\\":[{\\\"type\\\":\\\"text\\\",\\\"text\\\":\\\"<system-reminder>\\\\nAvailable agent types for the Agent tool:\\\\n- claude: Catch-all for any task that doesn't fit a more specific agent. (Tools: *)\\\\n- Explore: Fast read-only search agent for locating code. Use it to find files by pattern (eg. \\\\\\\"src/components/**/*.tsx\\\\\\\"), grep for symbols or keywords (eg. \\\\\\\"API endpoints\\\\\\\"), or answer \\\\\\\"where is X defined / which files reference Y.\\\\\\\" Do NOT use it for code review, design-doc auditing, cross-file consistency checks, or open-ended analysis — it reads excerpts rather than whole files and will miss content past its read window. When calling, specify search breadth: \\\\\\\"quick\\\\\\\" for a single targeted lookup, \\\\\\\"medium\\\\\\\" for moderate exploration, or \\\\\\\"very thorough\\\\\\\" to search across multiple locations and naming conventions. (Tools: All tools except Agent, Artifact, ExitPlanMode, Edit, Write, NotebookEdit)\\\\n- general-purpose: General-purpose agent for researching complex questions, searching for code, and executing multi-step tasks. When you are searching for a keyword or file and are not confident that you will find the right match in the first few tries use this agent to perform the search for you. (Tools: *)\\\\n- Plan: Software architect agent for designing implementation plans. Use this when you need to plan the implementation strategy for a task. Returns step-by-step plans, identifies critical files, and considers architectural trade-offs. (Tools: All tools except Agent, Artifact, ExitPlanMode, Edit, Write, NotebookEdit)\\\\n\\\\nWhen you launch multiple agents for independent work, send them in a single message with multiple tool uses so they run concurrently.\\\\n</system-reminder>\\\\n\\\"},{\\\"type\\\":\\\"text\\\",\\\"text\\\":\\\"<system-reminder>\\\\nAs you answer the user's questions, you can use the following context:\\\\n# currentDate\\\\nToday's date is <FIXTURE-DATE>.\\\\n\\\\n IMPORTANT: this context may or may not be relevant to your tasks. You should not respond to this context unless it is highly relevant to your task.\\\\n</system-reminder>\\\\n\\\\n\\\"},{\\\"type\\\":\\\"text\\\",\\\"text\\\":\\\"first\\\"}]}]\"},{\"role\":\"user\",\"content\":\"second\"}]",
159
171
  "permission_denials": []
160
172
  }
161
173
  }
@@ -48,7 +48,13 @@
48
48
  ],
49
49
  "output_style": "default",
50
50
  "skills": [],
51
- "plugins": []
51
+ "plugins": [],
52
+ "agents": [
53
+ "claude",
54
+ "Explore",
55
+ "general-purpose",
56
+ "Plan"
57
+ ]
52
58
  }
53
59
  },
54
60
  {
@@ -65,7 +71,8 @@
65
71
  "name": "Agent",
66
72
  "input": {
67
73
  "description": "message target",
68
- "prompt": "child probe text"
74
+ "prompt": "child probe text",
75
+ "run_in_background": false
69
76
  }
70
77
  }
71
78
  ]
@@ -75,6 +82,55 @@
75
82
  {
76
83
  "sequence": 2,
77
84
  "direction": "runtime-to-host",
85
+ "kind": "system/task_started",
86
+ "payload": {
87
+ "type": "system",
88
+ "subtype": "task_started",
89
+ "task_id": "TASKID_1",
90
+ "tool_use_id": "agent-call-1",
91
+ "description": "message target",
92
+ "subagent_type": "general-purpose",
93
+ "is_backgrounded": false,
94
+ "spawn_depth": 1,
95
+ "task_type": "local_agent",
96
+ "prompt": "child probe text"
97
+ }
98
+ },
99
+ {
100
+ "sequence": 3,
101
+ "direction": "runtime-to-host",
102
+ "kind": "system/task_updated",
103
+ "payload": {
104
+ "type": "system",
105
+ "subtype": "task_updated",
106
+ "task_id": "TASKID_1",
107
+ "patch": {
108
+ "status": "completed",
109
+ "end_time": "<end_time>"
110
+ }
111
+ }
112
+ },
113
+ {
114
+ "sequence": 4,
115
+ "direction": "runtime-to-host",
116
+ "kind": "system/task_notification",
117
+ "payload": {
118
+ "type": "system",
119
+ "subtype": "task_notification",
120
+ "task_id": "TASKID_1",
121
+ "tool_use_id": "agent-call-1",
122
+ "status": "completed",
123
+ "output_file": "/winter-fixture-tasks/TASKID_1.output",
124
+ "summary": "child finished",
125
+ "usage": {
126
+ "total_tokens": "<total_tokens>",
127
+ "tool_uses": 0
128
+ }
129
+ }
130
+ },
131
+ {
132
+ "sequence": 5,
133
+ "direction": "runtime-to-host",
78
134
  "kind": "user",
79
135
  "payload": {
80
136
  "type": "user",
@@ -83,14 +139,14 @@
83
139
  {
84
140
  "type": "tool_result",
85
141
  "tool_use_id": "agent-call-1",
86
- "content": "{\"agentId\":\"<scrubbed>\",\"content\":[{\"type\":\"text\",\"text\":\"child finished\"}],\"totalToolUseCount\":0,\"totalDurationMs\":\"<scrubbed>\",\"resolvedModel\":\"winter-test/echo\",\"prompt\":\"child probe text\"}"
142
+ "content": "{\"agentId\":\"<scrubbed>\",\"agentType\":\"general-purpose\",\"content\":[{\"type\":\"text\",\"text\":\"child finished\"}],\"totalToolUseCount\":0,\"totalDurationMs\":\"<scrubbed>\",\"resolvedModel\":\"winter-test/echo\",\"prompt\":\"child probe text\"}"
87
143
  }
88
144
  ]
89
145
  }
90
146
  }
91
147
  },
92
148
  {
93
- "sequence": 3,
149
+ "sequence": 6,
94
150
  "direction": "runtime-to-host",
95
151
  "kind": "assistant",
96
152
  "payload": {
@@ -111,7 +167,7 @@
111
167
  }
112
168
  },
113
169
  {
114
- "sequence": 4,
170
+ "sequence": 7,
115
171
  "direction": "runtime-to-host",
116
172
  "kind": "user",
117
173
  "payload": {
@@ -128,7 +184,7 @@
128
184
  }
129
185
  },
130
186
  {
131
- "sequence": 5,
187
+ "sequence": 8,
132
188
  "direction": "runtime-to-host",
133
189
  "kind": "assistant",
134
190
  "payload": {
@@ -144,7 +200,7 @@
144
200
  }
145
201
  },
146
202
  {
147
- "sequence": 6,
203
+ "sequence": 9,
148
204
  "direction": "runtime-to-host",
149
205
  "kind": "result",
150
206
  "payload": {
@@ -51,7 +51,13 @@
51
51
  "skills": [
52
52
  "p5probe"
53
53
  ],
54
- "plugins": []
54
+ "plugins": [],
55
+ "agents": [
56
+ "claude",
57
+ "Explore",
58
+ "general-purpose",
59
+ "Plan"
60
+ ]
55
61
  }
56
62
  },
57
63
  {
@@ -49,7 +49,13 @@
49
49
  ],
50
50
  "output_style": "default",
51
51
  "skills": [],
52
- "plugins": []
52
+ "plugins": [],
53
+ "agents": [
54
+ "claude",
55
+ "Explore",
56
+ "general-purpose",
57
+ "Plan"
58
+ ]
53
59
  }
54
60
  },
55
61
  {
@@ -49,7 +49,13 @@
49
49
  ],
50
50
  "output_style": "default",
51
51
  "skills": [],
52
- "plugins": []
52
+ "plugins": [],
53
+ "agents": [
54
+ "claude",
55
+ "Explore",
56
+ "general-purpose",
57
+ "Plan"
58
+ ]
53
59
  }
54
60
  },
55
61
  {
@@ -48,7 +48,13 @@
48
48
  ],
49
49
  "output_style": "default",
50
50
  "skills": [],
51
- "plugins": []
51
+ "plugins": [],
52
+ "agents": [
53
+ "claude",
54
+ "Explore",
55
+ "general-purpose",
56
+ "Plan"
57
+ ]
52
58
  }
53
59
  },
54
60
  {
@@ -65,7 +71,8 @@
65
71
  "name": "Agent",
66
72
  "input": {
67
73
  "description": "permission probe",
68
- "prompt": "child probe text"
74
+ "prompt": "child probe text",
75
+ "run_in_background": false
69
76
  }
70
77
  }
71
78
  ]
@@ -75,6 +82,23 @@
75
82
  {
76
83
  "sequence": 2,
77
84
  "direction": "runtime-to-host",
85
+ "kind": "system/task_started",
86
+ "payload": {
87
+ "type": "system",
88
+ "subtype": "task_started",
89
+ "task_id": "TASKID_1",
90
+ "tool_use_id": "agent-call-1",
91
+ "description": "permission probe",
92
+ "subagent_type": "general-purpose",
93
+ "is_backgrounded": false,
94
+ "spawn_depth": 1,
95
+ "task_type": "local_agent",
96
+ "prompt": "child probe text"
97
+ }
98
+ },
99
+ {
100
+ "sequence": 3,
101
+ "direction": "runtime-to-host",
78
102
  "kind": "assistant",
79
103
  "payload": {
80
104
  "type": "assistant",
@@ -83,7 +107,7 @@
83
107
  {
84
108
  "type": "tool_use",
85
109
  "id": "child-call-1",
86
- "name": "ReadNotifications",
110
+ "name": "ListAgents",
87
111
  "input": {}
88
112
  }
89
113
  ]
@@ -92,7 +116,25 @@
92
116
  }
93
117
  },
94
118
  {
95
- "sequence": 3,
119
+ "sequence": 4,
120
+ "direction": "runtime-to-host",
121
+ "kind": "system/task_progress",
122
+ "payload": {
123
+ "type": "system",
124
+ "subtype": "task_progress",
125
+ "task_id": "TASKID_1",
126
+ "tool_use_id": "agent-call-1",
127
+ "description": "permission probe",
128
+ "subagent_type": "general-purpose",
129
+ "usage": {
130
+ "total_tokens": "<total_tokens>",
131
+ "tool_uses": 1
132
+ },
133
+ "last_tool_name": "ListAgents"
134
+ }
135
+ },
136
+ {
137
+ "sequence": 5,
96
138
  "direction": "runtime-to-host",
97
139
  "kind": "user",
98
140
  "payload": {
@@ -102,7 +144,7 @@
102
144
  {
103
145
  "type": "tool_result",
104
146
  "tool_use_id": "child-call-1",
105
- "content": "{\"notifications\":[],\"remaining\":0}"
147
+ "content": "{\"listing\":\"- agent:<uuid>:<uuid> [agent/winter-agent] status=running mode=default\"}"
106
148
  }
107
149
  ]
108
150
  },
@@ -110,7 +152,7 @@
110
152
  }
111
153
  },
112
154
  {
113
- "sequence": 4,
155
+ "sequence": 6,
114
156
  "direction": "runtime-to-host",
115
157
  "kind": "assistant",
116
158
  "payload": {
@@ -127,7 +169,39 @@
127
169
  }
128
170
  },
129
171
  {
130
- "sequence": 5,
172
+ "sequence": 7,
173
+ "direction": "runtime-to-host",
174
+ "kind": "system/task_updated",
175
+ "payload": {
176
+ "type": "system",
177
+ "subtype": "task_updated",
178
+ "task_id": "TASKID_1",
179
+ "patch": {
180
+ "status": "completed",
181
+ "end_time": "<end_time>"
182
+ }
183
+ }
184
+ },
185
+ {
186
+ "sequence": 8,
187
+ "direction": "runtime-to-host",
188
+ "kind": "system/task_notification",
189
+ "payload": {
190
+ "type": "system",
191
+ "subtype": "task_notification",
192
+ "task_id": "TASKID_1",
193
+ "tool_use_id": "agent-call-1",
194
+ "status": "completed",
195
+ "output_file": "/winter-fixture-tasks/TASKID_1.output",
196
+ "summary": "child finished after its own tool call",
197
+ "usage": {
198
+ "total_tokens": "<total_tokens>",
199
+ "tool_uses": 1
200
+ }
201
+ }
202
+ },
203
+ {
204
+ "sequence": 9,
131
205
  "direction": "runtime-to-host",
132
206
  "kind": "user",
133
207
  "payload": {
@@ -137,14 +211,14 @@
137
211
  {
138
212
  "type": "tool_result",
139
213
  "tool_use_id": "agent-call-1",
140
- "content": "{\"agentId\":\"<scrubbed>\",\"content\":[{\"type\":\"text\",\"text\":\"child finished after its own tool call\"}],\"totalToolUseCount\":1,\"totalDurationMs\":\"<scrubbed>\",\"resolvedModel\":\"winter-test/echo\",\"prompt\":\"child probe text\"}"
214
+ "content": "{\"agentId\":\"<scrubbed>\",\"agentType\":\"general-purpose\",\"content\":[{\"type\":\"text\",\"text\":\"child finished after its own tool call\"}],\"totalToolUseCount\":1,\"totalDurationMs\":\"<scrubbed>\",\"resolvedModel\":\"winter-test/echo\",\"prompt\":\"child probe text\"}"
141
215
  }
142
216
  ]
143
217
  }
144
218
  }
145
219
  },
146
220
  {
147
- "sequence": 6,
221
+ "sequence": 10,
148
222
  "direction": "runtime-to-host",
149
223
  "kind": "assistant",
150
224
  "payload": {
@@ -160,7 +234,7 @@
160
234
  }
161
235
  },
162
236
  {
163
- "sequence": 7,
237
+ "sequence": 11,
164
238
  "direction": "runtime-to-host",
165
239
  "kind": "result",
166
240
  "payload": {