pythia-plsql 0.3.4__tar.gz → 0.3.5__tar.gz

{pythia_plsql-0.3.4/scripts/pythia_plsql.egg-info → pythia_plsql-0.3.5}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: pythia-plsql
-Version: 0.3.4
+Version: 0.3.5
 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.3.4 → pythia_plsql-0.3.5}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "pythia-plsql"
-version = "0.3.4"
+version = "0.3.5"
 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.3.4 → pythia_plsql-0.3.5/scripts/pythia_plsql.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: pythia-plsql
-Version: 0.3.4
+Version: 0.3.5
 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.3.4 → pythia_plsql-0.3.5}/skills/pythia-explore/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: pythia-explore
-description: Use when you need to understand anything in an Oracle schema - finding objects, reading PL/SQL source, signatures, table columns, DDL, searching code, or asking who uses what. ALSO use when a .sql file, dump, export, migration script or repo copy of an object appears to answer the question already, including when the developer points you at one: those files drift from the database and are wrong in ways that read as correct. The database is the only source of truth.
+description: Use when you need to understand anything in an Oracle schema - finding objects, reading PL/SQL source, signatures, table columns, DDL, searching code, or asking who uses what. ALSO use when a .sql file, dump, export, migration script or repo copy of an object appears to answer the question already, including one the developer points you at - because those files drift from the database and are wrong in ways that read as correct. The database is the only source of truth.
 ---
 
 # Exploring the Schema

{pythia_plsql-0.3.4 → pythia_plsql-0.3.5}/tests/test_phase5.py

@@ -54,6 +54,33 @@ def test_frontmatter_is_valid_and_triggering():
         assert len(desc) <= 1024, f"{name}: description too long ({len(desc)})"
 
 
+def test_frontmatter_is_parseable_yaml():
+    """A description holding an unquoted ": " is not valid YAML, and the
+    agent harness then falls back to the H1 heading — the skill keeps its
+    name but loses its trigger, so it silently stops firing. This shipped
+    once; it does not ship twice. Checked without PyYAML: the suites run on
+    the stdlib alone.
+    """
+    for name in sorted(EXPECTED):
+        path = SKILLS / name / "SKILL.md"
+        if not path.is_file():
+            continue
+        m = re.match(r"^---\n(.*?)\n---\n", path.read_text(encoding="utf-8"),
+                     re.S)
+        assert m, f"{name}: no YAML frontmatter"
+        for line in m.group(1).splitlines():
+            km = re.match(r"^([A-Za-z_][\w.]*):\s+(.*)$", line)
+            if not km:
+                continue            # continuation or nested line
+            value = km.group(2)
+            if value[:1] in "\"'":
+                continue            # quoted: a colon inside is fine
+            assert ": " not in value, (
+                f"{name}: frontmatter '{km.group(1)}' holds an unquoted "
+                f"': ' — YAML reads that as a nested mapping and the field "
+                f"is lost. Rephrase or quote the value.")
+
+
 def test_skill_bodies_stay_within_budget():
     for name in sorted(EXPECTED):
         path = SKILLS / name / "SKILL.md"