[samkeen]

Follows the 2026-09 backlog reset (29 open issues down to 4: #23, #225, #230, #232). Future work starts from what real use shows.

• .github/ISSUE_TEMPLATE/observed.yml: an issue form that asks what I was doing, what I expected, what happened and how often. It applies the new observed label.

The README change that was here moved to #234, which rewrites the README, so the two PRs don't conflict.

🤖 Generated with Claude Code

[coderabbitai]

Navigate logical layers of code changes, visualize relationships, and explore their blast radius.

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Advanced

Run ID: 06654bed-43a4-4776-b464-771ea468ac18

📥 Commits

Reviewing files that changed from the base of the PR and between c1c06ea and 43c268d.

📒 Files selected for processing (2)

• .github/ISSUE_TEMPLATE/observed.yml
• README.md

Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review.

---

📝 Walkthrough

Walkthrough

Adds an observed-issue GitHub template and updates the README to describe the shipped desktop chat pane and the daily-use focus.

Changes

Observed issue reporting

Layer / File(s)	Summary
Observed issue intake and README status .github/ISSUE_TEMPLATE/observed.yml, README.md	The new issue form collects required details about what happened and how often, plus an optional vault/build description. The README describes the desktop chat pane as shipped and says daily-use issues start as observed reports.

Estimated code review effort: 2 (Simple) | ~8 minutes

Suggested reviewers: claude

Merge Risk: ⚪ Minimal · up to 3ab18

The observed-report form and README describe the intended workflow consistently. No issue identified here needs to be resolved before merging.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
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.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and concisely identifies the main change: adding an observed issue form. It is relevant to the pull request objectives.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

---

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

_{A rabbit files what happened today
With expected and actual in play
“Once” or “each time,”
The form keeps the line
While chat finds its pane on display}

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