Skip to content

v0.8.0 feat: add clean launch profiles - #19

Merged
minglong51 merged 1 commit into
mainfrom
feat/clean-profiles-v0.8.0
Aug 25, 2026
Merged

v0.8.0 feat: add clean launch profiles#19
minglong51 merged 1 commit into
mainfrom
feat/clean-profiles-v0.8.0

Conversation

@minglong51

Copy link
Copy Markdown
Owner

Summary

  • Add strict clean launch profiles with explicit environment contracts and launch-size preflight.
  • Share launch specifications across terminal and Agent View paths while preserving raw-launch compatibility.
  • Harden hub v2 compare-and-swap state and absolute tmux control-socket handling.
  • Add a tag-gated, deterministic, non-clobbering release workflow.

Test coverage

  • 72 unit tests pass.
  • Real tmux PTY integration passes.
  • Provider evidence matrix passes all 24 cells.
  • Statement coverage is 84 percent.

Pre-landing review

Four independent product, engineering, founder, and adversarial review lenses returned SHIP with no P0 or P1 findings.

Plan completion

The clean-profile release scope is complete. Broader Attention View and provider-collector work remains intentionally outside v0.8.0.

Verification

  • python3 -m unittest discover -s tests -v
  • python3 tests/hub_pty.py
  • python3 scripts/provider_evidence.py --check
  • Python syntax compilation, workflow YAML parsing, and git diff checks
  • bin/clilane --version reports clilane 0.8.0

Documentation

README usage and profile semantics are updated. No architecture boundary document exists in this repository.

Test plan

Merge only after the Linux and macOS smoke matrix passes. After merge, tag the exact green main commit, verify the deterministic release archive and checksum, then update and canary the Homebrew formula.

Co-Authored-By: OpenAI Codex <noreply@openai.com>
@minglong51
minglong51 merged commit f52c679 into main Aug 25, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant