LineLoom v1.4.1 — LineLoom Code Research & Privacy Preview

LineLoom v1.4.1 — LineLoom Code Research & Privacy Preview

Candidate status: NOT YET PUBLISHED. This GitHub-only pre-release requires separately approved owner flag and successful locked automated publishing. It is not a stable release. The latest verified stable is v1.3.0, and the latest currently published preview is v1.4.0. Do not offer v1.4.1 assets before the GitHub publishing run verifies them.

New since GitHub preview v1.4.0

• Explicit sanitized support report — PR #126: user-triggered Copy Sanitized Support Summary through native sidebar, Quick Actions and Command Palette. Allowlisted session counts and last-check states only, no source, file paths, prompt, endpoint URL, model tags or private document identities. Optional aggregate timing only after diagnostics opt-in; the user's clipboard is visible to other local apps and should be reviewed before sharing.
• Editor-scoped readiness correction — PR #126: switching, changing or closing editors revokes the prior editor's manual file privacy and active-model check snapshots and rejects old asynchronous outcomes.
• Cancellation of obsolete manual model discovery — PR #127: superseding /api/tags checks, editor/configuration changes and trust invalidation abort stale user-invoked model-list network work. No background monitoring or automatic model download.
• LineLoom Code synthetic comparison — PR #129: offline comparison of exactly two bounded JSON reports using deterministic fixture-content SHA-256, the same prompt mode and repetition count. Source-free per-language/category exact-match and latency deltas. No real local model benchmark was run.
• Dataset governance preflight — PR #130: opt-in offline manifest audit for human-declared rights, provenance-revision syntax, train/validation/test split isolation, approximate duplicates and public synthetic evaluation contamination, and obvious secret/PII patterns. A successful mechanical screening does not authorize training or establish legal permission.
• Synthetic benchmark protocol v2 — PR #131: aggregate conservative response-format signals for empty output, markdown, chat preamble, special tokens, hidden Unicode and echoed prefix/suffix. Strict separation of v1/v2 comparison protocols. Not compile correctness or semantic quality.

The extension remains MIT-licensed, local-first and tied to user-configured Ollama by default. Related-file context remains off by default and requires explicit selection. Workspace trust, sensitive-file filtering and separate remote HTTPS approval continue to apply. The extension ID remains SanskarCodes.lineloom; publisher rename or registry migration is not authorized.

Verification, quality and release limitations

All feature PRs above passed their own Windows/macOS/Linux checks, mocked Linux VS Code extension-host, security audit, and independent VSIX candidate packaging verification. The v1.4.1 release itself is not verified until the version-pinned publishing workflow completes successfully with a genuine VS Code pre-release marker, checksum, clean install, and isolated pinned v1.3.0 stable-to-v1.4.1 upgrade. The GitHub publisher must reject duplicate tags and verify public asset names.

Manual QA outstanding — NOT RUN: real Ollama quality/latency results, dedicated trained LineLoom Code weights, reviewed/approved training corpus and base checkpoint, physical Windows/macOS/Linux VS Code keyboard and screen-reader behavior, privacy/consent tests on actual user-controlled files, and real remote endpoint approval tests. Automated mocks do not substitute for that evidence.

Four moderate development-only transitive dependency advisories were documented during previous preview preparation in issue #79. A passing high-severity audit does not imply a zero-advisory tree. The publisher must still pass high/critical complete-toolchain and moderate-or-higher production-only dependency checks; assess dev-only advisories separately.

Distribution and rollback

Until an authorized GitHub publisher completes, v1.4.1 is a candidate only, and no public v1.4.1 VSIX or checksum is claimed. When verified, the GitHub-only prerelease must contain LineLoom-1.4.1.vsix and LineLoom-1.4.1.sha256 with matching SHA-256; use VS Code → Extensions → ... → Install from VSIX, not the Visual Studio VSIX installer. This workflow does not publish to the VS Code Marketplace, Open VSX, GitHub Packages or npmjs.com, nor does it change GitHub stable/latest. For rollback, use the verified v1.3.0 stable release and its published checksum.