LineLoom v1.4.4 — Completion Reliability and Publisher Migration Preview

LineLoom v1.4.4 — Completion Reliability and Publisher Migration Preview

GitHub-only pre-release (not a stable release). This version packages the reviewed
post-v1.4.3 source work into two distinct, independently checkable VS Code
extension identities: SanskarCodes.lineloom and Sanskar.lineloom.
Publishing this GitHub release does not publish to Visual Studio Marketplace,
Open VSX or npmjs and does not migrate existing subscribers or extension state.

Download and identity

VS Code extension ID	GitHub preview asset	Who should use it
SanskarCodes.lineloom	LineLoom-1.4.4-SanskarCodes.vsix	Existing-publisher preview testers
Sanskar.lineloom	LineLoom-1.4.4-Sanskar.vsix	Explicit opt-in testers preparing for the new publisher

Each VSIX has its own .sha256 file. Both must have the genuine VS Code
pre-release marker and pass the full packaged-file parity check: other than
publisher identity metadata, the shipped files must be byte-identical.
The tracked package.json remains SanskarCodes.lineloom to avoid silently
renaming existing installs.

Changes since v1.4.3

• Safer inline completions: stronger rejection of mismatched fenced languages,
  malformed chat/FIM protocol markers, reasoning envelopes and invisible Unicode
  tag characters; preserve meaningful Unicode, literal backticks and cursor spacing.
• Lower-risk prompt context: bounded Python f-string expression hints, JS/TS
  template-expression and regular-expression scanning, and refined Rust
  character-literal context. These are lexical hints, not compiler validation.
• More optional languages: C#, CUDA C++, Swift, Dart, Ruby and PHP can be
  enabled individually. The existing nine default enabled languages remain
  unchanged; no new language's model quality has been independently established.
• Reliability: bound stalled or cancelled model discovery and completion
  requests even when a transport ignores cancellation; improve timing and
  editor state guards.
• Local research tooling: add more source-free evaluation diagnostics,
  optional native syntax checks, and conservative LoRA adapter export guards.
  No first-party model weights were trained or shipped with this VSIX.
• Publisher migration and CLI safety: new-publisher installation is explicit
  and checks for a conflicting old publisher before and just prior to install.
  The npm CLI source and its registry releases have separate versioning and
  publication gates; this extension release does not publish the CLI.
• Maintenance: update development Vitest to 5.1.0 and tighten dual-publisher
  archive parity and preview-to-preview upgrade validation.

Publisher status and required manual action

The maintainer has confirmed Owner access to the Sanskar Visual Studio
Marketplace publisher under the intended permanent Microsoft account on
November 8, 2026. This confirms publisher administration only; it does not
mean Sanskar.lineloom has been uploaded or publicly indexed. The Open VSX
Sanskar namespace is a separate, independently verified requirement.
Do not claim a new registry listing is live without opening and testing it.

Migration is not a standard extension update. Back up or review your
lineloom.* settings, uninstall SanskarCodes.lineloom, reload VS Code,
install the matching, SHA-256-verified Sanskar preview VSIX through
Extensions → … → Install from VSIX, then confirm the Ollama/model and privacy
settings. Do not enable both identities at once: commands and settings overlap.
See the detailed migration guide.

Visual Studio Marketplace naming restriction

The official Microsoft documentation
states that Marketplace extension names and display names must be unique, and
that deleting an extension permanently reserves the name. The existing
SanskarCodes.lineloom listing can therefore block adding the exact
Sanskar.lineloom ID, despite verified ownership of publisher Sanskar.
Do not delete the existing listing. Contact Microsoft Marketplace Support
first to ask whether a publisher reassignment is supported; its availability,
conditions and outcome are unverified. The GitHub preview is separate from
Marketplace publication.

Release verification and honest limitations

The owner-authorized GitHub publishing workflow requires a clean locked install,
unit and source checks, mocked VS Code host integration, dependency auditing,
VSIX pre-release metadata validation, two isolated publisher install checks,
full shipped-file parity, individual SHA-256 validation, and an upgrade from
the independently digest-pinned published v1.4.3
SanskarCodes.lineloom preview. It separately smoke-tests migrating from
that legacy preview to the new ID using synthetic settings, and it refuses
to overwrite existing release tags. Passing these gates verifies the preview
package pipeline, not real model quality.

Manual QA outstanding — NOT RUN: actual Windows/macOS/Linux UI migration,
real Ollama completion quality and latency, accessibility and screen-reader
checks, workspace-specific privacy/consent review, VS Code Settings Sync,
real user upgrades, Microsoft Marketplace Sanskar.lineloom upload and
public download validation, independent Open VSX namespace/publication
verification, and first-party model training. No separate model artifacts
or stable-channel release are authorized by this preview.

Rollback: uninstall the new Sanskar.lineloom and reinstall the known
v1.3.0 stable SanskarCodes.lineloom,
then review the saved editor settings. Never upload an asset under the wrong
publisher ID or announce a marketplace migration before live verification.