LineLoom v1.4.3 — Dual Publisher Migration Preview

LineLoom v1.4.3 — Dual Publisher Migration Preview

GitHub-only pre-release (not a stable release). Two different extension
IDs are intentionally packaged from the same reviewed code snapshot. This
release does not change the existing Visual Studio Marketplace or Open VSX
listings and does not transfer subscribers, reviews, update history, or
extension-private storage.

Which archive should I install?

Extension ID	GitHub VSIX	Intended audience
SanskarCodes.lineloom	LineLoom-1.4.3-SanskarCodes.vsix	Existing users who want to test a normal same-ID upgrade
Sanskar.lineloom	LineLoom-1.4.3-Sanskar.vsix	Testers preparing to install from the future Sanskar publisher

Both assets have separate matching .sha256 files. Both must have the real
VS Code pre-release marker. The source manifest intentionally remains
SanskarCodes.lineloom; the Sanskar artifact is staged separately so
source builds do not silently rename existing users' extension identity.

Migration steps: see publisher migration guide.
Back up or note your LineLoom settings. Uninstall the old extension through
VS Code's Extensions view, then install the new VSIX via
Extensions → … → Install from VSIX. Reload the editor. Retain your
lineloom.* settings where applicable; re-check the model and privacy
settings and explicitly reapprove any remote endpoint. Installing the new
publisher is not an automatic extension update. Do not leave both enabled.

Contents since v1.4.2

• Dual publisher build and archive verification with an isolated source-tree
  staging step, no automatic publisher credentials and no marketplace publish.
• Existing LineLoom code-completion functionality is shared between the two
  packages. Opening extension-specific settings targets the installed identity.
• Regression gates for installing both IDs, removing the old one, and preserving
  synthetic VS Code user settings, plus the normal legacy preview upgrade.
• Post-v1.4.2 source development documented in CHANGELOG.md
  includes local-only model-evaluation and fine-tuning research refinements.
  Those tools do not represent trained weights or proven completion quality.

Validation and limitations

The owner-gated GitHub publishing job requires locked dependency install,
source checks, mocked editor-host integration, high-severity toolchain audit,
production moderate audit, separate preview-channel VSIX inspections, isolated
CLI installation, SHA-256 verification and a prior-v1.4.2 upgrade check.
The publication job rejects an already existing tag and does not alter the
GitHub stable latest, Visual Studio Marketplace, Open VSX or npm registries.

Manual QA outstanding — NOT RUN: physical Windows/macOS/Linux migration,
real Ollama suggestions and latency, VS Code sync implications, accessibility
and keyboard review, extension-private storage migration, actual Open VSX and
Marketplace publisher setup, and live new-listing download verification.
No first-party trained model weights are shipped. Security audits are useful
gates, not guarantees of zero development-tool advisories.

Rollback: reinstall the published
v1.3.0 stable under SanskarCodes,
and uninstall the new Sanskar.lineloom ID if present. Independently verify
the live registries before claiming a Sanskar listing is public.