List view
This milestone delivers the first usable version of **release-oppa** focused exclusively on repository inspection. The goal is to establish a stable, read-only inspection engine with a well-defined plugin contract, using Git as the built-in baseline inspector. No planning, version mutation, or publishing is included in this milestone. By the end of this milestone, users should be able to run a single command (`oppa inspect`) in any repository and receive a deterministic, machine-readable report describing repository state and plugin findings. Plugin authors should be able to implement and load new inspection plugins without modifying the core. ### Scope - Implement `oppa inspect` with text and JSON output - Built-in Git inspection (branch, HEAD, dirty state, remotes, tag summary) - Plugin discovery, detection, and execution - Stable inspection report schema with plugin-namespaced findings - Reference inspection plugin (e.g., Dockerfile inspector) - Configuration loading and plugin-scoped config passing - Deterministic output suitable for CI consumption ### Out of Scope - Version planning or semantic version calculation - File mutation or local changes - Git tagging or publishing - Registry, package manager, or remote write operations - Environment, staging, or promotion concepts ### Success Criteria - `oppa inspect` works in arbitrary Git repositories - All operations are strictly read-only - JSON output is stable and test-covered - Adding a new plugin requires no core changes This milestone establishes the architectural foundation on which future planning, apply, and publish capabilities will be built.
No due date