---
source: crates/shiplog-render-md/src/lib.rs
expression: result
---
# Summary
**Window:** 2024
**Workstreams:** 1
**Events:** 1 PRs, 0 reviews, 0 manual
**Coverage:** Partial
**Sources:** github
**Warnings:**
- ⚠️ API rate limit hit
## Workstreams
### Feature
**Evidence anchors**
- [PR] Add feature (1970-01-01) — [owner/repo](https://github.com/owner/repo/pull/1)
**Suggested claim prompts**
- What changed for users, operators, or maintainers?
- Which risk, delay, or repeated work did this reduce?
- Which evidence anchor best proves the change?
- What follow-up or gap should a reviewer know about?
_PRs: 1, Reviews: 0, Manual: 0_
## Receipts
### Workstream: Feature
- [PR] Add feature (1970-01-01) — [owner/repo](https://github.com/owner/repo/pull/1)
## Coverage and Limits
Included:
- GitHub: 1 event
- Query slices: 1 slice, fetched 50 of 100 reported results
Skipped:
- None recorded
Known gaps:
- Overall completeness is Partial
- API rate limit hit
- 1 query slice reported incomplete results
- 1 query slice fetched fewer results than reported
Details:
- **Date window:** 2024-01-01 to 2024-12-31
- **Mode:** test
- **Sources:** github
- **Completeness:** Partial
- **Query slices:** 1
- ⚠️ 1 slices had incomplete results
- **Slicing applied (API caps):**
- test: fetched 50/100 (50%)
## Appendix: All Receipts
### Feature
- [PR] Add feature (1970-01-01) — [owner/repo](https://github.com/owner/repo/pull/1)
---
## File Artifacts
- `ledger.events.jsonl` (canonical events)
- `coverage.manifest.json` (completeness + slicing)
- `workstreams.yaml` (editable clustering)
- `manual_events.yaml` (non-GitHub work)