docs: add CI pipeline receipt example

[hummbl-dev]

Summary

• Add a CI pipeline execution receipt worked example.
• Include command, inputs, outputs, environment fingerprint, exit status, and verification chain.
• Keep the example candidate/non-canon.

Validation

• git diff --check passed.

Refs #5

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: a707084b-beeb-4d77-91c1-a7b180e6afab

📥 Commits

Reviewing files that changed from the base of the PR and between 6a5e025 and 5495b1a.

📒 Files selected for processing (1)

• examples/ci-pipeline-receipt-worked-example.md

---

📝 Walkthrough

Summary by CodeRabbit

• Documentation
  • Added a worked example showing a CI pipeline execution receipt in a clear Markdown format.
  • Includes a sample receipt packet with command details, inputs/outputs, environment fingerprinting, exit status, and verification chain.
  • Provides a short summary of what the example covers for easier reference.

Walkthrough

Adds a new documentation file, examples/ci-pipeline-receipt-worked-example.md, containing a worked example of a CI pipeline execution receipt packet in JSON format, with fields for authority, command, inputs/outputs, environment fingerprint, exit status, verification chain, and a summary bullet list.

Changes

Worked Example Documentation

Layer / File(s)	Summary
Receipt packet worked example examples/ci-pipeline-receipt-worked-example.md	New Markdown doc presents a scenario description and a JSON-shaped receipt packet example (authority, command, inputs/outputs with digests, environment fingerprint, exit status, verification chain), followed by a bullet list summarizing scope and clarifying it does not change operator-authority surfaces or introduce new terminology.

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

Possibly related issues

• good-first-issue: add example execution receipt for a CI pipeline run #5: Requests the same kind of CI pipeline execution receipt example with matching core fields and constraints that this PR adds.

Poem

A rabbit hops through logs and lines,
Stamping receipts with digest signs,
No powers changed, just words made clear,
A worked example, crisp and dear.
🐇📄✨ Hop on, review is near!

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly matches the change: a new documentation example for CI pipeline receipts.
Description check	✅ Passed	The description accurately summarizes the added receipt example and its validation note.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
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 unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch docs/codex/issue-5-ci-receipt-example

Warning

Tools execution failed with the following error:

Failed to run tools: 13 INTERNAL: Received RST_STREAM with code 2 (Internal server error)

---

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