Skip to content

chore: prepare v3.0.0 beta 3 public beta#123

Open
thunderdew-dawn wants to merge 14 commits into
v3/alphafrom
release/v3-beta-3-prep
Open

chore: prepare v3.0.0 beta 3 public beta#123
thunderdew-dawn wants to merge 14 commits into
v3/alphafrom
release/v3-beta-3-prep

Conversation

@thunderdew-dawn

Copy link
Copy Markdown
Owner

Summary

  • Prepares release/v3-beta-3-prep for PR into v3/alpha.
  • Corrects premature v3.0.0 RC1 metadata back to v3.0.0 Beta 3 public beta.
  • Uses 3.0.0b3 for Python/package/app versions.
  • Uses v3.0.0-beta.3 for GitHub release/tag-facing references.
  • Uses 3.0.0-beta.3 for SemVer-style registry/server version fields.
  • Updates README, tests, eval metadata, server manifest, and agent-doc snapshots accordingly.

Why

RC1 was premature. The current v3 line should remain public beta until release-candidate blockers are explicitly cleared.

Verification

  • python -m json.tool server.json >/dev/null
  • python -m json.tool evals/evals.json >/dev/null
  • JSON validation for edited agent-docs machine snapshots
  • Version smoke tests for pyproject, server.json, and fls_pilot.version
  • python -m pytest tests/test_workflow_registry.py tests/test_pack_manifest.py tests/test_control_center.py tests/test_pack_manager.py
  • Optional: python -m build && python -m twine check dist/*
  • Optional: python -m mkdocs build --strict
  • Optional: python -m ruff check .

Intentionally not changed

  • No nested chore branch created.
  • No Git tags created, moved, deleted, or force-pushed.
  • No PyPI publishing.
  • No runtime behavior changes.
  • No FL Studio automation changes.

Release artifact note

If v3.0.0-rc.1 or 3.0.0rc1 was already published externally, maintainers must decide separately whether to mark it as mistaken, delete/yank where possible, or publish a corrective note. This PR only corrects repository metadata.

Add Level 1/Level 2 routing audit modes, Channel Rack vs Mixer discrepancy findings, profile-driven template-compliance checks, Level 2 meter evidence handling, and the psytrance routing profile. Update Control Center UI, MCP routing review inputs, workflow declarations, evals, architecture snapshots, and regression coverage.

closing #122
Implement Level 1 static, Level 2 live peak watch, and Level 3/4 rendered evidence placeholders across MCP, Runtime, and Control Center. Add finding evidence metadata, conservative psytrance guidance, docs, evals, architecture snapshots, and regression coverage.

closes #124
…and control center UI enhancements for improved workflow transparency.
…intent confirmation, risk scoring, and cleanup plan gating
…execution state management in Control Center
…standardized findings, and decision requirements
…lows and update organizer UI status reporting.
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