What is Delivery Integrity?

Delivery Integrity is the engineering discipline of proving that what a team says is done is actually done — with line-level evidence attached to Jira or Linear tickets rather than a status dropdown.

How does Tyne differ from AI code review tools like CodeRabbit or Qodo?

Unlike AI code reviewers that grade style nits on PRs after the fact, Tyne verifies acceptance criteria while the developer still has the file open in VS Code, with zero PR noise.

What is the Evidence Ledger?

The Evidence Ledger is Tyne’s immutable proof record mapping commit hash, file path, line range, acceptance criterion ID, and confidence score directly into your system of record.

// SYSTEM LOGS

[ ENGINEERING_LOGS ]

0.2.10

// CURRENT_BUILD

0.2.10 — Compile changelog + UI quieting

### Added - Compile → DB changelog: npm run compile / vsix record rows in public.changelog via scripts/record-changelog.mjs. ### Changed - UI quieting: Reviews work-list first (Action Needed before gauges); 1px radius; no pill glow; flat Analytics; removed orphan Technical Review page; Thread scorecard primary + More.

0.2.9

STABLE

0.2.9 — Validate & Review PDF export

### Added - Validate & Review PDF export — Modern print-ready HTML report with Tyne branding, generator + code authorship, quality scorecard, findings, changed files, and technical appendix. Open → Print → Save as PDF.

0.2.8

STABLE

0.2.8 — Contributors attribution

### Fixed - Validation report Contributors — No longer scans the code diff for AI tool names (which falsely listed Tyne’s own tooling as authors). Attribution uses git author + commit co-author trailers only.

0.2.7

STABLE

0.2.7 — Jira task refresh / auth

### Fixed - Jira tasks not appearing / yellow refresh dot — Hosted Jira task pull, project list, and project mapping now authenticate with the active Tyne session (device-auth JWT or GitHub token), not GitHub-token-only. Connect prompts for a project when none is mapped. Sync tooltip and empty list show the real pull error (including “assign to yourself”).

0.2.6

STABLE

0.2.6 — Jira / Linear Connect browser

### Fixed - Jira / Linear Connect opens no browser — Connect clicks no longer get stolen by BYOK provider toggles; stuck in-progress OAuth is cancelled so a new click reopens the browser; auth for PM OAuth accepts Tyne session JWT or GitHub token; Settings no longer shows a sticky false Connected / false GitHub-ready state from webview persist.

0.2.5

STABLE

0.2.5 — PM Connect / Disconnect state

### Fixed - PM Connect / Disconnect stuck on Connected — Settings no longer sticky-ORs old connected state after Disconnect. Jira disconnect also sets a local opt-out so hosted session recovery cannot silently reconnect until the user Connects again. Stale connectedTools entries are pruned when a tool is not actually connected.

0.2.4

STABLE

0.2.4 — Marketplace runtime deps fix

### Fixed - Marketplace infinite loading / failed activation — 0.2.2 and 0.2.3 VSIX builds were packaged with --no-dependencies, which stripped required runtime packages (typescript, web-tree-sitter). Packaging again includes those deps (same as 0.2.1).

0.2.3

STABLE

0.2.3 — Core quota + PM-bound validation

### Fixed - Core validation quota — Validate & Review hard-stops after 5 runs/month with a clear upgrade prompt (BYOK no longer silently bypasses the Core cap). - Task-bound validation — Direct BYOK and managed review score the diff against the linked Jira/Linear Golden Contract (goal, AC, constraints). - Quota edge cases — Core Direct BYOK metered server-side; 402 / quota errors no longer fall back to unmetered local review; usage checks fail closed. - Validate & Review gating — Requires a linked Jira or Linear task with goal/AC before running. ### Changed - Core Validate & Review ≈ Pro quality (5/month) — same PM alignment, missing-test review, full report, and chunked/PEV/scope-drift pipeline as Pro. - Core managed routing — Core's 5 managed validations run on the Axiom AI standard path.; Core skips Direct BYOK. - Upgrade CTA on Core emphasizes volume (Pro 50 / Max unlimited). ### Security - Usage metering fails closed on RPC errors; Core quota cannot be skipped via client-only paths.

0.2.2

STABLE

0.2.2 — Core quota packaging (superseded)

### Fixed - Initial packaging of Core quota + PM-binding hardening for Validate & Review (superseded and completed in 0.2.3). ### Known issue - VSIX built with --no-dependencies omitted runtime deps — fixed in 0.2.4. Prefer upgrading to 0.2.4.

0.2.1

STABLE

0.2.1 — Marketplace activation + upgrade CTAs

### Fixed - Marketplace activation hang — ship runtime deps (typescript, web-tree-sitter) that esbuild left external so the extension activates from the VSIX. - Branding assets and packaging for Marketplace install. ### Added - In-extension upgrade CTAs for free-tier validation and Settings (Upgrade / Manage billing).

0.2.0

STABLE

0.2.0 — Validate & Review foundation

### Added - Validate & Review privacy modes with Direct BYOK. - Quality scanners, PEV scope drift, and parallel file review. - Beta validation reminders and launch polish. - PM task intelligence, Jira/Linear OAuth flows, hosted Linear sync. ### Changed - Refined thread review UX and architecture flowchart readability.

0.1.0

STABLE

0.1.0 — Initial release

### Added - Initial Tyne VS Code extension: goal enforcement, thread workflow, validation, and Supabase-backed services.