v0.36.2

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.

What's Changed

Changed

• 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

• 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.

Docs

• 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/.

Breaking Changes

• None.

Notes

• 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.

v0.36.1

What's New

• Added and exported normalizeConfigKey() with unit-test coverage to keep config-key handling consistent.
• Simplified runtime diagnostics to high-level resource/opencode-coder signals and streamlined manual bootstrap guidance.
• Clarified canonical documentation ownership and release entry points, including the accepted private-package test limitation for release-test coverage.

Notes

• Release-test coverage may still be limited in environments without access to private package @hk9890/opencode-dynatrace, as documented in the repository's release guidance.

v0.36.0

Highlights

• Completed OpenCode skill-creator parity and stabilized packaging by vendoring skill-creator resources.
• Refactored bootstrap boundaries and improved published command UX, especially the inspect-first /opencode-coder/init flow.
• Added reliability fixes around Unix socket detection and tightened planning/docs lifecycle guidance.

Added

• Finished OpenCode-native skill-creator parity workflow and captured parity evidence.

Changed

• Split opencode-coder bootstrap responsibilities from resource-backed workflows.
• Reworked published command content for clearer user-facing guidance.

Fixed

• Corrected Unix socket detection in project-path test paths using fs.stat().isSocket() semantics.
• Replaced symlink-based skill-creator wiring with vendored files for stable packaging/install behavior.

Docs

• Tightened planning and docs lifecycle guidance.
• Trimmed overly specific packaging details in overview/contributor docs.

Breaking changes

• None.

v0.35.0

Summary

• require explicit saved project enablement before opencode-coder activates project-local behavior, with /opencode-coder/init as the documented setup entry point
• preserve active behavior for legacy projects during upgrade and clarify disabled-mode precedence for the hard-disable override
• stabilize manual-launcher/integration validation so missing opencode or private-package auth degrades cleanly instead of hanging or crashing release checks

Docs

• refresh README, testing, and release guidance to match the explicit enablement model and release verification workflow

v0.34.3

Fixed

• Prevent blank-screen startup hangs when a project is not fully initialized and the readiness warning toast never resolves.
• Make the startup readiness warning toast fire-and-forget so OpenCode startup can continue in degraded mode.

Added

• Add an integration regression test covering the non-ready startup path when the toast promise stalls.

Docs

• Update stale bd sync references to supported bd dolt persistence commands.

v0.34.2

What's New

Fixed

• Prevent startup from creating .coder/, .coder/logs/, or ai.package.yaml in repositories that have not opted in.
• Replay early startup diagnostics into .coder/logs once file logging is enabled so opted-in projects keep a complete startup timeline.
• Make opted-in startup integration coverage deterministic across environments by removing a debug-only assertion.

Added

• Add real filesystem integration coverage for both the no-.coder startup path and the opted-in .coder startup path.

v0.34.1

Fixed

• Prevent startup from auto-bootstrapping aimgr or creating project-local files when .coder is absent.
• Keep /init as the explicit opt-in setup flow and create .coder there when needed.

v0.34.0

What's New

Added

• Added project-local plugin logs (.coder/logs/coder-YYYY-MM-DD.log) with retention, plus startup timeout support to keep initialization bounded and diagnosable.

Fixed

• Improved CLI availability checks for aimgr/bd by handling timeout conditions gracefully and continuing in degraded mode instead of hanging or misreporting tool absence.

No breaking changes in this release.

v0.33.1

What's Changed

Changed

• startup now waits for aimgr initialization and can auto-repair unhealthy resources before project detection and default-agent selection
• project context generation no longer includes unused git.platform and git.remote metadata

Fixed

• stale readiness no longer blocks orchestrator as the default agent after successful aimgr remediation
• /coder/status now probes supported plugin install scopes instead of assuming a single package path
• plugin integration tests now stub startup beads availability checks so CI no longer fails from background toast leakage

Docs

• updated coding and release docs to match the current startup, repair, and verification flow
• clarified GitHub Packages verification guidance and added Scion integration brainstorming notes

Breaking Changes

• None

v0.33.0

Highlights

• Added a new /simplify workflow command to help review and simplify recently changed files with the opencode-coder process.
• Migrated repository and package identity to dynatrace-oss, including release/install references for @dynatrace-oss/opencode-coder.
• Improved documentation quality and workflow guidance for setup, GitHub task sync, and acceptance review task patterns.
• Tightened beads workflow guidance by enforcing skill-loading expectations for agents and updating bd command usage to current v0.59.0-compatible commands.

Added

• /simplify command: Added a dedicated workflow command to review and simplify recently changed files using the opencode-coder process.

Changed

• Repository/package identity migration: Updated project and package identity to dynatrace-oss, including install and release references for @dynatrace-oss/opencode-coder.
• Project setup and workflow docs: Consolidated and clarified setup guidance, including GitHub task sync workflow and acceptance review task patterns.

Fixed

• Agent workflow enforcement: Improved agent guidance to consistently load required skills for beads issue workflows and improved reviewer comment quality expectations.
• Beads command examples: Replaced invalid bd command usage with current v0.59.0-compatible commands.

Breaking Changes

• None.