fix: address the three alpha3 field reports

[HelloThisWorld]

Summary

Fixes the three issues reported from local v1.3.0-alpha3 testing.

#	Report	Root cause	Fix
1	Antivirus alert on every new PowerShell tab	touch created files through a raw [System.IO.File]::Open(OpenOrCreate, Write) call; combined with the & $native.Source dispatch blocks in the same script, the file read as a write-then-execute dropper shape to antivirus heuristics, flagging the whole module at load	File creation goes through New-Item, reachable only when the file does not exist — behavior identical, heuristic shape gone
2	Every completed command shows ? Unknown	The documented supported flow relies on the Enter keypress heuristic for the command-executed transition, but that heuristic only set buffer marks and never notified the shell-integration lifecycle. The Timeline never observed the executed stage, the per-mark capability chain never read Full, and _effectiveResult downgraded every trusted exit code to Unknown	The Enter path now reports CommandExecuted when the current mark was established by the shell (OSC 133 A/B) and the input line is non-empty. Heuristic-only marks (cmd.exe) still report nothing; an empty input line starts no command
3	Long commands unreadable, no tooltip	Rows show one trimmed line with no way to read the rest	Every row now carries a tooltip with the full wrapped command text (no marquee animation); the Unknown status also explains itself on hover via the new CommandTimelineStatusUnknownDetail resource

Fix 2 also restores the Running status during execution: entries now
materialize when the command executes rather than only at completion, which
alpha3's 133;B-no-entry change had made the only creation point in the live
flow.

Root-cause detail for #1 (bisected, not guessed)

On a local engine that reproduces the field report, every function of
Compatibility.ps1 loads clean in isolation, and every combination of
touch + any sibling function is flagged (14 of 14 such combinations; all 21
others clean). Replacing the raw File::Open write with New-Item clears
every combination and the full file. After the change, the complete module
imports with zero failed components and all eleven exports in both
Windows PowerShell 5.1 and PowerShell 7 on that engine. touch behavior
verified: creates a missing file, advances the timestamp of an existing file,
never truncates content.

Root-cause detail for #2

Synthetic tests always fed 133;C explicitly on the wire, so they passed
while the live path was broken: PowerShell's integration emits A/B/D but the
executed transition is supplied by the terminal-side Enter heuristic
(Terminal.cpp autoMarkPrompts
block), which called TextBuffer::StartOutput() and raised only a scrollbar
notification. Without a lifecycle OutputStart, _observeLifecycleCapability
never saw P|B|C, CommandFinished refused the D bit, capability stayed
below Full, and the navigation model's _effectiveResult rendered every
Succeeded/Failed as Unknown — exactly the field screenshots.

The new EnterKeypressSuppliesExecutedTransition test drives a live core
through the real flow: 133;A/133;B on the wire, echoed input, a real
SendCharEvent(L'\r'), then output and 133;D;0 — asserting no entry before
Enter, Running with the typed text after Enter, Succeeded with exit 0 and
capability Full after D, and that an Enter on an empty integrated prompt
adds no entry.

Validation performed

Environment: Windows 11 Pro 26100, MSVC 14.44.35207, Windows SDK 10.0.26100.0.

Module verification — ran, passed: bisect matrix as above; full-module
import clean in both shells; touch create/timestamp/no-truncate behavior
verified.

Repository gates — ran, passed: test-command-timeline.ps1 (now asserts
the new resource), test-visual-progress.ps1, test-privacy.ps1,
verify-version.ps1, test-release-workflow.ps1,
test-ci-classification.ps1, test.ps1 -Suite Smoke.

Static — git diff --check clean.

Compiled tests — running at PR creation: the x64 Release build of
Control.UnitTests (which compiles the Terminal.cpp, TermControl.cpp, and
new-test changes) was still building when this PR was opened; I will post the
CommandTimelineTests result (expected 44 with the new test) as a PR comment
the moment it lands, before any merge. test-shell-integration.ps1 -Shell All cannot run fully on this machine (its antivirus blocked the old file;
post-fix the compatibility commands now load locally, and the suite runs in
the release workflow's gates).

No screenshot was needed or created. winterm-site is untouched. Version
metadata is unchanged; the next prerelease bump follows separately.

Checklist

• The change is focused and does not include unrelated formatting.
• Tests were added or updated where appropriate.
• All tests claimed above actually ran and passed; the one still running is labeled as such.
• User-facing behavior and limitations are documented in this repository.
• This source/docs commit updates the root CHANGELOG.md.
• The Wiki Development-Changes.md ledger has been pushed with the final source SHA, link, summary, and checkpoint/release.
• Documentation screenshots reuse a suitable existing sanitized winterm-site asset, or no screenshot was added.
• Version or schema changes include compatibility and migration notes.
• Package identity, winterm.exe, and Microsoft Terminal coexistence remain isolated.
• No command text, terminal output, clipboard content, credentials, or private paths are logged.
• New source and script files contain the appropriate MIT license header.
• I did not include generated build output, secrets, certificates, or local absolute paths.

Source ↔ Wiki mapping

Source commit	Wiki commit	Wiki pages
2ecd3bc	890e05e	Development-Changes

Boundary

No persistent history, no output cache, no heuristic prompt detection for
unsupported shells (the Enter notification fires only for shell-established
marks), no telemetry. Workspace schema (2), docking model (1), shell protocol
(1), theme schema (1), update manifest schema (1), package identity, and
signing policy are unchanged. No winterm-site change.

Next step after this merges: prepare and publish the next alpha for local
re-testing.

[HelloThisWorld]

Compiled-test verification completed as promised: fresh x64 Release build of Control.UnitTests exits 0, and the CommandTimelineTests suite — including the new end-to-end EnterKeypressSuppliesExecutedTransition — reports Total=44, Passed=44, Failed=0. All validation claimed in the PR body is now complete.