Add host repository inventory to CLI and /bot - #16
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Operators can now inspect every registered bot repository on a host instead of opening each checkout and guessing whether polling is active.
opencode2-automation listworks outside Git and without a service;/bot→ Repositories reads the connected server's inventory. Both show checkout/owner paths, base branches, timestamped dispatcher and scheduler readings, task counts, and concrete blocked issue keys.initand plugin activation register owners.list --discover <root>imports older inactive standard configurations without GitHub requests or service activation, with explicit traversal limits and warnings. Independent atomic component snapshots distinguish running, paused, stopped, stale, missing, and unconfigured owners. Reading inventory never starts another bot or changes a task, and registry failures do not stop automation.Updated README, runtime/configuration/installation/architecture/advanced references, affected startup and TUI workflow diagrams, AGENTS documentation map, and Unreleased notes. Reviewed all eight workflow sections; execution, verification, publication, and recovery transitions are unchanged.
Validation: full application check (lint, types, unit/integration tests, native TUI rendering, build); focused inventory/UI tests including offline CLI, migration/worktree exclusion, concurrent registration, stale/dead processes, failures and task counts; final lint/types/build; isolated package installation including
list --json; all eight Mermaid diagrams and 82 local documentation links.Targets
devel. This does not publish a release or deploy the server. After deployment, reopen TUI clients; activate existing owners or uselist --discoverto register inactive standard configurations under the service user's state directory.