Codemble v0.18.0

Codemble v0.18.0 — one feature, one shared learning journey

Codemble can now show how a selected feature connects to the application, not
just explain the file where it lives. Study begins with one deterministic route
from Home through proven imports and calls. Easy mode guides one cited step at a
time; Expert mode keeps that exact step selected and adds its parser evidence.
Impact, Connections, and verification candidates remain explicitly scoped to
the selected feature rather than being presented as facts about every step.

What changed

• Graph schema 11 adds parser-owned roles for app entries, route handlers, UI
  renderers, and tests across Python, JavaScript, TypeScript, Go, Java, Rust,
  and C#.
• Each framework role requires the exact imported annotation, macro, or
  factory binding at the observation site—not merely another import from the
  same framework—and revokes that proof on project-type shadowing or receiver
  rebinding. Every role then cites a stable parser rule and exact observation
  lines. A route registration can cite one file while the handler declaration
  cites another.
• The route completes only over certain directed imports and calls. When proof
  ends, Study inserts a visible break before a bounded possible frontier that
  can still lead toward the selected feature.
• Easy and Expert project one mode-neutral payload. The current step survives a
  mode change; neither mode can teach a different graph.
• Impact and Connections appear once inside journey details and are labelled as
  selected-feature facts. Expert may also show connected test-role nodes as
  selected-feature verification candidates.

Deliberate limits

• This release deepens all seven supported parsers; it does not add an eighth
  language.
• A possible edge never completes the feature route, even when it is the only
  apparent connection.
• Verification candidates are places to inspect. They do not claim coverage,
  invent a test command, run a test, or report a pass.
• A module target ends at its file, and runtime is marked not applicable.
• Missing Home, partial source, cycles, and long paths stop or truncate with an
  explicit reason instead of being filled by narration.
• Framework-looking method or annotation names without a proven framework
  binding are ordinary code, not application-role evidence.
• Journey position is not XP or proof. Existing graph-derived checks remain the
  only way to light a system amber.

Human learner acceptance for milestone issue #13 remains open; this release
does not substitute technical coverage for those external runs.