-
Notifications
You must be signed in to change notification settings - Fork 0
Development Changes
HelloThisWorld edited this page Aug 2, 2026
·
3 revisions
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.
-
Source:
e3033cced4f68ae6e50962b48c91eb432d3d0e17 - Pull request: #28 — feat: add Command Timeline phase 2 checkpoint
-
Merged source:
395f9becd3237bf0d439ba58de50a667a911445d -
Version intent:
1.2.2/ tagv1.2.2. - Summary: Adds the pane-owned, read-only Command Timeline overlay; pure deterministic navigation; incremental Phase 1 index consumption; keyboard, pointer, wheel, accessibility, privacy, warm-access, and cleanup behavior; shortcut remapping; version synchronization; CI badge repair; and permanent changelog/Wiki policy.
- Documentation: Wiki changelog, repository changelog, and current progress.
- Boundary: No command insertion, copy, paste, execution, output jump, search, persistence, Release asset, installer, website, or screenshot change.
-
Merged source:
510c326e474eccfbc40f8f6763b4b9227a2aa6b0 - Pull request: #26 — feat: add Command Timeline Phase 1 checkpoint
-
Version intent:
1.2.1/ tagv1.2.1. -
Summary: Introduced pane-local OSC 133 indexing, stable native mark
identity, bounded command-text caching, no output cache or persistence, warm
markRevisionreads, and lifecycle/reflow/eviction/close coverage. - Documentation: Wiki changelog and repository changelog.
-
Merged source:
abb581a2a661f1d3a1f34b2ac384ce4c7e3c69c9 - Pull request: #27 — fix: prevent hanging tests and optimize CI builds
-
Summary: Added bounded TAEF process-tree cleanup and made native build,
delivery, and
ci:fullvalidation explicit maintainer-selected gates while ordinary pull requests retain quick validation.
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.