@yahyahammad/venastine 0.2.0 → 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.
Files changed (152) hide show
  1. package/.env.example +9 -4
  2. package/CONFIG_ARCHITECTURE.md +2030 -0
  3. package/LICENSE +201 -201
  4. package/NOTICE +1 -1
  5. package/README.md +1034 -895
  6. package/agents/builtin/build.md +73 -0
  7. package/agents/builtin/compactor.md +75 -75
  8. package/agents/builtin/explore.md +77 -77
  9. package/agents/builtin/general.md +80 -0
  10. package/agents/builtin/pipeline-reviewer.md +100 -100
  11. package/agents/builtin/plan.md +106 -88
  12. package/agents/builtin/review.md +74 -74
  13. package/agents/builtin/test.md +65 -0
  14. package/agents/builtin/writer.md +67 -0
  15. package/agents/manager.py +68 -2
  16. package/agents/subagent_tool.py +472 -238
  17. package/agents/tui_commands.py +238 -151
  18. package/bin/venastine.mjs +150 -4
  19. package/bin/venastine.py +71 -0
  20. package/cli_commands.py +838 -0
  21. package/config.py +95 -1198
  22. package/config.yaml +1103 -0
  23. package/config_edit.py +1301 -0
  24. package/config_schema.py +971 -0
  25. package/config_update.py +749 -0
  26. package/core/agent_activity.py +256 -118
  27. package/core/ansi.py +452 -0
  28. package/core/approval.py +137 -115
  29. package/core/call_view.py +364 -0
  30. package/core/cancel.py +121 -0
  31. package/core/chatgpt_auth.py +747 -0
  32. package/core/claims_view.py +107 -0
  33. package/core/client.py +2715 -1559
  34. package/core/commands.py +460 -0
  35. package/core/compaction.py +1735 -971
  36. package/core/config_loader.py +1982 -1563
  37. package/core/connect.py +686 -0
  38. package/core/events.py +123 -61
  39. package/core/file_mentions.py +280 -0
  40. package/core/interaction.py +411 -328
  41. package/core/line_pattern.py +128 -0
  42. package/core/loop.py +2566 -1490
  43. package/core/memory.py +482 -370
  44. package/core/pipeline_models.py +190 -176
  45. package/core/provider_errors.py +234 -0
  46. package/core/reasoning/authorization.py +130 -130
  47. package/core/reasoning/base.py +219 -219
  48. package/core/reasoning/confidence_scoring.py +484 -468
  49. package/core/reasoning/events.py +149 -149
  50. package/core/reasoning/json_retry.py +19 -1
  51. package/core/reasoning/orchestrator.py +1561 -1382
  52. package/core/reasoning/output_writer.py +345 -286
  53. package/core/reasoning/payload_validation.py +524 -398
  54. package/core/reasoning/pipeline_storage.py +88 -22
  55. package/core/reasoning/review.py +659 -615
  56. package/core/reasoning/scholar.py +458 -434
  57. package/core/reasoning/source_corpus.py +433 -327
  58. package/core/reasoning/source_scoring.py +855 -855
  59. package/core/replay.py +315 -183
  60. package/core/session.py +36 -12
  61. package/core/session_view.py +259 -0
  62. package/core/session_wake.py +259 -0
  63. package/core/shell_sessions.py +1553 -0
  64. package/core/workspace_trust.py +1 -1
  65. package/credentials.py +148 -20
  66. package/database.py +333 -252
  67. package/{PRIVACY.md → docs/PRIVACY.md} +78 -66
  68. package/docs/SECURITY.md +108 -0
  69. package/docs/THIRD_PARTY_NOTICES.md +148 -0
  70. package/env_secrets.py +50 -9
  71. package/json_store.py +343 -123
  72. package/logging_setup.py +295 -185
  73. package/main.py +3433 -1961
  74. package/mcp_client/client.py +733 -499
  75. package/mcp_client/config.py +126 -21
  76. package/mcp_client/registration.py +343 -182
  77. package/memories/manager.py +147 -132
  78. package/memories/tui_commands.py +319 -244
  79. package/package.json +303 -73
  80. package/project_init/config_files.py +282 -278
  81. package/project_init/generator.py +728 -564
  82. package/project_init/manifest.py +18 -6
  83. package/project_init/tui_commands.py +147 -144
  84. package/prompts/critic_pass.md +24 -24
  85. package/prompts/revalidate.md +25 -25
  86. package/prompts/revise.md +2 -0
  87. package/prompts/source_grounding.md +66 -66
  88. package/prompts/system_prompts.py +316 -262
  89. package/providers.json.example +4 -2
  90. package/pyproject.toml +149 -100
  91. package/requirements.txt +295 -72
  92. package/safety/policy_enforcement.py +1082 -746
  93. package/security/askpass.py +419 -0
  94. package/security/capability.py +207 -177
  95. package/security/confine.py +484 -0
  96. package/security/hosted.py +182 -0
  97. package/security/permissions.py +237 -190
  98. package/security/posture.py +124 -12
  99. package/security/protected_paths.py +501 -309
  100. package/security/sandbox.py +4108 -985
  101. package/security/secrets.py +855 -0
  102. package/skills/builtin/math/formal-specification.md +67 -67
  103. package/skills/builtin/math/numerical-methods.md +66 -66
  104. package/skills/builtin/research/experiment-design.md +62 -62
  105. package/skills/builtin/research/reproducibility.md +55 -55
  106. package/skills/builtin/research/source-evaluation.md +70 -70
  107. package/skills/builtin/research/statistical-inference.md +63 -63
  108. package/skills/builtin/research/technical-writing.md +59 -59
  109. package/skills/builtin/software/code-review.md +61 -61
  110. package/skills/builtin/software/debugging.md +61 -61
  111. package/skills/builtin/software/test-design.md +67 -67
  112. package/skills/tui_commands.py +110 -111
  113. package/storage.py +1338 -1005
  114. package/tools/base.py +161 -1
  115. package/tools/builtin/_math_common.py +667 -377
  116. package/tools/builtin/_net_common.py +225 -19
  117. package/tools/builtin/arxiv.py +497 -39
  118. package/tools/builtin/ask_user.py +231 -213
  119. package/tools/builtin/discrete_math.py +35 -4
  120. package/tools/builtin/fetch_url.py +371 -153
  121. package/tools/builtin/file_ops.py +720 -412
  122. package/tools/builtin/geometry.py +48 -12
  123. package/tools/builtin/get_time.py +2 -2
  124. package/tools/builtin/linear_algebra.py +66 -23
  125. package/tools/builtin/load_skill.py +76 -66
  126. package/tools/builtin/logic.py +171 -12
  127. package/tools/builtin/pin.py +227 -193
  128. package/tools/builtin/probability_stats.py +12 -16
  129. package/tools/builtin/project_docs.py +464 -405
  130. package/tools/builtin/remember.py +175 -158
  131. package/tools/builtin/shell.py +980 -461
  132. package/tools/builtin/shell_sessions.py +613 -0
  133. package/tools/builtin/symbolic_math.py +80 -10
  134. package/tools/builtin/todo.py +149 -147
  135. package/tools/builtin/web_search.py +191 -13
  136. package/tools/context.py +159 -136
  137. package/tools/isolation.py +107 -34
  138. package/tools/registry.py +1242 -925
  139. package/tui/app.py +8318 -4100
  140. package/tui/app.tcss +747 -556
  141. package/tui/commands.py +26 -170
  142. package/tui/diffs.py +34 -13
  143. package/tui/history.py +128 -128
  144. package/tui/hosted_driver.py +102 -0
  145. package/tui/markdown.py +1329 -1279
  146. package/tui/meters.py +364 -268
  147. package/tui/ravens.py +146 -146
  148. package/tui/screens.py +1255 -943
  149. package/tui/themes.py +599 -559
  150. package/tui/widgets.py +3813 -2332
  151. package/SECURITY.md +0 -88
  152. package/THIRD_PARTY_NOTICES.md +0 -100
