Skip to content

Development Changes

Jump to bottom
HelloThisWorld edited this page Aug 4, 2026 · 33 revisions

Development Changes

This ledger maps winTerm source changes to their durable GitHub records and the Wiki pages synchronized with them. Source commits remain authoritative; the Wiki explains their user-visible and engineering effect.

2026-08-04 — winTerm 1.3.0-alpha3 prerelease

  • Source: 9f8198cf247190903e6a3fdce08d058c8b4b025f
  • Branch: release/v1.3.0-alpha3, based on main at e0fd786c (alpha2 field-report fixes, pull request #34)
  • Version intent: 1.3.0-alpha3 / tag v1.3.0-alpha3, channel alpha, package/file version 1.3.0.2.
  • Summary: Promotes the five alpha2 field-report fixes to a third installable alpha. Metadata only: application version 1.3.0-alpha3, module prerelease suffix alpha3, package version 1.3.0.2, and the version literals pinned by the verification scripts.
  • Publication boundary: The release workflow marks any non-stable channel --prerelease --latest=false, so /releases/latest keeps resolving to v1.2.0. The alpha is deliberately not listed on winterm-site and is not submitted to WinGet. The Setup EXE is unsigned and says so in its release notes.
  • Documentation: release notes, repository changelog, and current progress.

2026-08-04 — Alpha2 field-report fixes

  • Source: 09bd1b5f19f05a9e5ae8bf41453e25feba62dd98
  • Branch: fix/alpha2-feedback, based on main at e225933e (1.3.0-alpha2 release metadata, pull request #33)
  • Version intent: fixes ahead of 1.3.0-alpha3; version metadata unchanged.
  • Summary: Fixes the five issues reported from local v1.3.0-alpha2 testing. The shell integration module wrote its string terminator as a PowerShell single-quoted '\' — two literal characters — leaving one stray backslash on screen per emitted sequence, and wrote its marks as console side effects, which the host prints before a prompt function's returned text, so the command-start mark landed before the visible prompt: the Timeline recorded the whole prompt line and Load inserted the prompt path. The wrapper now returns one string with the marks embedded in FinalTerm order and a single-character terminator. The progress state machine no longer shows a bar for 133;B (composing input), so an idle integrated prompt stays quiet; the lifecycle model no longer creates a Timeline entry at 133;B, removing the phantom Command text unavailable / Running row; and selection-only Timeline updates reuse the existing rows, removing the arrow-key/hover jitter. A module component blocked by antivirus at parse time is now skipped silently and recorded in diagnostics.
  • Validation: SettingsModel winTerm TAEF classes 44/44, Control CommandTimelineTests 43/43 on fresh builds, both test projects x64 Release exit 0, live-session prompt bytes verified in FinalTerm order, and all eight repository gates pass.
  • Documentation: PowerShell integration and repository changelog.

2026-08-04 — winTerm 1.3.0-alpha2 prerelease

  • Source: 1202129f6d89627b5ac1bd8baa801dcfe3e81232
  • Branch: release/v1.3.0-alpha2, based on main at 18310e9f (alpha1 field-report fixes, pull request #32)
  • Version intent: 1.3.0-alpha2 / tag v1.3.0-alpha2, channel alpha, package/file version 1.3.0.1.
  • Summary: Promotes the four alpha1 field-report fixes to a second installable alpha. This commit only moves release metadata: application version 1.3.0-alpha2, module prerelease suffix alpha2, package version advanced to 1.3.0.1 so alpha binaries stay distinguishable, and the version literals pinned by the verification scripts.
  • Publication boundary: The release workflow marks any non-stable channel --prerelease --latest=false, so /releases/latest keeps resolving to v1.2.0. The alpha is deliberately not listed on winterm-site and is not submitted to WinGet. The Setup EXE is unsigned and says so in its release notes.
  • Documentation: release notes, repository changelog, and current progress.

2026-08-04 — Alpha1 field-report fixes

  • Source: f3697b8c30776b7eb031b35bd29adac20d43c2a4
  • Branch: fix/alpha1-feedback, based on main at ed70755 (pull request #31)
  • Version intent: fixes ahead of 1.3.0-beta1; version metadata unchanged.
  • Summary: Fixes the four issues reported from local v1.3.0-alpha1 testing. The Command Timeline handle is now a thin auto-hiding strip flush against the terminal's left edge that widens on hover, focus, or while the overlay is open, instead of a floating button that covered terminal content. A pointer press on the terminal area now light-dismisses an open overlay. The Visual Progress recognition engine no longer claims ownership from a bare product-name mention (a dir listing containing .gradle previously started a bar that never stopped), no longer rematches arbitrary records under an established claim, structurally clears a still-running provider bar after two consecutive ordinary records, and no longer reads slashed dates as completed/total meters. Bare PowerShell profile commandlines are now rewritten at connection creation to import the packaged winTerm.Shell module, so OSC 133 marks and the Command Timeline work out of the box; the rewrite is gated by the new per-profile setting "shellIntegration.autoInject" (default true) and refuses every customized invocation.
  • Validation: SettingsModel winTerm TAEF classes 44/44, Control CommandTimelineTests 43/43, TerminalAppLib and Control.UnitTests x64 Release builds clean, and the command-timeline, visual-progress, privacy, version, release-workflow, CI-classification, and Smoke gates all pass.
  • Documentation: PowerShell integration, repository changelog, and current progress.

2026-08-04 — winTerm 1.3.0-alpha1 prerelease

  • Source: cdfa02be0ac0f9f3c7ba8bd34200854323dbf130
  • Branch: release/v1.3.0-alpha1, based on main
  • Version intent: 1.3.0-alpha1 / tag v1.3.0-alpha1, channel alpha.
  • Summary: Promotes the Command Timeline to a testable alpha. The feature content was already on main as checkpoints v1.2.1–v1.2.4; this moves the release metadata and makes the version gates channel-aware. verify-version.ps1 now accepts stable, alpha, and beta and enforces that the channel, the module prerelease suffix, and the application-version suffix agree. The WinGet workflow now skips prerelease Releases.
  • Publication boundary: The release workflow marks any non-stable channel --prerelease --latest=false, so /releases/latest keeps resolving to v1.2.0. The alpha is deliberately not listed on winterm-site and is not submitted to WinGet. The Setup EXE is unsigned and says so in its release notes.
  • Documentation: Wiki changelog, release notes, repository changelog, and current progress.

2026-08-04 — Command Timeline Phase 4 checkpoint

  • Source: c1426996372c5af0ba442eebf5603bad15a9135e
  • Branch: feature/command-timeline-v1.3.0-phase4, based on main (Phase 3 was squash-merged to main as 5fd2172 through pull request #29)
  • Pull request: #30 — feat: complete Command Timeline Phase 4 checkpoint
  • Version intent: 1.2.4 / tag v1.2.4.
  • Summary: Completes the in-memory Command Timeline surface. Adds pane-local literal case-insensitive search over each pane's bounded command-text index with a 256 UTF-16 surrogate-safe query cap, a filtered projection that keeps stable CommandId identity, / and Tab focus routing that never reaches the PTY, Escape clear-then-close, the commandTimeline.enabled and commandTimeline.historyLimit settings with a Settings UI section, four distinct shell-degradation states, and bounded per-pane history with oldest-first eviction.
  • Documentation: Wiki changelog, repository changelog, Phase 4 development notes, Command Timeline user guide, keyboard shortcuts, privacy, and current progress.
  • Boundary: No persistent history, output cache, output search, regex or fuzzy matching, telemetry, automatic execution, ConPTY/VT/TextBuffer/renderer change, workspace or shell protocol schema change, installer, Portable packaging, Release asset, Latest update, website change, or screenshot.

2026-08-03 — Command Timeline Phase 3 checkpoint

2026-08-02 — Command Timeline Phase 2 checkpoint

2026-08-02 — Command Timeline Phase 1 checkpoint

2026-08-02 — Test cleanup and label-gated CI

Synchronization rule

Every source commit that changes user-visible behavior, versioning, release status, or project history must update the root CHANGELOG.md and the matching Wiki record in the same delivery cycle. A later source correction receives a new ledger entry; published tags and Releases are never rewritten.

winTerm

Clone this wiki locally