Spec v0.1.8

Documentation-only source release from dev, following the v0.1.7 Optimization Button filepath diagnostics fix. Runtime code and convergence behavior are unchanged. Release versions use Git tags; package manifests remain at 0.1.0.

Changes

• Clarify that the optimization project comes from the selected execution invocation, not a repository name mentioned in a build prompt.
• Explain that successful discovery followed by a missing .optim error requires the owner to supply the intended process and measurable objectives in the discovered project on the execution host.
• Preserve fail-closed configuration selection; do not substitute unrelated configs or invent objectives.

The commit includes the requested wording:

Optimization Button fixed error in confusion of optimization spec filepath (convergence to upper-bound limiting)

That wording references the existing filepath fix. This release does not change the convergence algorithm: a measured plateau is not proof of an upper bound or global optimum.

Validation

• Polled the preceding spec build to completion: exit status 0; it made no code changes and diagnosed missing optimization configuration.
• All 38 Python optimizer tests passed in the build and in an independent review rerun.
• Reviewed the existing filepath diagnostic fix and new documentation diff; no release-blocking issues found.
• Whitespace checks passed. Rust/frontend/browser suites were not rerun for this documentation-only release. Live SSH and model-provider integrations were not exercised.

Only README.md and OPTIMIZE.md changed. Unrelated session logs, run artifacts, and Python caches were excluded and left untouched locally. No binary assets are attached.

Full changes: v0.1.7...v0.1.8