@@ -1,130 +1,130 @@
1
- """
2
- core/reasoning/authorization.py
3
-
4
- ROADMAP_v2 §25. The pipeline's POLICY about pre-flight grants -- which
5
- tools may be offered, and how a user's answer is parsed.
6
-
7
- core/approval.py holds the data shapes and core/loop.py enforces them.
8
- This file answers the two questions that are specific to the research
9
- pipeline, and both shells (main.py's flag, tui/app.py's picker) consume it
10
- so the CLI and the TUI cannot drift into offering different sets.
11
-
12
- Why the pipeline needs its own answer at all: it is the harness's highest
13
- prompt-injection surface by construction. It fetches web pages and feeds
14
- them to a model that then chooses tools, unattended, across ten passes.
15
- §23 reasoned the same way when it decided the question tool denies
16
- headless -- "an injected question from fetched web content would be least
17
- noticed" there.
18
- """
19
-
20
- import logging
21
-
22
- logger = logging.getLogger(__name__)
23
-
24
-
25
- # What both shells say when nothing in this run can be granted (#106).
26
- #
27
- # One string, two callers, for the same reason the module exists: they
28
- # drifted, and the TUI's version was FALSE where it fired. It said "no
29
- # approval-gated tool is AVAILABLE to this run" when two were -- they
30
- # simply could not be pre-granted, which is a different sentence and the
31
- # only one either shell is in a position to make.
32
- #
33
- # This module already kept the two from offering different SETS. What it
34
- # had never been given is what they say about an empty one.
35
- NOTHING_TO_GRANT = (
36
- "No approval-gated tool in this run can be granted up front, so there "
37
- "is nothing to authorise. Gated tools are still asked about per call "
38
- "wherever something can answer."
39
- )
40
-
41
-
42
- # "The flag was given with no value -- ask me which." A distinct object
43
- # rather than "" so an explicitly empty list (--grant-tools "") stays an
44
- # empty GRANT rather than becoming a prompt. Defined here, not in either
45
- # shell, because both compare against it and two sentinels would compare
46
- # unequal while looking identical.
47
- GRANT_PICKER = object()
48
-
49
-
50
- def candidates(context=None) -> list[tuple[str, str]]:
51
- """(name, description) for every tool a pipeline grant could cover.
52
-
53
- Three filters, and the composition is the point:
54
- * advertised and approval-gated -- i.e. exactly what the headless
55
- rule hides today. Offering anything else would be offering a grant
56
- for a tool that never needed one.
57
- * registry.grantable -- a param-dependent gate was never consented
58
- to by name (R2).
59
- * grant_policy is GRANT_ANYWHERE (R13). This is the STRICT half of
60
- the pair: a GRANT_SIGNOFF_ONLY tool may be pre-granted by a human
61
- answering about one named agent for one turn, and may not be
62
- pre-granted to ten unattended passes on one launch-time tick.
63
-
64
- That third filter used to be a frozenset in this module, which is
65
- exactly how #67 and #133 happened: agents/manager.py could not see it,
66
- so the §18 sign-off and this function held different ideas of what a
67
- grant covers, and a tool registered after the set was written
68
- (write_project_doc, §24) joined the picker without anyone being asked.
69
- The answer now lives on the tool and both callers read it.
70
-
71
- On a default install this returns an EMPTY list, and that is correct
72
- rather than a regression: every built-in is either ungated, param-
73
- dependent, or excluded by policy. The population this exists for is
74
- MCP tools -- allowed but approval-gated by default (§17 decision D),
75
- no approval_check, and named at connection time.
76
-
77
- Descriptions come from the tool's own schema because they are the only
78
- signal available: MCP exposes no read-only/write metadata, so nothing
79
- can tell the user that one granted tool searches a library and another
80
- posts to a channel. Showing what a tool says it does is the whole of
81
- informed consent here, which is also why the grant is per-tool (R1)
82
- rather than one yes covering the set.
83
- """
84
- from tools.base import GRANT_ANYWHERE
85
- from tools.registry import registry
86
-
87
- out = []
88
- for name in sorted(registry.headless_hidden(context)):
89
- if (not registry.grantable(name)
90
- or registry.grant_policy(name) != GRANT_ANYWHERE):
91
- continue
92
- spec = registry._tools.get(name)
93
- description = ""
94
- if spec is not None:
95
- description = (spec.schema or {}).get("description", "") or ""
96
- out.append((name, description.strip().splitlines()[0]
97
- if description.strip() else ""))
98
- return out
99
-
100
-
101
- class GrantSpecError(ValueError):
102
- """A --grant-tools value naming something that cannot be granted."""
103
-
104
-
105
- def parse_grant_spec(text: str, offered) -> set:
106
- """Turn a comma-separated --grant-tools value into a set of names.
107
-
108
- RAISES on an unknown name rather than dropping it. A typo'd tool would
109
- otherwise produce an empty or partial grant, the run would proceed
110
- looking authorised, and the pass would report that a tool it was
111
- supposed to have was unavailable -- with the actual cause three layers
112
- away. The same argument D24 settled for undeclared permissions: an
113
- authorization mistake must be loud at the point it is made.
114
-
115
- `offered` is candidates()' output (or any iterable of names), so what a
116
- flag may name and what a picker may show are the same set by
117
- construction.
118
- """
119
- allowed = {n if isinstance(n, str) else n[0] for n in offered}
120
- names = {part.strip() for part in (text or "").split(",") if part.strip()}
121
- unknown = sorted(names - allowed)
122
- if unknown:
123
- raise GrantSpecError(
124
- f"cannot grant {', '.join(unknown)}: "
125
- + (f"grantable tools are {', '.join(sorted(allowed))}"
126
- if allowed else
127
- "no tool in this run needs a grant, so there is nothing to "
128
- "authorise")
129
- )
130
- return names
1
+ """
2
+ core/reasoning/authorization.py
3
+
4
+ ROADMAP_v2 §25. The pipeline's POLICY about pre-flight grants -- which
5
+ tools may be offered, and how a user's answer is parsed.
6
+
7
+ core/approval.py holds the data shapes and core/loop.py enforces them.
8
+ This file answers the two questions that are specific to the research
9
+ pipeline, and both shells (main.py's flag, tui/app.py's picker) consume it
10
+ so the CLI and the TUI cannot drift into offering different sets.
11
+
12
+ Why the pipeline needs its own answer at all: it is the harness's highest
13
+ prompt-injection surface by construction. It fetches web pages and feeds
14
+ them to a model that then chooses tools, unattended, across ten passes.
15
+ §23 reasoned the same way when it decided the question tool denies
16
+ headless -- "an injected question from fetched web content would be least
17
+ noticed" there.
18
+ """
19
+
20
+ import logging
21
+
22
+ logger = logging.getLogger(__name__)
23
+
24
+
25
+ # What both shells say when nothing in this run can be granted (#106).
26
+ #
27
+ # One string, two callers, for the same reason the module exists: they
28
+ # drifted, and the TUI's version was FALSE where it fired. It said "no
29
+ # approval-gated tool is AVAILABLE to this run" when two were -- they
30
+ # simply could not be pre-granted, which is a different sentence and the
31
+ # only one either shell is in a position to make.
32
+ #
33
+ # This module already kept the two from offering different SETS. What it
34
+ # had never been given is what they say about an empty one.
35
+ NOTHING_TO_GRANT = (
36
+ "No approval-gated tool in this run can be granted up front, so there "
37
+ "is nothing to authorise. Gated tools are still asked about per call "
38
+ "wherever something can answer."
39
+ )
40
+
41
+
42
+ # "The flag was given with no value -- ask me which." A distinct object
43
+ # rather than "" so an explicitly empty list (--grant-tools "") stays an
44
+ # empty GRANT rather than becoming a prompt. Defined here, not in either
45
+ # shell, because both compare against it and two sentinels would compare
46
+ # unequal while looking identical.
47
+ GRANT_PICKER = object()
48
+
49
+
50
+ def candidates(context=None) -> list[tuple[str, str]]:
51
+ """(name, description) for every tool a pipeline grant could cover.
52
+
53
+ Three filters, and the composition is the point:
54
+ * advertised and approval-gated -- i.e. exactly what the headless
55
+ rule hides today. Offering anything else would be offering a grant
56
+ for a tool that never needed one.
57
+ * registry.grantable -- a param-dependent gate was never consented
58
+ to by name (R2).
59
+ * grant_policy is GRANT_ANYWHERE (R13). This is the STRICT half of
60
+ the pair: a GRANT_SIGNOFF_ONLY tool may be pre-granted by a human
61
+ answering about one named agent for one turn, and may not be
62
+ pre-granted to ten unattended passes on one launch-time tick.
63
+
64
+ That third filter used to be a frozenset in this module, which is
65
+ exactly how #67 and #133 happened: agents/manager.py could not see it,
66
+ so the §18 sign-off and this function held different ideas of what a
67
+ grant covers, and a tool registered after the set was written
68
+ (write_project_doc, §24) joined the picker without anyone being asked.
69
+ The answer now lives on the tool and both callers read it.
70
+
71
+ On a default install this returns an EMPTY list, and that is correct
72
+ rather than a regression: every built-in is either ungated, param-
73
+ dependent, or excluded by policy. The population this exists for is
74
+ MCP tools -- allowed but approval-gated by default (§17 decision D),
75
+ no approval_check, and named at connection time.
76
+
77
+ Descriptions come from the tool's own schema because they are the only
78
+ signal available: MCP exposes no read-only/write metadata, so nothing
79
+ can tell the user that one granted tool searches a library and another
80
+ posts to a channel. Showing what a tool says it does is the whole of
81
+ informed consent here, which is also why the grant is per-tool (R1)
82
+ rather than one yes covering the set.
83
+ """
84
+ from tools.base import GRANT_ANYWHERE
85
+ from tools.registry import registry
86
+
87
+ out = []
88
+ for name in sorted(registry.headless_hidden(context)):
89
+ if (not registry.grantable(name)
90
+ or registry.grant_policy(name) != GRANT_ANYWHERE):
91
+ continue
92
+ spec = registry._tools.get(name)
93
+ description = ""
94
+ if spec is not None:
95
+ description = (spec.schema or {}).get("description", "") or ""
96
+ out.append((name, description.strip().splitlines()[0]
97
+ if description.strip() else ""))
98
+ return out
99
+
100
+
101
+ class GrantSpecError(ValueError):
102
+ """A --grant-tools value naming something that cannot be granted."""
103
+
104
+
105
+ def parse_grant_spec(text: str, offered) -> set:
106
+ """Turn a comma-separated --grant-tools value into a set of names.
107
+
108
+ RAISES on an unknown name rather than dropping it. A typo'd tool would
109
+ otherwise produce an empty or partial grant, the run would proceed
110
+ looking authorised, and the pass would report that a tool it was
111
+ supposed to have was unavailable -- with the actual cause three layers
112
+ away. The same argument D24 settled for undeclared permissions: an
113
+ authorization mistake must be loud at the point it is made.
114
+
115
+ `offered` is candidates()' output (or any iterable of names), so what a
116
+ flag may name and what a picker may show are the same set by
117
+ construction.
118
+ """
119
+ allowed = {n if isinstance(n, str) else n[0] for n in offered}
120
+ names = {part.strip() for part in (text or "").split(",") if part.strip()}
121
+ unknown = sorted(names - allowed)
122
+ if unknown:
123
+ raise GrantSpecError(
124
+ f"cannot grant {', '.join(unknown)}: "
125
+ + (f"grantable tools are {', '.join(sorted(allowed))}"
126
+ if allowed else
127
+ "no tool in this run needs a grant, so there is nothing to "
128
+ "authorise")
129
+ )
130
+ return names