codeweb v0.15.0

Added

• Explicit pre-edit baselines survive ordinary and automatic graph refreshes. Agents can
  refresh and verify an edit in one diff call, then check repairs against the same baseline.
• Context responses distinguish list/source-evidence limits from graph uncertainty, with
  actionable freshness and recovery information. Local setup diagnostics report installation,
  graph discovery, source freshness and optional-parser availability without changing source.
• First-use instructions include a tested installed-package cycle walkthrough and a
  baseline-preserving MCP workflow.

Fixed

• Diagnostic masking recognizes regex statements after multiline control heads while
  preserving division expressions, avoiding false incomplete-analysis reports.
• Package exclusions keep generated Python bytecode and verification-harness caches out
  of the npm artifact, even after the verification suite has run.
• Refreshing verification rejects baselines without valid node and edge arrays before
  changing the live graph. Baseline parsing and fingerprinting use the same bytes.
• Current documentation count checks include SPEC and recognize formatted counts and
  Codeweb possessive phrasing while leaving dated audit and release records historical.
• Known unsupported same-line JavaScript/TypeScript declaration layouts now carry bounded
  source diagnostics. Gates refuse an unqualified clean verdict when either snapshot has
  detected incomplete analysis. This contains the reported false-clean result; it does not
  claim complete syntax coverage or repair every omitted declaration.
• Gate comments use commit links only when the checkout is clean before and after analysis
  and HEAD is unchanged; otherwise locations remain plain text. Comments include bounded
  evidence and investigation guidance.
• Removed unsupported metadata keys from the shipped hook configuration while retaining
  all three handlers and moving their descriptions into adjacent documentation.

Changed

• Prominent guidance describes mapped-graph limits, exported-symbol exemptions, skipped
  checks, and tested-client scope. Teams availability copy now reflects restricted GitHub
  App access while preserving the ratified planned price and free-local boundary.
• Inconclusive analysis is a non-success result distinct from detected regressions; callers
  must inspect diagnostics rather than interpreting an incomplete comparison as clean.

Documentation

• Updated contributor guidance, operational graph-schema notes, and a documentation index
  describe the required gate, ownership, provenance, freshness and missing data. Audit
  indexes connect historical findings to implementation and verification records.

Verification scope

• Runtime analysis remains deterministic, local and free of required third-party dependencies.
  Optional parser installation is not a substitute for the incomplete-analysis checks.
• Structural results do not establish behavioral correctness. Run the relevant product tests.
  Release-candidate test results and artifact hashes are recorded in the accompanying review.

Also added in product clarity

• Package commands for client setup, local diagnostics, change review, and the existing CI gate.
• Portable change-review HTML with caller evidence, baseline provenance, and explicit analysis limits.
• Report-only gate mode that preserves regression verdicts and still fails on analysis errors.
• A reproducible edit-review demo, a dated Graphify comparison, and pilot and case-study protocols.

Changed

• Public identity: “See what your AI edits affect.” and “Structural checks for AI code changes.”
• Setup uses shared recipes for five clients and shows an observable caller-query check.
• Findings separate body confidence from priority and provide source evidence and an agent task.
• The public Axios demo is re-extracted from a pinned commit with current engine provenance.
• Agent review details are bounded and report omitted counts; supporting HTML retains full evidence.