test: verify manual term candidates on installed 0.5.4 (M5.5 complete)

[kun002]

Scope

Complete the M5.5 installed acceptance and record it:

• app-smoke vscode-project-candidate: the dictionary wait now accepts the persisted symbol after \tmanual\t as well as \tlanguage_server\t, so user-approved terms can drive the scenario
• host evidence: on the installed 0.5.4-preview, a fresh smoke workspace was ingested by the real Adapter, the term was injected via a minimal CIPM UPSERT_TERM client while the lease was live, and the smoke observed the candidate window (CeShiShuYu 〔项目·术语〕 first, 91,899 changed pixels) and committed it inside a TypeScript comment (final text ends // CeShiShuYu); Passed = true with screenshot
• session diagnostics recorded: the TSF server death cascade, KEYEVENTF_UNICODE injection bypassing the IME pipeline, and the M3 comment→Chinese automatic switch remaining unverified
• all test workspaces and dictionaries were removed via CIPM REMOVE_PROJECT; the real dictionary SHA-256 stayed byte-identical throughout

Verification status

Layer	Status	Evidence
real_machine_verified	complete for M5.5	m55-installed-acceptance2.json + .project-candidate.png in artifacts/contextime-0.5.4-staged/; docs/evidence/m5-approved-terms-host-verification.md updated to M5.5_INSTALLED_CANDIDATE_ACCEPTANCE = VERIFIED

Known unverified boundaries

M3 real-TSF automatic comment switching, clean machine, LAN, RDP, and the installer reboot-prompt fix (0.5.5 task) remain open.