pythia-plsql 0.6.0__tar.gz → 0.6.1__tar.gz

{pythia_plsql-0.6.0/scripts/pythia_plsql.egg-info → pythia_plsql-0.6.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: pythia-plsql
-Version: 0.6.0
+Version: 0.6.1
 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.
 License: MIT
 Project-URL: Homepage, https://github.com/thaildhe172591/pythia

{pythia_plsql-0.6.0 → pythia_plsql-0.6.1}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "pythia-plsql"
-version = "0.6.0"
+version = "0.6.1"
 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."
 readme = "README.md"
 license = { text = "MIT" }

{pythia_plsql-0.6.0 → pythia_plsql-0.6.1}/scripts/pythia.py

@@ -2000,6 +2000,10 @@ Nothing here writes. Reading is free; guessing is not.
 
   the problem's shape     deps · impact · plscope     the exact graph, not a skim
   the schema's truth      src · args · cols · ddl · errors · invalid · check · ls · grep · sql
+  what you can reach      connections - names, users, targets. NEVER open
+                          connections.json yourself: it holds passwords, a
+                          permission gate should stop you, and this command
+                          is the answer you were reaching for.
   the house style         conventions (--scan / --check) · the project's conventions.md
   how it is done here     similar · history            neighbours to imitate, versions that exist
 
@@ -2038,6 +2042,59 @@ This page is the contract; follow it as written.
 """
 
 
+def connection_summary(cfg):
+    """Everything about the configured connections except the secrets.
+
+    An agent has to know which connections exist. Without a sanctioned way to
+    ask, it reads connections.json itself — which is exactly the access a
+    permission classifier should stop, and did. So this exists, and it is
+    built to be provably safe: fields are copied in by name, never by
+    iterating the entry, so a key added to the config later cannot leak
+    through here by accident.
+    """
+    cfg = dict(cfg or {})
+    default = cfg.pop("default", None)
+    rows = []
+    for name, entry in cfg.items():
+        if not isinstance(entry, dict):
+            continue
+        dsn = entry.get("dsn") or ""
+        if not dsn and entry.get("host"):
+            svc = entry.get("service_name") or entry.get("sid") or ""
+            dsn = f"{entry['host']}:{entry.get('port', 1521)}"
+            if svc:
+                dsn += f"/{svc}"
+        user = str(entry.get("user") or "")
+        rows.append({
+            "name": name,
+            "user": user,
+            "target": dsn or "\u2014",
+            "schema": (entry.get("schema") or user.split("[")[-1].rstrip("]")
+                       or "\u2014").upper(),
+            "default": isinstance(default, str) and default.upper() == name.upper(),
+        })
+    return rows
+
+
+def cmd_connections(conn, schema, ns):
+    cfg, _ = find_config(pathlib.Path.cwd(), os.environ)
+    rows = connection_summary(cfg)
+    if ns.json:
+        print(json.dumps(rows, indent=2))
+        return
+    if not rows:
+        print("No connections configured. "
+              f"{invocation()} install scaffolds .pythia/connections.json.")
+        return
+    print(f"{'':1} {'NAME':<16} {'USER':<26} {'SCHEMA':<20} TARGET")
+    for r in rows:
+        mark = "*" if r["default"] else " "
+        print(f"{mark} {r['name']:<16} {r['user']:<26} {r['schema']:<20} "
+              f"{r['target']}")
+    print("\n* default. Passwords are never printed — this command reads the "
+          "config so you\n  do not have to open it. Pick one with --conn NAME.")
+
+
 def cmd_guide(conn, schema, ns):
     print(OPERATING_GUIDE)
 
@@ -2435,11 +2492,11 @@ COMMANDS = {"check": cmd_check, "ls": cmd_ls, "src": cmd_src, "args": cmd_args,
             "invalid": cmd_invalid, "errors": cmd_errors, "deps": cmd_deps,
             "impact": cmd_impact, "similar": cmd_similar, "plscope": cmd_plscope,
             "policy": cmd_policy, "journal": cmd_journal, "apply": cmd_apply,
-            "conventions": cmd_conventions, "guide": cmd_guide, "install": cmd_install,
+            "conventions": cmd_conventions, "guide": cmd_guide, "connections": cmd_connections, "install": cmd_install,
             "unistr": cmd_unistr, "agent-user": cmd_agent_user,
             "history": cmd_history}
 
-NO_DB_COMMANDS = {"policy", "journal", "install", "unistr", "guide",
+NO_DB_COMMANDS = {"policy", "journal", "install", "unistr", "guide", "connections",
                   "history"}
 
 
@@ -2537,6 +2594,9 @@ def build_parser():
                    help="apply without stopping; the full preview still prints and journals")
     s.add_argument("--depth", type=int, default=3,
                    help="impact depth for the preview (default 3)")
+    sub.add_parser("connections", parents=[common()],
+                   help="list configured connections — names, users, "
+                        "targets; never passwords")
     sub.add_parser("guide", parents=[common()],
                    help="the operating model: Learn, Ask, Do — the whole "
                         "harness on one page, no database needed")

{pythia_plsql-0.6.0 → pythia_plsql-0.6.1/scripts/pythia_plsql.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: pythia-plsql
-Version: 0.6.0
+Version: 0.6.1
 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.
 License: MIT
 Project-URL: Homepage, https://github.com/thaildhe172591/pythia

{pythia_plsql-0.6.0 → pythia_plsql-0.6.1}/skills/pythia-setup/SKILL.md

@@ -85,7 +85,7 @@ until you want it.
 
 | File | Created by | What it does |
 |---|---|---|
-| `connections.json` | `pythia install` | Where to connect. Holds credentials; gitignored. |
+| `connections.json` | `pythia install` | Where to connect. **Holds passwords — never open it**; `pythia connections` lists names, users, schemas and targets with no secrets. Gitignored. |
 | `journal/` | first write or snapshot | Every captured version, with a runnable rollback per entry. |
 | `conventions.json` | `pythia conventions --init` | Naming patterns per object type. Every apply preview warns when a new name drifts. |
 | `conventions.md` | `pythia conventions --init` | The house rules in prose. **`pythia-write` reads this before writing anything**, and it outranks the generic patterns this pack ships with. |

{pythia_plsql-0.6.0 → pythia_plsql-0.6.1}/tests/test_phase1.py

@@ -327,6 +327,46 @@ def test_oracle_account_taken_from_a_proxy_connect_string():
     assert pythia.authenticating_account(None) is None
 
 
+SECRET = "hunter2-do-not-leak"
+
+
+def _cfg():
+    return {
+        "dev": {"host": "db.example.com", "port": 1521,
+                "service_name": "orcl", "user": "app_agent[app_owner]",
+                "password": SECRET, "schema": "APP_OWNER"},
+        "stage": {"dsn": "stage.example.com:1521/orcl", "user": "u2",
+                  "password": SECRET},
+        "default": "dev",
+    }
+
+
+def test_connection_summary_never_carries_a_secret():
+    """An agent needs to know which connections exist. Until it could ask,
+    it parsed connections.json itself -- which is exactly the read a
+    permission classifier should block. This is the sanctioned answer, so it
+    must be provably secret-free, in every field and both output modes."""
+    import json
+    rows = pythia.connection_summary(_cfg())
+    blob = json.dumps(rows)
+    assert SECRET not in blob
+    assert "password" not in blob.lower()
+    names = [r["name"] for r in rows]
+    assert names == ["dev", "stage"]          # the "default" key is not one
+    dev = rows[0]
+    assert dev["default"] is True and rows[1]["default"] is False
+    assert dev["user"] == "app_agent[app_owner]"     # proxy shape is safe to show
+    assert dev["target"] == "db.example.com:1521/orcl"
+    assert rows[1]["target"] == "stage.example.com:1521/orcl"   # dsn form
+    assert dev["schema"] == "APP_OWNER"
+
+
+def test_connection_summary_survives_a_thin_entry():
+    rows = pythia.connection_summary({"env": {"user": "u"}})
+    assert rows[0]["target"] == "—" and rows[0]["schema"] == "U"
+    assert pythia.connection_summary(None) == []
+
+
 def main():
     failed = 0
     for name, fn in sorted(globals().items()):

{pythia_plsql-0.6.0 → pythia_plsql-0.6.1}/tests/test_phase5.py

@@ -145,6 +145,28 @@ def test_every_skill_declares_its_phase():
             f"{name}: phase must name Learn/Ask/Do, got {m.group(1)!r}"
 
 
+def test_no_manifest_hardcodes_a_stale_skill_count():
+    """The pack grew from seven skills to eight and three shipped manifests
+    still said seven. Counting in prose is a contradiction waiting to happen,
+    so the check is: no manifest states a number the code can disprove."""
+    import json
+    n = len(EXPECTED)
+    words = {7: "seven", 8: "eight", 9: "nine"}
+    stale = [w for k, w in words.items() if k != n]
+    for rel in (".claude-plugin/marketplace.json", "npm/package.json",
+                "npm/README.md"):
+        text = (ROOT / rel).read_text(encoding="utf-8").lower()
+        for word in stale:
+            assert word + " skill" not in text and word + "-skill" not in text, \
+                f"{rel} claims {word} skills; there are {n}"
+    mk = json.loads((ROOT / ".claude-plugin/marketplace.json")
+                    .read_text(encoding="utf-8"))
+    declared = {p.rsplit("/", 1)[-1] for p in mk["plugins"][0]["skills"]}
+    assert declared == EXPECTED, (
+        f"marketplace.json and the pack disagree: "
+        f"missing {sorted(EXPECTED - declared)}, extra {sorted(declared - EXPECTED)}")
+
+
 def main():
     failed = 0
     for name, fn in sorted(globals().items()):