devtime-ei 0.2.0__tar.gz → 0.4.0__tar.gz

{devtime_ei-0.2.0 → devtime_ei-0.4.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: devtime-ei
-Version: 0.2.0
+Version: 0.4.0
 Summary: Local-first Engineering Intelligence for software repositories
 Author-email: Aviad Shakargi <aviad94@gmail.com>
 Maintainer-email: Aviad Shakargi <aviad94@gmail.com>
@@ -8,7 +8,7 @@ License: Apache-2.0
 Project-URL: Homepage, https://github.com/Shakargy/devtime
 Project-URL: Repository, https://github.com/Shakargy/devtime
 Project-URL: Issues, https://github.com/Shakargy/devtime/issues
-Project-URL: Release Notes, https://github.com/Shakargy/devtime/releases/tag/v0.2.0
+Project-URL: Release Notes, https://github.com/Shakargy/devtime/releases/tag/v0.4.0
 Project-URL: Demo, https://youtu.be/1Hiu3Y9J_SI
 Keywords: devtools,cli,static-analysis,repository-analysis,engineering-intelligence,local-first
 Classifier: Development Status :: 3 - Alpha
@@ -317,8 +317,8 @@ Contradictions:
 ```
 
 Statuses are SUPPORTED, WEAK, CONTRADICTED, or UNKNOWN; contradictions always
-show both sides; changed evidence marks a claim STALE. One built-in claim ships
-in v0.2. See **[VERIFICATION.md](VERIFICATION.md)**.
+show both sides; changed evidence marks a claim STALE. Two built-in claims ship
+(billing webhook signatures, JWT authentication). See **[VERIFICATION.md](VERIFICATION.md)**.
 
 ## Example output
 

{devtime_ei-0.2.0 → devtime_ei-0.4.0}/README.md

@@ -278,8 +278,8 @@ Contradictions:
 ```
 
 Statuses are SUPPORTED, WEAK, CONTRADICTED, or UNKNOWN; contradictions always
-show both sides; changed evidence marks a claim STALE. One built-in claim ships
-in v0.2. See **[VERIFICATION.md](VERIFICATION.md)**.
+show both sides; changed evidence marks a claim STALE. Two built-in claims ship
+(billing webhook signatures, JWT authentication). See **[VERIFICATION.md](VERIFICATION.md)**.
 
 ## Example output
 

{devtime_ei-0.2.0 → devtime_ei-0.4.0}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "devtime-ei"
-version = "0.2.0"
+version = "0.4.0"
 description = "Local-first Engineering Intelligence for software repositories"
 readme = "README.md"
 requires-python = ">=3.11"
@@ -50,7 +50,7 @@ dev = [
 Homepage = "https://github.com/Shakargy/devtime"
 Repository = "https://github.com/Shakargy/devtime"
 Issues = "https://github.com/Shakargy/devtime/issues"
-"Release Notes" = "https://github.com/Shakargy/devtime/releases/tag/v0.2.0"
+"Release Notes" = "https://github.com/Shakargy/devtime/releases/tag/v0.4.0"
 Demo = "https://youtu.be/1Hiu3Y9J_SI"
 
 [project.scripts]

{devtime_ei-0.2.0 → devtime_ei-0.4.0}/src/devtime/__init__.py

@@ -1,6 +1,6 @@
 """DevTime - local-first Engineering Intelligence for repository memory."""
 
-__version__ = "0.2.0"
+__version__ = "0.4.0"
 
 # Version metadata (Builder Edition, Chapter 20).
 EVIDENCE_MODEL = "2026.06.1"

{devtime_ei-0.2.0 → devtime_ei-0.4.0}/src/devtime/cli.py

@@ -347,11 +347,29 @@ def risk(
     conn = connection.connect()
     try:
         intelligence = repository.load_all_concepts(conn)
+        from devtime.intelligence.verification import claims_affected_by_paths
+
+        claim_impact = claims_affected_by_paths(conn, info.changed_files)
     finally:
         conn.close()
 
     review = review_diff(info, intelligence)
     console.print(render_risk_review(review), markup=False)
+
+    # v0.4.0: claim impact. A diff is not just risky in general - it can
+    # destabilize a previously verified claim. Only evidence files count;
+    # nothing is printed when no verified claim is affected.
+    if claim_impact:
+        console.print("\nClaim impact:", markup=False)
+        for item in claim_impact:
+            console.print(
+                f"  - {item['claim_id']} (previous status: {item['previous_status']})",
+                markup=False,
+            )
+            for p in item["changed_evidence"]:
+                console.print(f"      changed evidence: {p}", markup=False)
+            console.print(f"      re-verify: {item['suggested_action']}", markup=False)
+
     if review.state == STATE_REVIEW_FAILED:
         raise typer.Exit(code=1)
 

{devtime_ei-0.2.0 → devtime_ei-0.4.0}/src/devtime/intelligence/verification.py

@@ -149,8 +149,17 @@ BUILTIN_CLAIMS: dict[str, ClaimDefinition] = {
         statement="Incoming billing webhooks verify the payment provider's signature.",
         category="billing",
     ),
+    "jwt-authentication": ClaimDefinition(
+        slug="jwt-authentication",
+        name="JWT Authentication",
+        statement="Authentication uses JWT access tokens.",
+        category="authentication",
+    ),
 }
 
+# JWT library names for dependency evidence.
+_JWT_DEP_TOKENS = ("jsonwebtoken", "pyjwt", "jose", "njwt", "jwt-decode", "fast-jwt")
+
 _LIMITATIONS = [
     "Heuristic scanner: evidence comes from static patterns, not execution.",
     "Signature verification is recognized for known provider patterns "
@@ -225,7 +234,8 @@ def verify_claim(conn: sqlite3.Connection, slug: str) -> VerificationResult:
         )
 
     rows = _load_signals(conn, scan_id)
-    return _verify_billing_webhook_signature(definition, rows, scan_id)
+    evaluator = _EVALUATORS[slug]
+    return evaluator(definition, rows, scan_id)
 
 
 def _verify_billing_webhook_signature(
@@ -348,6 +358,135 @@ def _verify_billing_webhook_signature(
     )
 
 
+def _verify_jwt_authentication(
+    definition: ClaimDefinition, rows: list[sqlite3.Row], scan_id: str
+) -> VerificationResult:
+    """Verify JWT access-token authentication, with the documentation-vs-
+    implementation contradiction detector.
+
+    The purpose classifier (Trust Repair v0.0.6) distinguishes access tokens
+    from invitation/verification tokens. Documentation claiming JWT while the
+    only JWT usage found is invitation-purpose is a real, both-sided conflict.
+    Documentation with NO usage found at all is missing evidence (WEAK), not a
+    contradiction: absence is not positive conflicting evidence.
+    """
+    access_usage: list[EvidenceRef] = []
+    invitation_usage: list[EvidenceRef] = []
+    unclear_usage: list[EvidenceRef] = []
+    jwt_docs: list[EvidenceRef] = []
+    jwt_deps: list[EvidenceRef] = []
+
+    for row in rows:
+        hay = _hay(row)
+        kind = row["kind"]
+
+        if kind == "token_usage":
+            try:
+                purpose = json.loads(row["metadata_json"] or "{}").get("purpose", "unclear")
+            except json.JSONDecodeError:
+                purpose = "unclear"
+            if purpose == "access":
+                access_usage.append(
+                    _ref(row, "JWT used as an access token (login/bearer context).", "strong")
+                )
+            elif purpose == "invitation":
+                invitation_usage.append(
+                    _ref(
+                        row,
+                        "JWT used for invitation/verification tokens, not access.",
+                        "moderate",
+                    )
+                )
+            else:
+                unclear_usage.append(
+                    _ref(row, "JWT usage found; its purpose is unclear.", "weak")
+                )
+        elif kind in ("doc", "decision") and "jwt" in hay:
+            jwt_docs.append(
+                _ref(
+                    row,
+                    "Documentation or decision record references JWT.",
+                    "moderate" if kind == "decision" else "weak",
+                )
+            )
+        elif kind == "dependency" and any(t in hay for t in _JWT_DEP_TOKENS):
+            jwt_deps.append(
+                _ref(row, "JWT library dependency is declared.", "weak")
+            )
+
+    why: list[str] = []
+    missing: list[str] = []
+    contradictions: list[Contradiction] = []
+    supporting: list[EvidenceRef] = []
+
+    if access_usage:
+        status = SUPPORTED
+        supporting = access_usage + jwt_docs + jwt_deps
+        why.append("JWT access-token usage evidence was found.")
+        if jwt_docs:
+            why.append("Documentation or a decision record corroborates JWT usage.")
+        else:
+            missing.append("A decision record explaining the JWT choice.")
+    elif jwt_docs and invitation_usage:
+        status = CONTRADICTED
+        supporting = invitation_usage
+        doc = jwt_docs[0]
+        inv = invitation_usage[0]
+        contradictions.append(
+            Contradiction(
+                summary="Documentation claims JWT authentication, but the only JWT "
+                "usage found is invitation/verification tokens.",
+                claimed_side=f"{doc.path} references JWT in a documentation or "
+                "decision context, implying JWT-based authentication.",
+                observed_side=f"{inv.path} uses JWT for invitation/verification "
+                "tokens. Invitation tokens are not access-token authentication, "
+                "and no access-token usage was found.",
+                evidence=[doc, inv],
+            )
+        )
+        why.append(
+            "Documentation references JWT, but no access-token usage exists; "
+            "the only JWT usage found is invitation-purpose."
+        )
+        missing.append("JWT access-token usage (login/bearer/authorization context).")
+    elif jwt_docs or jwt_deps or invitation_usage or unclear_usage:
+        status = WEAK
+        supporting = jwt_docs + jwt_deps + invitation_usage + unclear_usage
+        why.append(
+            "JWT surface exists (documentation, dependencies, or unclear usage), "
+            "but access-token authentication is not established."
+        )
+        missing.append("JWT access-token usage (login/bearer/authorization context).")
+    else:
+        status = UNKNOWN
+        why.append(
+            "No JWT evidence was found in the scanned files. The claim does not "
+            "apply, or the usage is outside scanner coverage."
+        )
+        missing.append("Any JWT usage, dependency, or documentation.")
+
+    return VerificationResult(
+        claim_slug=definition.slug,
+        claim_name=definition.name,
+        statement=definition.statement,
+        status=status,
+        why=why,
+        supporting=supporting,
+        contradictions=contradictions,
+        missing=missing,
+        limitations=_LIMITATIONS,
+        scan_id=scan_id,
+        verified_at=_now(),
+        engine_version=__version__,
+    )
+
+
+_EVALUATORS = {
+    "billing-webhook-signature": _verify_billing_webhook_signature,
+    "jwt-authentication": _verify_jwt_authentication,
+}
+
+
 def _ref(row: sqlite3.Row, observation: str, strength: str) -> EvidenceRef:
     return EvidenceRef(
         path=row["path"],
@@ -441,6 +580,38 @@ def load_latest_verification(
     )
 
 
+def claims_affected_by_paths(
+    conn: sqlite3.Connection, changed_paths: list[str]
+) -> list[dict]:
+    """Claim impact for a set of changed paths (v0.4.0, diff integration).
+
+    For every claim with a stored verification, report it when a changed path
+    is one of its recorded evidence files. Only evidence files count: a diff
+    touching unrelated files never flags a claim. Advisory output - the caller
+    decides what to do with it.
+    """
+    changed = set(changed_paths)
+    out: list[dict] = []
+    for slug in BUILTIN_CLAIMS:
+        latest = load_latest_verification(conn, slug)
+        if latest is None:
+            continue
+        result, fingerprints, created_at = latest
+        evidence_paths = {fp["path"] for fp in fingerprints}
+        hits = sorted(evidence_paths & changed)
+        if hits:
+            out.append(
+                {
+                    "claim_id": slug,
+                    "previous_status": result["status"],
+                    "verified_at": created_at,
+                    "changed_evidence": hits,
+                    "suggested_action": f"dtc verify {slug}",
+                }
+            )
+    return out
+
+
 def freshness_for(conn: sqlite3.Connection, slug: str) -> tuple[str, list[str]]:
     """Compare stored evidence fingerprints against current file hashes.
 

{devtime_ei-0.2.0 → devtime_ei-0.4.0}/src/devtime/scanner/signals.py

@@ -10,6 +10,7 @@ Never executes repository code, never makes network calls.
 from __future__ import annotations
 
 import hashlib
+import json
 import sqlite3
 import uuid
 from dataclasses import dataclass, field
@@ -214,7 +215,10 @@ def run_scan(
                         s.start_line,
                         s.end_line,
                         s.confidence,
-                        "{}",
+                        # v0.3.0: persist extractor metadata (was hardcoded '{}',
+                        # silently dropping e.g. the JWT purpose classification
+                        # that verification reads back from the database).
+                        json.dumps(s.metadata or {}),
                     ),
                 )
         conn.commit()

{devtime_ei-0.2.0 → devtime_ei-0.4.0}/src/devtime_ei.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: devtime-ei
-Version: 0.2.0
+Version: 0.4.0
 Summary: Local-first Engineering Intelligence for software repositories
 Author-email: Aviad Shakargi <aviad94@gmail.com>
 Maintainer-email: Aviad Shakargi <aviad94@gmail.com>
@@ -8,7 +8,7 @@ License: Apache-2.0
 Project-URL: Homepage, https://github.com/Shakargy/devtime
 Project-URL: Repository, https://github.com/Shakargy/devtime
 Project-URL: Issues, https://github.com/Shakargy/devtime/issues
-Project-URL: Release Notes, https://github.com/Shakargy/devtime/releases/tag/v0.2.0
+Project-URL: Release Notes, https://github.com/Shakargy/devtime/releases/tag/v0.4.0
 Project-URL: Demo, https://youtu.be/1Hiu3Y9J_SI
 Keywords: devtools,cli,static-analysis,repository-analysis,engineering-intelligence,local-first
 Classifier: Development Status :: 3 - Alpha
@@ -317,8 +317,8 @@ Contradictions:
 ```
 
 Statuses are SUPPORTED, WEAK, CONTRADICTED, or UNKNOWN; contradictions always
-show both sides; changed evidence marks a claim STALE. One built-in claim ships
-in v0.2. See **[VERIFICATION.md](VERIFICATION.md)**.
+show both sides; changed evidence marks a claim STALE. Two built-in claims ship
+(billing webhook signatures, JWT authentication). See **[VERIFICATION.md](VERIFICATION.md)**.
 
 ## Example output