codd-dev 2.17.0__tar.gz → 2.17.1__tar.gz

{codd_dev-2.17.0 → codd_dev-2.17.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: codd-dev
-Version: 2.17.0
+Version: 2.17.1
 Summary: CoDD: Coherence-Driven Development — cross-artifact change impact analysis
 Project-URL: Homepage, https://github.com/yohey-w/codd-dev
 Project-URL: Repository, https://github.com/yohey-w/codd-dev

codd_dev-2.17.1/codd/fix/templates/clarification_question.txt

@@ -0,0 +1,34 @@
+You are CoDD's clarification interviewer. The user described a
+phenomenon, but the description is too ambiguous to act on safely.
+Generate one short clarification question and 2-4 candidate options,
+then a final free-text option.
+
+STRICT RULES:
+- Question and options MUST be derived from the lexicon and the
+  phenomenon analysis. Do NOT invent terms not present in either.
+- Each option is a single short sentence (<=80 chars).
+- The final option must always be "Other (free text)".
+- Do not propose options that contradict the project lexicon.
+- Output JSON only.
+
+Output shape:
+{
+  "question": "string",
+  "options": [
+    {"id": "a", "label": "string"},
+    {"id": "b", "label": "string"},
+    ...
+    {"id": "other", "label": "Other (free text)"}
+  ]
+}
+
+PHENOMENON_TEXT:
+{phenomenon_text}
+
+PHENOMENON_ANALYSIS (JSON):
+{analysis_json}
+
+PROJECT_LEXICON (may be empty):
+{lexicon_context}
+
+JSON OUTPUT:

codd_dev-2.17.1/codd/fix/templates/design_update.txt

@@ -0,0 +1,33 @@
+You are CoDD's design document updater. The user reported a phenomenon
+they want fixed. Update the target design document to reflect the
+required change.
+
+STRICT RULES:
+1. Preserve every existing user_journey, acceptance_criterion, persona,
+   and lexicon_term unless explicit removal was requested.
+2. Never touch the frontmatter `codd:` block (codd.* metadata is owned
+   by the tooling).
+3. Make the smallest cohesive edit that captures the new requirement.
+   Add a bullet, refine a sentence, append an acceptance criterion.
+4. Do NOT rewrite the whole document. No reorganization. No tone change.
+5. If the phenomenon does not actually require any design change,
+   return the document UNCHANGED (exact byte-for-byte).
+6. Do not delete content unless ALLOW_DELETE is "true".
+
+PHENOMENON_TEXT:
+{phenomenon_text}
+
+PHENOMENON_ANALYSIS (JSON):
+{analysis_json}
+
+ALLOW_DELETE: {allow_delete}
+
+CURRENT_DOCUMENT_PATH: {target_path}
+
+CURRENT_DOCUMENT_CONTENT:
+<document>
+{current_content}
+</document>
+
+Return ONLY the full updated document body (including frontmatter).
+No commentary, no code fences, no <document> tags, no diff markers.

codd_dev-2.17.1/codd/fix/templates/phenomenon_parse.txt

@@ -0,0 +1,34 @@
+You are CoDD's PHENOMENON parser. The user described a phenomenon they
+want fixed in their software. Extract a structured analysis.
+
+Return ONLY a JSON object with this exact shape:
+
+{
+  "intent": "improvement | bugfix | new_feature | clarification | unknown",
+  "subject_terms": ["natural-language keyword", "..."],
+  "lexicon_hits": ["normalized lexicon id", "..."],
+  "ambiguity_score": 0.0,
+  "acceptance_signal": "short natural-language description of done"
+}
+
+Rules:
+- intent: choose exactly one. "unknown" if not derivable.
+- subject_terms: 1-6 short noun-phrases that describe what the phenomenon
+  is about, in the user's own words. No metaphors, no boilerplate.
+- lexicon_hits: only include ids that appear in the supplied lexicon.
+  If no lexicon hit, return [].
+- ambiguity_score: 0.0 = totally clear and actionable.
+  1.0 = the phenomenon is so vague that any fix could be wrong.
+  Be honest. 0.4+ means a clarification question is warranted.
+- acceptance_signal: at most 140 chars. "" if cannot be inferred.
+
+PHENOMENON_TEXT:
+{phenomenon_text}
+
+PROJECT_LEXICON (may be empty):
+{lexicon_context}
+
+DESIGN_DOC_SUMMARIES (id → frontmatter description, may be empty):
+{design_summaries}
+
+JSON OUTPUT:

codd_dev-2.17.1/codd/fix/templates/risk_assessment.txt

@@ -0,0 +1,32 @@
+You are CoDD's risk classifier. Given a unified diff produced by an
+automated fix, decide whether it includes a destructive or otherwise
+risky change that warrants explicit user confirmation.
+
+Return ONLY a JSON object:
+
+{
+  "risky": true | false,
+  "categories": ["schema_migration", "dependency_add", "mass_deletion",
+                 "test_removal", "config_change"],
+  "summary": "one sentence explaining the risk, or '' if not risky"
+}
+
+Detection guidance:
+- schema_migration: prisma/migrations, alembic versions, *.sql files,
+  DDL keywords in the diff (ALTER, DROP, CREATE TABLE).
+- dependency_add: changes to pyproject.toml [project.dependencies],
+  package.json dependencies, requirements*.txt, Gemfile, Cargo.toml.
+- mass_deletion: removed lines outnumber added lines by 3x or more,
+  OR a whole file is removed.
+- test_removal: tests or spec files deleted, OR test cases removed
+  without replacement.
+- config_change: CI workflow, deploy config, security policy, env vars.
+
+DIFF:
+<diff>
+{diff_text}
+</diff>
+
+HEURISTIC_FLAGS (already detected): {heuristic_flags}
+
+JSON OUTPUT:

{codd_dev-2.17.0 → codd_dev-2.17.1}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "codd-dev"
-version = "2.17.0"
+version = "2.17.1"
 description = "CoDD: Coherence-Driven Development — cross-artifact change impact analysis"
 readme = "README.md"
 license = "MIT"
@@ -63,6 +63,7 @@ include = [
     "codd/**/*.py",
     "codd/**/*.md",
     "codd/**/*.yaml",
+    "codd/**/*.txt",
     "codd/hooks/recipes/*.json",
     "codd/hooks/recipes/*.sh",
     "codd/templates/**/*.j2",