docs: v0.6.0 — CHANGELOG, README outcome vocabulary, ROADMAP

[teslamint]

Summary

• CHANGELOG.md: v0.6.0 entry with schema v14 breaking note, enum expansion, supersede-replaced auto-linkage, and accepted-weight verification
• README.md: "Outcome vocabulary" table listing all 5 outcome types with quality weights and semantics; updated ec_decision_outcome MCP tool description
• ROADMAP.md: v0.6.0 section with F5/F5a/F5b/F5c marked complete

Depends on #120 and #121.

Test plan

• test_schema_version_in_changelog passes (CHANGELOG has paragraph with v14 + schema)
• Full test suite green

🤖 Generated with Claude Code

[github-actions]

🧹 Tidy Pilot — Futures Assessment (assessed across 3 diff chunks)

🟢 EXPAND

Impact: This change expands future options by introducing new outcome types and enhancing the decision lifecycle, allowing for more nuanced tracking and management of decision outcomes. | This change expands future options by introducing a comprehensive outcome vocabulary for decision tracking, enhancing the system's ability to capture and analyze decision impacts.

Roadmap alignment: The change aligns with the roadmap's focus on improving decision memory for coding agents by enabling richer context and audit trails for decision-making processes.

Suggestion: Consider refactoring the record_decision_outcome and supersede_decision functions in decision_hooks.py to centralize outcome handling logic, which could simplify future modifications and enhance maintainability.

---

_{Powered by Tidy Pilot — analyzing futures, not just features}

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: e3ed40d2d1

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Align v0.6.0 release docs with published package version

This change marks 0.6.0 as a dated release (2026-04-29) and describes it as shipped, but the project metadata is still version = "0.5.0" in pyproject.toml. That mismatch can mislead users (and release automation) into expecting 0.6.0 features from the installable package before a matching version bump exists; keep these notes under Unreleased or bump the package version in the same release change.

Useful? React with 👍 / 👎.