Spec v0.1.4

Source release from commit f50c11d. Following the existing release convention, package manifests remain at 0.1.0; this release is versioned by the v0.1.4 tag. Earlier releases and tags are preserved.

Changes

• Add the Optimize button for recursive improvements using trusted project .optim commands, independent of the editor's unsaved content.
• Measure signed and cumulative gains, report marginal differences, and halt when all objectives sustain near-zero gains within configured tolerances. Constant positive gains do not trigger convergence merely because their differences are small.
• Discover the latest initial build through invocation metadata or narrowly parsed history, without executing history commands.
• Persist optimization output separately from file builds, recover after reload/restart, and expose manual cancellation.
• Keep optimizer progress streaming without the ordinary build timeout or 8 MiB log cap, while retaining bounded UI and recovery responses. Preserve full optimization reports from automatic seven-day cleanup.
• Fix review findings in large-log recovery and exclusion for target projects discovered outside the configured workspace. Add regression coverage and an optimizer configuration/safety guide.

The commit includes: Optimization Button for recursive improvements - and halting for marginal differences in gain...

Validation

• 116 Rust tests, 22 Python optimizer tests, 19 launcher tests, 13 frontend unit tests, and 81 Chromium browser tests passed (251 total).
• Rust formatting, Clippy with warnings denied, locked debug/release builds, shell syntax, frozen frontend install, TypeScript checks, frontend production build, and staged whitespace checks passed.
• One existing cancellation browser check timed out on the first full run. It then passed five isolated repeats and the full 81-test rerun; the initial failure's cause was not confirmed.
• Live provider calls and production SSH hosts were not exercised. Integration tests use isolated local fixtures and the actual remote scripts.

Upgrade And Safety

Rebuild/restart the local Rust server and reload the browser. Optimization requires Python 3.10+ on the remote Linux host and a trusted project .optim file; no project objectives are bundled. See OPTIMIZE.md.

Optimization has no automatic iteration or runtime cap. Commands can modify files, use credentials, access the network, and incur costs. Budget report storage and use Stop run when needed. Plateau detection does not guarantee optimality or positive gain. Locks are advisory; confirm descendant cleanup before restarting work after an optimizer crash. Cancellation cannot be guaranteed through a broken connection: reload output and retry Stop run if remote work remains active.

Generated logs, private session artifacts, and Python caches were excluded and left untouched locally. This is a source release with no uploaded binary assets.

Full changes: v0.1.3...v0.1.4