Move the opencode_env and pi_env removal to OpenEnv 0.9.0

[sergiopaniego]

Summary

#1276 deprecated opencode_env and pi_env with removal in 0.8.0, assuming it would ship in 0.6.1. There was no 0.6.1, and it shipped in 0.7.0. The deprecation policy in .claude/docs/INVARIANTS.md (#1277) keeps a deprecated feature for at least two minor releases before 1.0, so this moves the removal to 0.9.0 in the FutureWarning, the READMEs, the tutorials and their index.

Type of Change

• Bug fix
• New feature
• Breaking change
• Documentation
• New environment
• Refactoring

Alignment Checklist

Before submitting, verify:

• I have read .claude/docs/PRINCIPLES.md and this PR aligns with our principles
• I have checked .claude/docs/INVARIANTS.md and no invariants are violated
• I have run /pre-submit-pr (or bash .claude/hooks/lint.sh and tests) and addressed all issues

RFC Status

• Not required (bug fix, docs, minor refactoring)
• RFC exists: #___
• RFC needed (will create before merge)

Test Plan

git grep "OpenEnv 0.8" only finds the generic foo_env example in INVARIANTS.md. scripts/sync_env_docs.py --check passes.

Claude Code Review

N/A. This PR was written with AI assistance (Claude Code) and reviewed by me.

---

Note

Low Risk
Documentation and deprecation warning text only; no functional or removal logic changes.

Overview
Updates every planned removal date for deprecated opencode_env and pi_env from OpenEnv 0.8.0 to 0.9.0, aligning with the two-minor-release deprecation policy after deprecation shipped in 0.7.0 instead of the originally assumed 0.6.1.

The same version string change appears in environment docs (opencode.md, pi.md), tutorial pages and the tutorials index, both env READMEs, and the FutureWarning text emitted on import in envs/opencode_env/__init__.py and envs/pi_env/__init__.py. No runtime behavior beyond the updated warning message; packages remain deprecated with Harbor as the migration path.

^{Reviewed by Cursor Bugbot for commit 65ddd42. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cursor]

Alignment Review Report

Automated Checks

• Lint: PASS (for files touched by this PR). uv run ruff check src/ tests/ passes cleanly; uv run ruff format --check and uv run usort check flag pre-existing issues in unrelated files (55 files under src//envs/, plus tests/envs/test_grid_world.py and tests/envs/test_julia_env.py, matching the known pre-existing baseline noted in AGENTS.md). Neither envs/opencode_env/__init__.py nor envs/pi_env/__init__.py — the two Python files this PR touches — appear in the formatter's flagged list.
• Debug code: CLEAN — check-debug.sh finds no debugger statements and no new print/TODO markers introduced by this diff; all hits listed are pre-existing and outside the changed files.

Open RFCs Context

• RFC 006 (Agentic RL Harness Interception) — In Review. Explicitly discusses opencode_env/pi_env and lists "consolidate opencode_env/pi_env onto core.harness.capture" as an open item (Problem 1), calling it "a scheduled obligation rather than an aspiration." This PR does not touch that consolidation work — it only adjusts the stated removal version in the deprecation warnings/docs — so it does not conflict with or pre-empt RFC 006's open decision; if anything, delaying the hard-removal date gives more room for that consolidation to land first.
• Other RFCs (000–005, 008, 010–012) have no overlap with the files changed here (docs strings and two one-line FutureWarning messages).

Tier 1: Fixes Required

None. No lint failures, debug code, uninitialized variables, type errors, missing imports, or security issues in the changed files.

Tier 2: Alignment Discussion

Principle Conflicts

None identified. No code-behavior change: this is a pure version-string edit (0.8.0 → 0.9.0) across 9 files (2 FutureWarning strings, 2 env READMEs, 2 doc pages, 2 tutorial pages, 1 tutorials index). FutureWarning (not DeprecationWarning) and stacklevel=2 are both preserved, so the deprecation mechanics in envs/opencode_env/__init__.py / envs/pi_env/__init__.py remain compliant with the .claude/docs/INVARIANTS.md deprecation policy.

The change is directly justified by that same policy: deprecation warnings for opencode_env/pi_env shipped in 0.7.0 (not the originally assumed 0.6.1, per #1276), and INVARIANTS.md requires at least two minor releases of grace pre-1.0 before removal — 0.7.0 → 0.9.0 satisfies that, whereas the old 0.8.0 target did not. I independently verified git grep "OpenEnv 0.8" only matches the generic illustrative example in INVARIANTS.md:94 (not a real deprecation target) and scripts/sync_env_docs.py --check passes, matching the PR's test plan.

RFC Conflicts

None identified. See RFC 006 note above — this PR is orthogonal to (and doesn't block) the consolidation work that RFC tracks as still open.

Summary

• 0 mechanical issues to fix
• 0 alignment points for human review
• 0 RFC conflicts to discuss

This is a clean, self-consistent bug-fix/docs PR: it corrects a deprecation-removal version to match the policy in .claude/docs/INVARIANTS.md after the deprecation's actual ship date slipped from the originally assumed 0.6.1 to 0.7.0. No further changes requested.

  

_{Sent by Cursor Automation: Pre-review}

[bot-ci-comment]

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.