Add status_message field to client.proto Exporter

[kirkbrauer]

Continues implementation of https://github.com/jumpstarter-dev/jumpstarter/pull/606

Summary by CodeRabbit

• New Features
  • Export operations now include detailed status messaging for improved visibility into operation progress and outcomes.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

A new string field status_message with OUTPUT_ONLY behavior is added to the Exporter message in the protobuf definition, enabling textual status information to be transmitted alongside existing status mechanisms.

Changes

Cohort / File(s)	Summary
Exporter schema expansion proto/jumpstarter/client/v1/client.proto	Added status_message string field (field 5, OUTPUT_ONLY) to the Exporter message

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

• Single, isolated field addition with no logic or control flow changes
• No breaking changes to existing fields
• Clear field numbering and protobuf conventions applied

Possibly related PRs

• Add exporter status reporting #27: Modifies the same Exporter message by replacing the status enum with a shared jumpstarter.v1.ExporterStatus
• add online field to Exporter #24: Also adds OUTPUT_ONLY fields to the Exporter message (specifically the online field)
• Add ExporterStatus enum and status field #26: Adds status-related fields to the Exporter message and deprecates the online field

Suggested reviewers

• mangelajo

Poem

🐰 A message for status, so clear and so bright,
The Exporter now speaks what's wrong or what's right,
Output-only wisdom, field five takes the stage,
String words of guidance, written on the page! ✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main change in the pull request: adding a status_message field to the Exporter message in client.proto.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch add-hooks

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 1a9a9e4 and 3ca0da9.

📒 Files selected for processing (1)

• proto/jumpstarter/client/v1/client.proto (1 hunks)

🧰 Additional context used

🧠 Learnings (2)

📓 Common learnings

Learnt from: michalskrivanek
Repo: jumpstarter-dev/jumpstarter-protocol PR: 24
File: proto/jumpstarter/client/v1/client.proto:70-70
Timestamp: 2025-08-06T11:35:36.215Z
Learning: In the jumpstarter-protocol repository, the user michalskrivanek intentionally uses non-optional boolean fields for status indicators like the `online` field in the Exporter message, preferring to treat unset values as false rather than distinguishing between unset and explicitly false states.

📚 Learning: 2025-08-06T11:35:36.215Z

Learnt from: michalskrivanek
Repo: jumpstarter-dev/jumpstarter-protocol PR: 24
File: proto/jumpstarter/client/v1/client.proto:70-70
Timestamp: 2025-08-06T11:35:36.215Z
Learning: In the jumpstarter-protocol repository, the user michalskrivanek intentionally uses non-optional boolean fields for status indicators like the `online` field in the Exporter message, preferring to treat unset values as false rather than distinguishing between unset and explicitly false states.

Applied to files:

• proto/jumpstarter/client/v1/client.proto

🔇 Additional comments (1)

proto/jumpstarter/client/v1/client.proto (1)

73-73: Clean addition to the Exporter message.

The new status_message field is properly configured with OUTPUT_ONLY behavior and follows the existing pattern of status-related fields. Field numbering is sequential and correct for proto3. The addition complements the structured status enum field (field 4) by providing human-readable status details.

---

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 and usage tips.}