DRIFT v0.8.1

Fixed

• Made live Ask DRIFT responses structured and grounding-aware. The model now
  reports the Insight IDs it actually used, the API filters citations and
  grounded_insight_ids to that subset, and stray or malformed model IDs can
  no longer cause unrelated source links to be presented for a question.
• Added regression coverage for subset citation behavior, malformed structured
  responses, blank answers, router schema forwarding, and lifespan integration.

Release boundary

• This is a source patch release for the Ask DRIFT grounding fix, tagged from
  feature/v0.9.0-final-evidence. Hosted Railway/Vercel verification remains
  at v0.8.0 until a deployment is independently checked.

Targeted releases — planned, not released

These targets are planning records only. They do not change the current
verified release (v0.8.0) or claim that the paid Tier.FINAL rerun has run.

v0.9.0 — final-tier evidence and selected polish

Targeted scope:

• rerun selected reviewed examples through Tier.FINAL (Sol), initially the
  four currently published sources: Transformers, vLLM, NCCL, and TensorRT;
• preserve source bytes, exact claim spans/hashes, upstream references, model
  identifiers, verifier results, model-run audits, and meaningful human review
  notes for every accepted result;
• publish only verifier-passed results after human review, retaining the
  existing bounded-evidence and spend/retry guardrails; and
• optionally include narrowly scoped polish that improves judge clarity or the
  demo path, provided it does not delay or blur the evidence boundary.

The Tier.FINAL run is still pending operator execution and budget validation.
The reported remaining account balance is planning context, not release
evidence; the configured spend guard remains authoritative.

v1.0.0 — final submission release

Targeted scope:

• final product and documentation polish after the evidence decision;
• final local/hosted verification of the judge path and bounded claims;
• a public English YouTube demo under three minutes showing the working
  workflow, citations, verification, Codex contribution, and GPT-5.6 role; and
• final README, submission notes, Devpost metadata, and video-link replacement.

v1.0.0 is the submission-final target, not permission to add new feature
surfaces such as MCP, tool calling, IDE integration, or a release timeline.