Release v0.36.2 · dynatrace-oss/opencode-coder

Highlights

✨ Renamed the docs lifecycle command to /opencode-coder/init-or-update-docs and extended /opencode-coder/improve-doc with a discussion-first improvement flow.
🧭 Tightened canonical docs guidance so routing lives in AGENTS.md, canonical project-doc references live under ai-resources/, and user-guide project-doc references are symlinked entrypoints.
🛠️ Narrowed runtime normal-mode threshold to the minimal init+skill surfaces and hardened CI/release workflows so a real bd binary is available before integration tests run.

Renamed /opencode-coder/docs to /opencode-coder/init-or-update-docs while keeping the same docs lifecycle scope and adding optional focus context.
Extended /opencode-coder/improve-doc to support default analysis/discussion-first improvement before edits while preserving incident-driven targeted fixes.
Runtime now reaches normal mode when the opencode-coder/init command and opencode-coder skill are present, while preserving the existing bootstrap-vs-normal model.
CI and release workflows now install the official beads release binary directly so bd-dependent integration checks run reliably in GitHub Actions.

Fixed docs-command startup gating so improve-doc remains available in the intended partial-resource scenario under the narrowed normal-mode threshold.
Stabilized functional eval tracker isolation coverage so it compares pre/post bd behavior instead of assuming a pre-existing tracker in CI.
Replaced failed npm-based beads installation attempts in workflows with direct release-binary installation.

Standardized docs lifecycle consolidation guidance around canonical ai-resources sources, AGENTS-owned routing, and symlinked user-guide project-doc entrypoints.
Removed self-routing guidance from canonical topic-doc review rules and clarified source-of-truth rules for .opencode/ vs ai-resources/.

This release still carries the accepted repo-specific gap documented in docs/RELEASING.md: private-package-dependent e2e/manual coverage is required in a real release environment, but GitHub Actions does not fully enforce that coverage yet.