@yahyahammad/venastine 0.3.8 → 0.3.9
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.
- package/.env.example +19 -19
- package/CONFIG_ARCHITECTURE.md +2030 -2002
- package/LICENSE +201 -201
- package/README.md +1034 -1034
- package/agents/builtin/compactor.md +75 -75
- package/agents/builtin/explore.md +77 -77
- package/agents/builtin/pipeline-reviewer.md +100 -100
- package/agents/builtin/plan.md +106 -106
- package/agents/builtin/review.md +74 -74
- package/agents/manager.py +261 -261
- package/agents/subagent_tool.py +472 -472
- package/agents/tui_commands.py +238 -146
- package/bin/venastine.mjs +528 -528
- package/bin/venastine.py +71 -71
- package/cli_commands.py +838 -835
- package/config.yaml +13 -0
- package/config_edit.py +1301 -1301
- package/config_schema.py +971 -966
- package/config_update.py +749 -749
- package/core/agent_activity.py +256 -256
- package/core/ansi.py +452 -452
- package/core/approval.py +137 -137
- package/core/call_view.py +364 -364
- package/core/cancel.py +121 -121
- package/core/chatgpt_auth.py +747 -747
- package/core/claims_view.py +107 -107
- package/core/client.py +2715 -2715
- package/core/commands.py +460 -454
- package/core/compaction.py +1735 -1735
- package/core/config_loader.py +1982 -1982
- package/core/connect.py +686 -686
- package/core/events.py +123 -123
- package/core/file_mentions.py +280 -280
- package/core/interaction.py +411 -411
- package/core/loop.py +2566 -2566
- package/core/memory.py +482 -482
- package/core/pipeline_models.py +190 -190
- package/core/provider_errors.py +234 -234
- package/core/reasoning/authorization.py +130 -130
- package/core/reasoning/base.py +219 -219
- package/core/reasoning/confidence_scoring.py +484 -484
- package/core/reasoning/events.py +149 -149
- package/core/reasoning/orchestrator.py +1561 -1561
- package/core/reasoning/output_writer.py +345 -345
- package/core/reasoning/payload_validation.py +524 -524
- package/core/reasoning/pipeline_storage.py +427 -427
- package/core/reasoning/scholar.py +458 -458
- package/core/reasoning/source_corpus.py +433 -433
- package/core/reasoning/source_scoring.py +855 -855
- package/core/replay.py +315 -315
- package/core/shell_sessions.py +1553 -1553
- package/credentials.py +307 -307
- package/database.py +333 -333
- package/docs/PRIVACY.md +78 -78
- package/docs/SECURITY.md +108 -108
- package/docs/THIRD_PARTY_NOTICES.md +148 -148
- package/env_secrets.py +118 -118
- package/json_store.py +343 -343
- package/logging_setup.py +295 -295
- package/main.py +3433 -3433
- package/mcp_client/client.py +733 -733
- package/mcp_client/config.py +484 -484
- package/mcp_client/registration.py +343 -343
- package/memories/manager.py +147 -147
- package/memories/tui_commands.py +319 -239
- package/package.json +303 -303
- package/project_init/config_files.py +282 -282
- package/project_init/generator.py +728 -728
- package/project_init/manifest.py +418 -418
- package/project_init/tui_commands.py +147 -147
- package/prompts/critic_pass.md +24 -24
- package/prompts/revalidate.md +25 -25
- package/prompts/revise.md +17 -17
- package/prompts/source_grounding.md +66 -66
- package/prompts/system_prompts.py +316 -316
- package/providers.json.example +94 -94
- package/pyproject.toml +149 -149
- package/requirements.txt +295 -295
- package/safety/policy_enforcement.py +1082 -1082
- package/security/askpass.py +419 -419
- package/security/capability.py +207 -207
- package/security/confine.py +484 -484
- package/security/hosted.py +182 -182
- package/security/permissions.py +237 -237
- package/security/protected_paths.py +501 -501
- package/security/sandbox.py +4108 -4108
- package/skills/builtin/math/formal-specification.md +67 -67
- package/skills/builtin/math/numerical-methods.md +66 -66
- package/skills/builtin/research/experiment-design.md +62 -62
- package/skills/builtin/research/reproducibility.md +55 -55
- package/skills/builtin/research/source-evaluation.md +70 -70
- package/skills/builtin/research/statistical-inference.md +63 -63
- package/skills/builtin/research/technical-writing.md +59 -59
- package/skills/builtin/software/code-review.md +61 -61
- package/skills/builtin/software/debugging.md +61 -61
- package/skills/builtin/software/test-design.md +67 -67
- package/skills/tui_commands.py +110 -110
- package/storage.py +1338 -1338
- package/tools/base.py +465 -465
- package/tools/builtin/_math_common.py +667 -667
- package/tools/builtin/_net_common.py +267 -267
- package/tools/builtin/arxiv.py +681 -681
- package/tools/builtin/fetch_url.py +371 -371
- package/tools/builtin/file_ops.py +720 -720
- package/tools/builtin/geometry.py +184 -184
- package/tools/builtin/load_skill.py +76 -76
- package/tools/builtin/pin.py +227 -227
- package/tools/builtin/probability_stats.py +224 -224
- package/tools/builtin/project_docs.py +464 -464
- package/tools/builtin/remember.py +175 -175
- package/tools/builtin/shell.py +980 -980
- package/tools/builtin/todo.py +149 -149
- package/tools/builtin/web_search.py +328 -328
- package/tools/context.py +159 -159
- package/tools/isolation.py +387 -387
- package/tools/registry.py +1242 -1242
- package/tui/app.py +8318 -8307
- package/tui/app.tcss +747 -739
- package/tui/commands.py +26 -26
- package/tui/diffs.py +286 -286
- package/tui/history.py +128 -128
- package/tui/hosted_driver.py +102 -102
- package/tui/markdown.py +1329 -1329
- package/tui/meters.py +364 -364
- package/tui/ravens.py +146 -146
- package/tui/screens.py +1255 -1197
- package/tui/themes.py +599 -599
- package/tui/widgets.py +3813 -3796
package/core/reasoning/events.py
CHANGED
|
@@ -1,149 +1,149 @@
|
|
|
1
|
-
"""
|
|
2
|
-
core/reasoning/events.py
|
|
3
|
-
|
|
4
|
-
PipelineEvent is the single event type yielded by
|
|
5
|
-
core.reasoning.orchestrator.stream_deep_research_pipeline() as the
|
|
6
|
-
ten-pass research pipeline progresses. Consumers (the CLI's research
|
|
7
|
-
mode, the TUI's /research worker) iterate the generator and render what
|
|
8
|
-
they care about; run_pipeline_to_completion() drains it for callers that
|
|
9
|
-
only need the finished PipelineRun.
|
|
10
|
-
|
|
11
|
-
WHY THIS IS A SEPARATE TYPE FROM core.events.LoopEvent (ROADMAP_v2 §22
|
|
12
|
-
§22 AC4, decision P1). §22 required this decision be made and recorded
|
|
13
|
-
BEFORE any event was added, precisely so nobody discovered the problem at
|
|
14
|
-
§23. Three shapes were considered:
|
|
15
|
-
|
|
16
|
-
1. Add fields to LoopEvent. Rejected. LoopEvent is a flat dataclass
|
|
17
|
-
with an "exactly one field is populated" convention documented in a
|
|
18
|
-
docstring rather than in the type. That was right for six kinds;
|
|
19
|
-
§22 adds seven of a different family and §23 adds more, at which
|
|
20
|
-
point ~15 optional fields whose valid combinations live in prose
|
|
21
|
-
stops paying for itself.
|
|
22
|
-
2. A tagged union for both. Rejected as disproportionate: it rewrites
|
|
23
|
-
every `if event.token_delta:` read in tui/app.py, core/loop.py and
|
|
24
|
-
the streaming tests -- a §13-scale breakage inside a §22 change.
|
|
25
|
-
3. A separate, KIND-DISCRIMINATED type. Chosen. The two families have
|
|
26
|
-
different consumers and different lifetimes: a LoopEvent describes
|
|
27
|
-
one model call's progress and lives for a turn, a PipelineEvent
|
|
28
|
-
describes a ten-pass run and lives for the run. The `kind` field
|
|
29
|
-
puts the discriminator in the data rather than in a convention, so
|
|
30
|
-
adding a kind cannot silently widen what "exactly one field" means.
|
|
31
|
-
|
|
32
|
-
The two types deliberately do NOT compose, and ROADMAP_v2 §26 did not
|
|
33
|
-
change that. §22's P2 said a pass's LoopEvents are not forwarded up, on
|
|
34
|
-
the premise that a pass's internals are not worth seeing; a real ten-pass
|
|
35
|
-
run disproved the premise (a pass making fourteen tool calls over several
|
|
36
|
-
minutes was indistinguishable from one that had hung). So §26 amends P2:
|
|
37
|
-
core/reasoning/orchestrator.py now iterates
|
|
38
|
-
RunAgentLoop.stream_deep_research_mode() and TRANSLATES a chosen subset of
|
|
39
|
-
its LoopEvents into the pipeline kinds below.
|
|
40
|
-
|
|
41
|
-
Translated, not forwarded -- and the distinction is the whole amendment. A
|
|
42
|
-
consumer of this generator still receives exactly one event type, so no
|
|
43
|
-
`if event.token_delta:` read exists anywhere outside core/loop.py and the
|
|
44
|
-
streaming tests, which is what P1 and P2 were jointly protecting.
|
|
45
|
-
core/client.py, core/reasoning/json_retry.py and review.py's internals
|
|
46
|
-
remain untouched.
|
|
47
|
-
|
|
48
|
-
KNOWN LIMIT, stated rather than fixed: json_retry.py reaches the model via
|
|
49
|
-
continue_conversation(), which drains its own loop internally, so tool
|
|
50
|
-
calls made during a corrective JSON retry produce no tool_call event. The
|
|
51
|
-
retry itself is still visible -- that module appends a trace line per
|
|
52
|
-
failed parse, which _Progress's watermark carries as a trace_line.
|
|
53
|
-
|
|
54
|
-
ERROR HANDLING: there is deliberately no error variant, matching
|
|
55
|
-
core/events.py for the same reason. Exceptions raised mid-pipeline
|
|
56
|
-
propagate out of the generator unchanged, so the orchestrator's
|
|
57
|
-
`except Exception: update_pipeline_run(..., status="failed"); raise`
|
|
58
|
-
keeps working exactly as it did when the function was synchronous.
|
|
59
|
-
Turning failures into data-shaped events would require every consumer to
|
|
60
|
-
know to unpack and re-raise them.
|
|
61
|
-
"""
|
|
62
|
-
|
|
63
|
-
from dataclasses import dataclass
|
|
64
|
-
from typing import Any, Optional
|
|
65
|
-
|
|
66
|
-
# Every kind stream_deep_research_pipeline() can yield. Named here rather
|
|
67
|
-
# than left implicit in the emission sites so a consumer can be written
|
|
68
|
-
# against the list, and so an unknown kind in a test is a typo rather
|
|
69
|
-
# than a silently-ignored event.
|
|
70
|
-
PIPELINE_EVENT_KINDS = (
|
|
71
|
-
"pass_start", # pass_id -- an LLM-backed pass is about to run
|
|
72
|
-
"pass_complete", # pass_id (+ ok/text) -- it returned. ok=False
|
|
73
|
-
# marks a pass that ENDED BADLY (#115/E14): text
|
|
74
|
-
# carries a short reason, mirroring tool_result,
|
|
75
|
-
# and no success line may be printed for it. A
|
|
76
|
-
# skipped ensemble candidate resolves this way
|
|
77
|
-
# while the run continues; a fatal pass emits it
|
|
78
|
-
# before its exception propagates.
|
|
79
|
-
"trace_line", # text -- one line appended to PipelineRun.trace
|
|
80
|
-
"claim_extracted", # claim_id + text -- Pass 2 produced a claim
|
|
81
|
-
"claim_tiered", # claim_id + tier -- Pass 5 (or a 6b round) scored it
|
|
82
|
-
"retry", # claim_id + attempt -- Pass 6a revised a claim
|
|
83
|
-
"run_complete", # run -- the terminal event, carrying the PipelineRun
|
|
84
|
-
# --- §26 ---------------------------------------------------------
|
|
85
|
-
"stage", # pass_id -- a ZERO-LLM stage completed. Pass 5 and
|
|
86
|
-
# 6c are passes by the pipeline's numbering and
|
|
87
|
-
# stages by their cost: they make no model call,
|
|
88
|
-
# so they complete instantly and can never be
|
|
89
|
-
# meaningfully "running". Consumers distinguish
|
|
90
|
-
# them by THIS kind (tui/widgets.py's is_stage,
|
|
91
|
-
# main.py's '..'), never by matching pass-id
|
|
92
|
-
# strings -- #84 deleted CODE_STAGES, an unused
|
|
93
|
-
# list of those strings whose only future was to
|
|
94
|
-
# drift away from the orchestrator's _stage()
|
|
95
|
-
# call sites while looking like a contract.
|
|
96
|
-
"tool_call", # pass_id + tool + text -- a pass invoked a tool
|
|
97
|
-
"tool_result", # pass_id + tool + ok (+ text when it failed)
|
|
98
|
-
"pass_activity", # pass_id + chars -- output streamed so far, throttled
|
|
99
|
-
)
|
|
100
|
-
|
|
101
|
-
# There is deliberately NO "step" kind. §26 set out to report which model
|
|
102
|
-
# call a pass was on, and _run() has no step marker to read: within one
|
|
103
|
-
# step it yields tool_call_start/tool_result in pairs, and BETWEEN steps it
|
|
104
|
-
# yields nothing at all unless the model happened to stream text. Inferring
|
|
105
|
-
# a boundary from that interleaving would be a guess presented as a fact,
|
|
106
|
-
# and growing LoopEvent to carry a real one is what P1's test forbids.
|
|
107
|
-
#
|
|
108
|
-
# So a consumer counts tool_call events itself -- derivation, not a second
|
|
109
|
-
# writer of related data -- and pass_activity covers the other half: a pass
|
|
110
|
-
# that calls no tools (Pass 1, final synthesis) still proves it is alive by
|
|
111
|
-
# how much it has written.
|
|
112
|
-
|
|
113
|
-
|
|
114
|
-
@dataclass
|
|
115
|
-
class PipelineEvent:
|
|
116
|
-
"""One event yielded by stream_deep_research_pipeline().
|
|
117
|
-
|
|
118
|
-
`kind` says which of the fields below are meaningful; the rest stay
|
|
119
|
-
None. See PIPELINE_EVENT_KINDS for the mapping.
|
|
120
|
-
|
|
121
|
-
This type GROWS with its kinds, which is what P1 chose it for. The
|
|
122
|
-
contrast is LoopEvent, whose "exactly one field is populated" rule
|
|
123
|
-
lives in a docstring -- so an EIGHTH field there (it has seven: six
|
|
124
|
-
payload fields plus stop_reason) would silently widen a convention
|
|
125
|
-
nothing checks, and a test fails if one appears. Here the
|
|
126
|
-
discriminator is in the data, so a reader of `kind` cannot be wrong
|
|
127
|
-
about which fields to trust.
|
|
128
|
-
"""
|
|
129
|
-
|
|
130
|
-
kind: str
|
|
131
|
-
pass_id: Optional[str] = None
|
|
132
|
-
text: Optional[str] = None
|
|
133
|
-
claim_id: Optional[str] = None
|
|
134
|
-
tier: Optional[str] = None
|
|
135
|
-
attempt: Optional[int] = None
|
|
136
|
-
# §26. `text` carries the tool's redacted param digest on a tool_call
|
|
137
|
-
# and the error message on a failed tool_result -- one field for "the
|
|
138
|
-
# human-readable detail", rather than two more that are each set on one
|
|
139
|
-
# kind.
|
|
140
|
-
tool: Optional[str] = None
|
|
141
|
-
ok: Optional[bool] = None
|
|
142
|
-
# Running total of characters the pass has streamed, on pass_activity.
|
|
143
|
-
# A total rather than a delta, so a consumer that drops an event (or
|
|
144
|
-
# attaches late) still renders the right number.
|
|
145
|
-
chars: Optional[int] = None
|
|
146
|
-
# PipelineRun on the terminal event. Typed Any to keep this module
|
|
147
|
-
# importable from anywhere without dragging base.py in behind it --
|
|
148
|
-
# the same reason LoopEvent.final_response is Any.
|
|
149
|
-
run: Optional[Any] = None
|
|
1
|
+
"""
|
|
2
|
+
core/reasoning/events.py
|
|
3
|
+
|
|
4
|
+
PipelineEvent is the single event type yielded by
|
|
5
|
+
core.reasoning.orchestrator.stream_deep_research_pipeline() as the
|
|
6
|
+
ten-pass research pipeline progresses. Consumers (the CLI's research
|
|
7
|
+
mode, the TUI's /research worker) iterate the generator and render what
|
|
8
|
+
they care about; run_pipeline_to_completion() drains it for callers that
|
|
9
|
+
only need the finished PipelineRun.
|
|
10
|
+
|
|
11
|
+
WHY THIS IS A SEPARATE TYPE FROM core.events.LoopEvent (ROADMAP_v2 §22
|
|
12
|
+
§22 AC4, decision P1). §22 required this decision be made and recorded
|
|
13
|
+
BEFORE any event was added, precisely so nobody discovered the problem at
|
|
14
|
+
§23. Three shapes were considered:
|
|
15
|
+
|
|
16
|
+
1. Add fields to LoopEvent. Rejected. LoopEvent is a flat dataclass
|
|
17
|
+
with an "exactly one field is populated" convention documented in a
|
|
18
|
+
docstring rather than in the type. That was right for six kinds;
|
|
19
|
+
§22 adds seven of a different family and §23 adds more, at which
|
|
20
|
+
point ~15 optional fields whose valid combinations live in prose
|
|
21
|
+
stops paying for itself.
|
|
22
|
+
2. A tagged union for both. Rejected as disproportionate: it rewrites
|
|
23
|
+
every `if event.token_delta:` read in tui/app.py, core/loop.py and
|
|
24
|
+
the streaming tests -- a §13-scale breakage inside a §22 change.
|
|
25
|
+
3. A separate, KIND-DISCRIMINATED type. Chosen. The two families have
|
|
26
|
+
different consumers and different lifetimes: a LoopEvent describes
|
|
27
|
+
one model call's progress and lives for a turn, a PipelineEvent
|
|
28
|
+
describes a ten-pass run and lives for the run. The `kind` field
|
|
29
|
+
puts the discriminator in the data rather than in a convention, so
|
|
30
|
+
adding a kind cannot silently widen what "exactly one field" means.
|
|
31
|
+
|
|
32
|
+
The two types deliberately do NOT compose, and ROADMAP_v2 §26 did not
|
|
33
|
+
change that. §22's P2 said a pass's LoopEvents are not forwarded up, on
|
|
34
|
+
the premise that a pass's internals are not worth seeing; a real ten-pass
|
|
35
|
+
run disproved the premise (a pass making fourteen tool calls over several
|
|
36
|
+
minutes was indistinguishable from one that had hung). So §26 amends P2:
|
|
37
|
+
core/reasoning/orchestrator.py now iterates
|
|
38
|
+
RunAgentLoop.stream_deep_research_mode() and TRANSLATES a chosen subset of
|
|
39
|
+
its LoopEvents into the pipeline kinds below.
|
|
40
|
+
|
|
41
|
+
Translated, not forwarded -- and the distinction is the whole amendment. A
|
|
42
|
+
consumer of this generator still receives exactly one event type, so no
|
|
43
|
+
`if event.token_delta:` read exists anywhere outside core/loop.py and the
|
|
44
|
+
streaming tests, which is what P1 and P2 were jointly protecting.
|
|
45
|
+
core/client.py, core/reasoning/json_retry.py and review.py's internals
|
|
46
|
+
remain untouched.
|
|
47
|
+
|
|
48
|
+
KNOWN LIMIT, stated rather than fixed: json_retry.py reaches the model via
|
|
49
|
+
continue_conversation(), which drains its own loop internally, so tool
|
|
50
|
+
calls made during a corrective JSON retry produce no tool_call event. The
|
|
51
|
+
retry itself is still visible -- that module appends a trace line per
|
|
52
|
+
failed parse, which _Progress's watermark carries as a trace_line.
|
|
53
|
+
|
|
54
|
+
ERROR HANDLING: there is deliberately no error variant, matching
|
|
55
|
+
core/events.py for the same reason. Exceptions raised mid-pipeline
|
|
56
|
+
propagate out of the generator unchanged, so the orchestrator's
|
|
57
|
+
`except Exception: update_pipeline_run(..., status="failed"); raise`
|
|
58
|
+
keeps working exactly as it did when the function was synchronous.
|
|
59
|
+
Turning failures into data-shaped events would require every consumer to
|
|
60
|
+
know to unpack and re-raise them.
|
|
61
|
+
"""
|
|
62
|
+
|
|
63
|
+
from dataclasses import dataclass
|
|
64
|
+
from typing import Any, Optional
|
|
65
|
+
|
|
66
|
+
# Every kind stream_deep_research_pipeline() can yield. Named here rather
|
|
67
|
+
# than left implicit in the emission sites so a consumer can be written
|
|
68
|
+
# against the list, and so an unknown kind in a test is a typo rather
|
|
69
|
+
# than a silently-ignored event.
|
|
70
|
+
PIPELINE_EVENT_KINDS = (
|
|
71
|
+
"pass_start", # pass_id -- an LLM-backed pass is about to run
|
|
72
|
+
"pass_complete", # pass_id (+ ok/text) -- it returned. ok=False
|
|
73
|
+
# marks a pass that ENDED BADLY (#115/E14): text
|
|
74
|
+
# carries a short reason, mirroring tool_result,
|
|
75
|
+
# and no success line may be printed for it. A
|
|
76
|
+
# skipped ensemble candidate resolves this way
|
|
77
|
+
# while the run continues; a fatal pass emits it
|
|
78
|
+
# before its exception propagates.
|
|
79
|
+
"trace_line", # text -- one line appended to PipelineRun.trace
|
|
80
|
+
"claim_extracted", # claim_id + text -- Pass 2 produced a claim
|
|
81
|
+
"claim_tiered", # claim_id + tier -- Pass 5 (or a 6b round) scored it
|
|
82
|
+
"retry", # claim_id + attempt -- Pass 6a revised a claim
|
|
83
|
+
"run_complete", # run -- the terminal event, carrying the PipelineRun
|
|
84
|
+
# --- §26 ---------------------------------------------------------
|
|
85
|
+
"stage", # pass_id -- a ZERO-LLM stage completed. Pass 5 and
|
|
86
|
+
# 6c are passes by the pipeline's numbering and
|
|
87
|
+
# stages by their cost: they make no model call,
|
|
88
|
+
# so they complete instantly and can never be
|
|
89
|
+
# meaningfully "running". Consumers distinguish
|
|
90
|
+
# them by THIS kind (tui/widgets.py's is_stage,
|
|
91
|
+
# main.py's '..'), never by matching pass-id
|
|
92
|
+
# strings -- #84 deleted CODE_STAGES, an unused
|
|
93
|
+
# list of those strings whose only future was to
|
|
94
|
+
# drift away from the orchestrator's _stage()
|
|
95
|
+
# call sites while looking like a contract.
|
|
96
|
+
"tool_call", # pass_id + tool + text -- a pass invoked a tool
|
|
97
|
+
"tool_result", # pass_id + tool + ok (+ text when it failed)
|
|
98
|
+
"pass_activity", # pass_id + chars -- output streamed so far, throttled
|
|
99
|
+
)
|
|
100
|
+
|
|
101
|
+
# There is deliberately NO "step" kind. §26 set out to report which model
|
|
102
|
+
# call a pass was on, and _run() has no step marker to read: within one
|
|
103
|
+
# step it yields tool_call_start/tool_result in pairs, and BETWEEN steps it
|
|
104
|
+
# yields nothing at all unless the model happened to stream text. Inferring
|
|
105
|
+
# a boundary from that interleaving would be a guess presented as a fact,
|
|
106
|
+
# and growing LoopEvent to carry a real one is what P1's test forbids.
|
|
107
|
+
#
|
|
108
|
+
# So a consumer counts tool_call events itself -- derivation, not a second
|
|
109
|
+
# writer of related data -- and pass_activity covers the other half: a pass
|
|
110
|
+
# that calls no tools (Pass 1, final synthesis) still proves it is alive by
|
|
111
|
+
# how much it has written.
|
|
112
|
+
|
|
113
|
+
|
|
114
|
+
@dataclass
|
|
115
|
+
class PipelineEvent:
|
|
116
|
+
"""One event yielded by stream_deep_research_pipeline().
|
|
117
|
+
|
|
118
|
+
`kind` says which of the fields below are meaningful; the rest stay
|
|
119
|
+
None. See PIPELINE_EVENT_KINDS for the mapping.
|
|
120
|
+
|
|
121
|
+
This type GROWS with its kinds, which is what P1 chose it for. The
|
|
122
|
+
contrast is LoopEvent, whose "exactly one field is populated" rule
|
|
123
|
+
lives in a docstring -- so an EIGHTH field there (it has seven: six
|
|
124
|
+
payload fields plus stop_reason) would silently widen a convention
|
|
125
|
+
nothing checks, and a test fails if one appears. Here the
|
|
126
|
+
discriminator is in the data, so a reader of `kind` cannot be wrong
|
|
127
|
+
about which fields to trust.
|
|
128
|
+
"""
|
|
129
|
+
|
|
130
|
+
kind: str
|
|
131
|
+
pass_id: Optional[str] = None
|
|
132
|
+
text: Optional[str] = None
|
|
133
|
+
claim_id: Optional[str] = None
|
|
134
|
+
tier: Optional[str] = None
|
|
135
|
+
attempt: Optional[int] = None
|
|
136
|
+
# §26. `text` carries the tool's redacted param digest on a tool_call
|
|
137
|
+
# and the error message on a failed tool_result -- one field for "the
|
|
138
|
+
# human-readable detail", rather than two more that are each set on one
|
|
139
|
+
# kind.
|
|
140
|
+
tool: Optional[str] = None
|
|
141
|
+
ok: Optional[bool] = None
|
|
142
|
+
# Running total of characters the pass has streamed, on pass_activity.
|
|
143
|
+
# A total rather than a delta, so a consumer that drops an event (or
|
|
144
|
+
# attaches late) still renders the right number.
|
|
145
|
+
chars: Optional[int] = None
|
|
146
|
+
# PipelineRun on the terminal event. Typed Any to keep this module
|
|
147
|
+
# importable from anywhere without dragging base.py in behind it --
|
|
148
|
+
# the same reason LoopEvent.final_response is Any.
|
|
149
|
+
run: Optional[Any] = None
|