osprey-stress: refresh measure/open-loop wording now that #236 merged

[julietshen]

The JetStream input stream sample (#236) has merged, so the "once #236 lands" wording in the osprey-stress measure stub and the consumer/reporter docstrings is now stale.

This is a wording-only change (no behavior change):

• measure (open-loop) is described as "not yet implemented" rather than "waiting for [examples] Bluesky/ATProto sample integration (input stream, rules) #236 to land" — the external-source prerequisite now exists (the JetStream stream is one such source); the subcommand itself just isn't built yet.
• Makes clear that run (closed-loop synthetic) is the working stress test.
• Updates the consumer/reporter docstrings to reference the JetStream input stream as an example external source instead of "once [examples] Bluesky/ATProto sample integration (input stream, rules) #236 lands".

Follow-up: actually implementing the open-loop measure mode is tracked separately.

🤖 Generated with Claude Code

Summary by CodeRabbit

• Documentation
  • Clarified that the measure command is an open-loop measurement mode that is not yet implemented.
  • Updated CLI guidance to use run instead.
  • Expanded documentation to describe support for externally produced event sources, including JetStream input streams.
  • Clarified that per-event latency cannot be calculated in open-loop mode.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: eb3c514a-68f1-48b4-aa9d-3d1c1fe907cb

📥 Commits

Reviewing files that changed from the base of the PR and between a5768a5 and 0633fa6.

📒 Files selected for processing (3)

• osprey_worker/src/osprey/worker/stress/cli.py
• osprey_worker/src/osprey/worker/stress/consumer.py
• osprey_worker/src/osprey/worker/stress/reporter.py

---

📝 Walkthrough

Walkthrough

The stress harness now describes measure as an unimplemented open-loop mode, directs users to run, and generalizes external-source documentation to include the JetStream input stream.

Changes

Stress harness open-loop messaging

Layer / File(s)	Summary
Measure mode guidance osprey_worker/src/osprey/worker/stress/cli.py, osprey_worker/src/osprey/worker/stress/consumer.py, osprey_worker/src/osprey/worker/stress/reporter.py	CLI help and stub output identify measure as unimplemented open-loop functionality and direct users to run; stress harness docstrings describe external input sources, including JetStream.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Possibly related PRs

• roostorg/osprey#367: Introduced the related stress harness measure stub and CLI messaging.

Suggested reviewers: exbreder

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately summarizes the wording refresh for measure/open-loop docs after #236 merged.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch julietshen/stress-236-language

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}