BetterWright 2.9.0

BetterWright 2.9.0 adds on-demand Pi evidence history and fixes Cookie Sync and CLI startup regressions.

Pi evidence

• Routine responses include the current checklist and archivedCount, so earlier journeys no longer inflate every tool response.
• browser_evidence list returns a paged journey index; get retrieves full current or archived evidence by exact name without changing state.
• Proofs include retained image references linked to the original worker artifact. Private copies survive worker quota eviction until extension session shutdown.
• Proof calls report a single post-operation status. Missing, unreadable, empty, oversized, or unretainable screenshots cannot prove pending requirements. Reproof requires another audit.
• Audit and history remain accessible after the browser step budget is exhausted.

Fixes

• Relative Cookie Sync source paths resolve against the caller's working directory, including across an existing daemon. Malformed paths still receive canonical validation.
• includeSession with explicit cookie paths reports the specific unsupported-option error.
• CLI launch errors name the offending environment variable. Daemons respect explicit configuration received over stdin; unrelated invalid launch defaults do not block management commands.

Migration and retention

This minor release replaces automatic archivedChecklists output with archivedCount. Use { "operation": "list" } followed by { "operation": "get", "name": "journey-name" } for history. See the Pi integration guide.

Evidence retention covers one Pi extension session. It does not provide cross-process recovery. Retained proof copies use disk outside the worker quota and are deleted at session shutdown. get reports whether each copy is currently readable.

Includes the useful fixes from #236 and #237 and resolves #238. The other fixes proposed in #237 were already included in 2.8.9.