4. Add CLI status JSON regression coverage
Labels: good first issue, tests, cli
Body:
hermes-collab status --json is listed as a quick way to inspect local state. Add a focused regression test that checks the command returns valid JSON with the expected top-level fields, using existing CLI test patterns.
Suggested scope:
- Look at existing tests under
tests/ for CLI invocation style.
- Add one narrow test for
status --json rather than broad CLI coverage.
- Assert stable structural fields, not volatile machine-specific values.
- Keep the test independent from real runtime databases, credentials, and agent installations.
Acceptance criteria:
- A new or updated test covers the JSON status command.
- The test avoids brittle assertions on local paths, timestamps, installed agents, or private configuration.
- The narrow test command passes locally, for example
PYTHONPATH=src python3 -m unittest tests.test_startup_mode -v or the closest existing CLI test file.
- No production data, secrets, or generated runtime artifacts are required.
Why it is newcomer-friendly:
The task has a small testing surface and can follow nearby unit-test patterns without changing runtime behavior.
This issue was created from the v5.0 launch backlog in docs/launch/good-first-issues.md.
4. Add CLI status JSON regression coverage
Labels:
good first issue,tests,cliBody:
hermes-collab status --jsonis listed as a quick way to inspect local state. Add a focused regression test that checks the command returns valid JSON with the expected top-level fields, using existing CLI test patterns.Suggested scope:
tests/for CLI invocation style.status --jsonrather than broad CLI coverage.Acceptance criteria:
PYTHONPATH=src python3 -m unittest tests.test_startup_mode -vor the closest existing CLI test file.Why it is newcomer-friendly:
The task has a small testing surface and can follow nearby unit-test patterns without changing runtime behavior.
This issue was created from the v5.0 launch backlog in
docs/launch/good-first-issues.md.