pythia-plsql 0.15.7__tar.gz → 0.15.9__tar.gz
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.
- {pythia_plsql-0.15.7/scripts/pythia_plsql.egg-info → pythia_plsql-0.15.9}/PKG-INFO +31 -18
- {pythia_plsql-0.15.7 → pythia_plsql-0.15.9}/README.md +30 -17
- {pythia_plsql-0.15.7 → pythia_plsql-0.15.9}/pyproject.toml +1 -1
- {pythia_plsql-0.15.7 → pythia_plsql-0.15.9}/scripts/pythia.py +401 -129
- {pythia_plsql-0.15.7 → pythia_plsql-0.15.9/scripts/pythia_plsql.egg-info}/PKG-INFO +31 -18
- {pythia_plsql-0.15.7 → pythia_plsql-0.15.9}/skills/pythia-apply/SKILL.md +12 -13
- {pythia_plsql-0.15.7 → pythia_plsql-0.15.9}/skills/pythia-autopilot/SKILL.md +4 -4
- {pythia_plsql-0.15.7 → pythia_plsql-0.15.9}/skills/pythia-deploy/SKILL.md +4 -3
- {pythia_plsql-0.15.7 → pythia_plsql-0.15.9}/skills/pythia-setup/SKILL.md +7 -4
- {pythia_plsql-0.15.7 → pythia_plsql-0.15.9}/skills/pythia-setup/reference/environment.md +6 -3
- {pythia_plsql-0.15.7 → pythia_plsql-0.15.9}/tests/test_mcp.py +24 -0
- {pythia_plsql-0.15.7 → pythia_plsql-0.15.9}/tests/test_phase3.py +1 -1
- {pythia_plsql-0.15.7 → pythia_plsql-0.15.9}/tests/test_phase6.py +310 -2
- {pythia_plsql-0.15.7 → pythia_plsql-0.15.9}/LICENSE +0 -0
- {pythia_plsql-0.15.7 → pythia_plsql-0.15.9}/queries/comment-current.sql +0 -0
- {pythia_plsql-0.15.7 → pythia_plsql-0.15.9}/queries/compile-errors.sql +0 -0
- {pythia_plsql-0.15.7 → pythia_plsql-0.15.9}/queries/current-schema.sql +0 -0
- {pythia_plsql-0.15.7 → pythia_plsql-0.15.9}/queries/db-nls.sql +0 -0
- {pythia_plsql-0.15.7 → pythia_plsql-0.15.9}/queries/db-version.sql +0 -0
- {pythia_plsql-0.15.7 → pythia_plsql-0.15.9}/queries/dependencies.sql +0 -0
- {pythia_plsql-0.15.7 → pythia_plsql-0.15.9}/queries/explain-display.sql +0 -0
- {pythia_plsql-0.15.7 → pythia_plsql-0.15.9}/queries/impact.sql +0 -0
- {pythia_plsql-0.15.7 → pythia_plsql-0.15.9}/queries/invalid-objects.sql +0 -0
- {pythia_plsql-0.15.7 → pythia_plsql-0.15.9}/queries/name-occupants.sql +0 -0
- {pythia_plsql-0.15.7 → pythia_plsql-0.15.9}/queries/object-names.sql +0 -0
- {pythia_plsql-0.15.7 → pythia_plsql-0.15.9}/queries/object-source.sql +0 -0
- {pythia_plsql-0.15.7 → pythia_plsql-0.15.9}/queries/plscope-enabled.sql +0 -0
- {pythia_plsql-0.15.7 → pythia_plsql-0.15.9}/queries/plscope-statements.sql +0 -0
- {pythia_plsql-0.15.7 → pythia_plsql-0.15.9}/queries/plscope-usages.sql +0 -0
- {pythia_plsql-0.15.7 → pythia_plsql-0.15.9}/queries/schema-settings.sql +0 -0
- {pythia_plsql-0.15.7 → pythia_plsql-0.15.9}/queries/session-privileges.sql +0 -0
- {pythia_plsql-0.15.7 → pythia_plsql-0.15.9}/queries/similar-candidates.sql +0 -0
- {pythia_plsql-0.15.7 → pythia_plsql-0.15.9}/queries/source.sql +0 -0
- {pythia_plsql-0.15.7 → pythia_plsql-0.15.9}/queries/table-comments.sql +0 -0
- {pythia_plsql-0.15.7 → pythia_plsql-0.15.9}/queries/table-indexes.sql +0 -0
- {pythia_plsql-0.15.7 → pythia_plsql-0.15.9}/queries/table-stats.sql +0 -0
- {pythia_plsql-0.15.7 → pythia_plsql-0.15.9}/queries/unindexed-fks.sql +0 -0
- {pythia_plsql-0.15.7 → pythia_plsql-0.15.9}/scripts/pythia_plsql.egg-info/SOURCES.txt +0 -0
- {pythia_plsql-0.15.7 → pythia_plsql-0.15.9}/scripts/pythia_plsql.egg-info/dependency_links.txt +0 -0
- {pythia_plsql-0.15.7 → pythia_plsql-0.15.9}/scripts/pythia_plsql.egg-info/entry_points.txt +0 -0
- {pythia_plsql-0.15.7 → pythia_plsql-0.15.9}/scripts/pythia_plsql.egg-info/requires.txt +0 -0
- {pythia_plsql-0.15.7 → pythia_plsql-0.15.9}/scripts/pythia_plsql.egg-info/top_level.txt +0 -0
- {pythia_plsql-0.15.7 → pythia_plsql-0.15.9}/setup.cfg +0 -0
- {pythia_plsql-0.15.7 → pythia_plsql-0.15.9}/skills/pythia-comment/SKILL.md +0 -0
- {pythia_plsql-0.15.7 → pythia_plsql-0.15.9}/skills/pythia-conventions/SKILL.md +0 -0
- {pythia_plsql-0.15.7 → pythia_plsql-0.15.9}/skills/pythia-explore/SKILL.md +0 -0
- {pythia_plsql-0.15.7 → pythia_plsql-0.15.9}/skills/pythia-explore/reference/data-dictionary.md +0 -0
- {pythia_plsql-0.15.7 → pythia_plsql-0.15.9}/skills/pythia-impact/SKILL.md +0 -0
- {pythia_plsql-0.15.7 → pythia_plsql-0.15.9}/skills/pythia-package/SKILL.md +0 -0
- {pythia_plsql-0.15.7 → pythia_plsql-0.15.9}/skills/pythia-package/reference/plsql-standards.md +0 -0
- {pythia_plsql-0.15.7 → pythia_plsql-0.15.9}/skills/pythia-review/SKILL.md +0 -0
- {pythia_plsql-0.15.7 → pythia_plsql-0.15.9}/skills/pythia-review/reference/antipatterns.md +0 -0
- {pythia_plsql-0.15.7 → pythia_plsql-0.15.9}/skills/pythia-skill-author/SKILL.md +0 -0
- {pythia_plsql-0.15.7 → pythia_plsql-0.15.9}/skills/pythia-spec/SKILL.md +0 -0
- {pythia_plsql-0.15.7 → pythia_plsql-0.15.9}/skills/pythia-table/SKILL.md +0 -0
- {pythia_plsql-0.15.7 → pythia_plsql-0.15.9}/skills/pythia-table/reference/ddl-standards.md +0 -0
- {pythia_plsql-0.15.7 → pythia_plsql-0.15.9}/skills/pythia-tune/SKILL.md +0 -0
- {pythia_plsql-0.15.7 → pythia_plsql-0.15.9}/skills/pythia-tune/reference/tuning-checklist.md +0 -0
- {pythia_plsql-0.15.7 → pythia_plsql-0.15.9}/skills/pythia-verify/SKILL.md +0 -0
- {pythia_plsql-0.15.7 → pythia_plsql-0.15.9}/skills/pythia-write/SKILL.md +0 -0
- {pythia_plsql-0.15.7 → pythia_plsql-0.15.9}/skills/pythia-write/reference/patterns.md +0 -0
- {pythia_plsql-0.15.7 → pythia_plsql-0.15.9}/skills/using-pythia/SKILL.md +0 -0
- {pythia_plsql-0.15.7 → pythia_plsql-0.15.9}/tests/test_install.py +0 -0
- {pythia_plsql-0.15.7 → pythia_plsql-0.15.9}/tests/test_phase1.py +0 -0
- {pythia_plsql-0.15.7 → pythia_plsql-0.15.9}/tests/test_phase2.py +0 -0
- {pythia_plsql-0.15.7 → pythia_plsql-0.15.9}/tests/test_phase5.py +0 -0
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
Metadata-Version: 2.4
|
|
2
2
|
Name: pythia-plsql
|
|
3
|
-
Version: 0.15.
|
|
3
|
+
Version: 0.15.9
|
|
4
4
|
Summary: PL/SQL development for AI agents on Oracle Database - expert data-dictionary queries, impact analysis, and a snapshot-verified write path with honest rollback.
|
|
5
5
|
License: MIT
|
|
6
6
|
Project-URL: Homepage, https://github.com/thaildhe172591/pythia
|
|
@@ -102,12 +102,15 @@ verify → report**. DDL self-commits in Oracle, so the snapshot is the only rea
|
|
|
102
102
|
undo — it runs first and no flag disables it. A content-bound token guarantees
|
|
103
103
|
what lands is byte-for-byte what was previewed, and a **developer-minted grant**
|
|
104
104
|
guarantees a person approved it at all — through a door that is always the
|
|
105
|
-
developer's
|
|
106
|
-
|
|
107
|
-
|
|
108
|
-
|
|
109
|
-
|
|
110
|
-
|
|
105
|
+
developer's, tried in order until one works. On Claude Code first: an
|
|
106
|
+
`AskUserQuestion` whose text is the card (`pythia approve --card <token>`) —
|
|
107
|
+
Claude Code's own dialog, shown in every client (terminal, desktop, web,
|
|
108
|
+
phone) and never answered by a hook or an allow rule; its **Approve**, chosen
|
|
109
|
+
in the dialog and traced through the session transcript to make sure the
|
|
110
|
+
agent did not write it, mints the one-time grant. Next, and first on Codex:
|
|
111
|
+
the `pythia_approve` tool (MCP), pythia's own card as a select prompt. Last, at
|
|
112
|
+
a console: `pythia approve <token>`. A door that fails says so and names the
|
|
113
|
+
next, and the agent moves on without asking.
|
|
111
114
|
Without that grant `apply --confirm` refuses. A headless agent cannot `--yes`
|
|
112
115
|
its own writes, cannot mint approval, and cannot loosen policy — each of those
|
|
113
116
|
takes a human, answering or typing.
|
|
@@ -201,6 +204,9 @@ each agent needs you to finish by hand.
|
|
|
201
204
|
text untouched. The rules hold even with `--no-hooks`, before a restart,
|
|
202
205
|
or while the hooks are untrusted; when the block is there, the
|
|
203
206
|
SessionStart hook adds only the live state instead of repeating the guide.
|
|
207
|
+
A block from an older pythia (upgraded, not yet re-installed) gets the
|
|
208
|
+
current guide instead, with a `NOTE` line saying it wins until `pythia
|
|
209
|
+
install` refreshes the block.
|
|
204
210
|
|
|
205
211
|
**The interpreter is chosen by what really starts pythia.** A hook that
|
|
206
212
|
cannot start fails open — Claude Code treats its error as non-blocking —
|
|
@@ -221,20 +227,25 @@ each agent needs you to finish by hand.
|
|
|
221
227
|
|
|
222
228
|
Skills land in `.claude/skills` (or `~/.claude/skills` with `-g`).
|
|
223
229
|
2. **Restart the Claude Code session** so the hooks and the MCP server load.
|
|
224
|
-
3. **Run `pythia doctor`.** It confirms the wiring and names
|
|
225
|
-
|
|
230
|
+
3. **Run `pythia doctor`.** It confirms the wiring and names the settings
|
|
231
|
+
that once made `AskUserQuestion` return without showing the question — an
|
|
226
232
|
allow rule or a skill's `allowed-tools` naming it, a PreToolUse hook with an
|
|
227
|
-
empty or `*` matcher,
|
|
228
|
-
|
|
229
|
-
|
|
233
|
+
empty or `*` matcher (in settings, or in a plugin that is installed and
|
|
234
|
+
enabled — the rest of a marketplace's plugins do not count). Current
|
|
235
|
+
Claude Code requires the dialog for `AskUserQuestion` whatever those say,
|
|
236
|
+
so they are warnings; `dontAsk` mode, which denies both chat doors, is the
|
|
237
|
+
one fail.
|
|
230
238
|
4. *Optional:* copy the allow-list and `autoMode` from
|
|
231
239
|
[`examples/claude-code-settings.example.json`](examples/claude-code-settings.example.json).
|
|
232
240
|
Those are your permission preferences, so pythia does not set them for you
|
|
233
241
|
([why](GUIDE.md#11-optional-claude-code-permission-settings)).
|
|
234
242
|
|
|
235
|
-
**Approving a change:** the agent previews with `pythia apply`,
|
|
236
|
-
`
|
|
237
|
-
|
|
243
|
+
**Approving a change:** the agent previews with `pythia apply`, asks an
|
|
244
|
+
`AskUserQuestion` carrying the card, you click **Approve**, and the agent runs
|
|
245
|
+
`apply --confirm` itself. If that dialog's answer does not count (it closed
|
|
246
|
+
while you were away, or the hook could not trace it), the agent goes on
|
|
247
|
+
unasked to the `pythia_approve` tool, then to `pythia approve <token>` for your
|
|
248
|
+
terminal.
|
|
238
249
|
|
|
239
250
|
**Working autonomously:** say so. The agent requests a lease
|
|
240
251
|
(`pythia autopilot request`), you approve its card once, and it builds —
|
|
@@ -257,7 +268,9 @@ tables, comments, packages, releases — without stopping for each write.
|
|
|
257
268
|
`pythia: connected`.
|
|
258
269
|
|
|
259
270
|
Needs **Codex ≥ v0.120** for the in-chat approval (MCP elicitation); an older
|
|
260
|
-
or headless Codex
|
|
271
|
+
or headless Codex — or any host that declines the prompt without showing it,
|
|
272
|
+
which pythia tells apart by time — falls back to the console `pythia approve
|
|
273
|
+
<token>`, and the agent says so without being asked. Do
|
|
261
274
|
**not** run Codex under `danger-full-access` — that sandbox auto-approves
|
|
262
275
|
elicitations and bypasses your Approve.
|
|
263
276
|
|
|
@@ -313,8 +326,8 @@ works just as well.
|
|
|
313
326
|
`pythia check` warns when the session runs with more power than the task needs.
|
|
314
327
|
|
|
315
328
|
The developer approval that `apply` requires is minted per agent — Claude
|
|
316
|
-
Code's `AskUserQuestion` hook,
|
|
317
|
-
console `pythia approve <token>` anywhere. How each is wired is in
|
|
329
|
+
Code's `AskUserQuestion` hook first, then the `pythia_approve` MCP tool (where
|
|
330
|
+
Codex starts), then the console `pythia approve <token>` anywhere. How each is wired is in
|
|
318
331
|
[Setting up Claude Code and Codex](#setting-up-claude-code-and-codex) above.
|
|
319
332
|
|
|
320
333
|
Per-group write policy, `.pythia/policy.json` (defaults shown):
|
|
@@ -88,12 +88,15 @@ verify → report**. DDL self-commits in Oracle, so the snapshot is the only rea
|
|
|
88
88
|
undo — it runs first and no flag disables it. A content-bound token guarantees
|
|
89
89
|
what lands is byte-for-byte what was previewed, and a **developer-minted grant**
|
|
90
90
|
guarantees a person approved it at all — through a door that is always the
|
|
91
|
-
developer's
|
|
92
|
-
|
|
93
|
-
|
|
94
|
-
|
|
95
|
-
|
|
96
|
-
|
|
91
|
+
developer's, tried in order until one works. On Claude Code first: an
|
|
92
|
+
`AskUserQuestion` whose text is the card (`pythia approve --card <token>`) —
|
|
93
|
+
Claude Code's own dialog, shown in every client (terminal, desktop, web,
|
|
94
|
+
phone) and never answered by a hook or an allow rule; its **Approve**, chosen
|
|
95
|
+
in the dialog and traced through the session transcript to make sure the
|
|
96
|
+
agent did not write it, mints the one-time grant. Next, and first on Codex:
|
|
97
|
+
the `pythia_approve` tool (MCP), pythia's own card as a select prompt. Last, at
|
|
98
|
+
a console: `pythia approve <token>`. A door that fails says so and names the
|
|
99
|
+
next, and the agent moves on without asking.
|
|
97
100
|
Without that grant `apply --confirm` refuses. A headless agent cannot `--yes`
|
|
98
101
|
its own writes, cannot mint approval, and cannot loosen policy — each of those
|
|
99
102
|
takes a human, answering or typing.
|
|
@@ -187,6 +190,9 @@ each agent needs you to finish by hand.
|
|
|
187
190
|
text untouched. The rules hold even with `--no-hooks`, before a restart,
|
|
188
191
|
or while the hooks are untrusted; when the block is there, the
|
|
189
192
|
SessionStart hook adds only the live state instead of repeating the guide.
|
|
193
|
+
A block from an older pythia (upgraded, not yet re-installed) gets the
|
|
194
|
+
current guide instead, with a `NOTE` line saying it wins until `pythia
|
|
195
|
+
install` refreshes the block.
|
|
190
196
|
|
|
191
197
|
**The interpreter is chosen by what really starts pythia.** A hook that
|
|
192
198
|
cannot start fails open — Claude Code treats its error as non-blocking —
|
|
@@ -207,20 +213,25 @@ each agent needs you to finish by hand.
|
|
|
207
213
|
|
|
208
214
|
Skills land in `.claude/skills` (or `~/.claude/skills` with `-g`).
|
|
209
215
|
2. **Restart the Claude Code session** so the hooks and the MCP server load.
|
|
210
|
-
3. **Run `pythia doctor`.** It confirms the wiring and names
|
|
211
|
-
|
|
216
|
+
3. **Run `pythia doctor`.** It confirms the wiring and names the settings
|
|
217
|
+
that once made `AskUserQuestion` return without showing the question — an
|
|
212
218
|
allow rule or a skill's `allowed-tools` naming it, a PreToolUse hook with an
|
|
213
|
-
empty or `*` matcher,
|
|
214
|
-
|
|
215
|
-
|
|
219
|
+
empty or `*` matcher (in settings, or in a plugin that is installed and
|
|
220
|
+
enabled — the rest of a marketplace's plugins do not count). Current
|
|
221
|
+
Claude Code requires the dialog for `AskUserQuestion` whatever those say,
|
|
222
|
+
so they are warnings; `dontAsk` mode, which denies both chat doors, is the
|
|
223
|
+
one fail.
|
|
216
224
|
4. *Optional:* copy the allow-list and `autoMode` from
|
|
217
225
|
[`examples/claude-code-settings.example.json`](examples/claude-code-settings.example.json).
|
|
218
226
|
Those are your permission preferences, so pythia does not set them for you
|
|
219
227
|
([why](GUIDE.md#11-optional-claude-code-permission-settings)).
|
|
220
228
|
|
|
221
|
-
**Approving a change:** the agent previews with `pythia apply`,
|
|
222
|
-
`
|
|
223
|
-
|
|
229
|
+
**Approving a change:** the agent previews with `pythia apply`, asks an
|
|
230
|
+
`AskUserQuestion` carrying the card, you click **Approve**, and the agent runs
|
|
231
|
+
`apply --confirm` itself. If that dialog's answer does not count (it closed
|
|
232
|
+
while you were away, or the hook could not trace it), the agent goes on
|
|
233
|
+
unasked to the `pythia_approve` tool, then to `pythia approve <token>` for your
|
|
234
|
+
terminal.
|
|
224
235
|
|
|
225
236
|
**Working autonomously:** say so. The agent requests a lease
|
|
226
237
|
(`pythia autopilot request`), you approve its card once, and it builds —
|
|
@@ -243,7 +254,9 @@ tables, comments, packages, releases — without stopping for each write.
|
|
|
243
254
|
`pythia: connected`.
|
|
244
255
|
|
|
245
256
|
Needs **Codex ≥ v0.120** for the in-chat approval (MCP elicitation); an older
|
|
246
|
-
or headless Codex
|
|
257
|
+
or headless Codex — or any host that declines the prompt without showing it,
|
|
258
|
+
which pythia tells apart by time — falls back to the console `pythia approve
|
|
259
|
+
<token>`, and the agent says so without being asked. Do
|
|
247
260
|
**not** run Codex under `danger-full-access` — that sandbox auto-approves
|
|
248
261
|
elicitations and bypasses your Approve.
|
|
249
262
|
|
|
@@ -299,8 +312,8 @@ works just as well.
|
|
|
299
312
|
`pythia check` warns when the session runs with more power than the task needs.
|
|
300
313
|
|
|
301
314
|
The developer approval that `apply` requires is minted per agent — Claude
|
|
302
|
-
Code's `AskUserQuestion` hook,
|
|
303
|
-
console `pythia approve <token>` anywhere. How each is wired is in
|
|
315
|
+
Code's `AskUserQuestion` hook first, then the `pythia_approve` MCP tool (where
|
|
316
|
+
Codex starts), then the console `pythia approve <token>` anywhere. How each is wired is in
|
|
304
317
|
[Setting up Claude Code and Codex](#setting-up-claude-code-and-codex) above.
|
|
305
318
|
|
|
306
319
|
Per-group write policy, `.pythia/policy.json` (defaults shown):
|
|
@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
|
|
|
4
4
|
|
|
5
5
|
[project]
|
|
6
6
|
name = "pythia-plsql"
|
|
7
|
-
version = "0.15.
|
|
7
|
+
version = "0.15.9"
|
|
8
8
|
description = "PL/SQL development for AI agents on Oracle Database - expert data-dictionary queries, impact analysis, and a snapshot-verified write path with honest rollback."
|
|
9
9
|
readme = "README.md"
|
|
10
10
|
license = { text = "MIT" }
|