[hdcodedev]

Context

The README listed only pull requests, so issues reported in Kilo did not show up anywhere. This adds those issues: a counts table under the PR stats, and issue rows in each month's table. Config controls which statuses are shown. It starts with Kilo repos only, showing open issues and issues fixed by a merged PR.

Implementation

• New issues block in oss-contributions.json sets the repos and statuses. OPEN is still open. FIXED is closed with a merged linked PR. CLOSED is closed without one. An empty list shows all three.
• Issues are fetched with their linked PRs (fetch_authored_issues). Each issue's status comes from its state and whether a linked PR is merged (issue_status).
• The issue counts table uses the same stats_projects groups, so both Kilo repos add up into one row. Issues are left out of the merged-PR counts.
• Issue rows have their own icons (🟡 open, ✅ fixed, ⚫ closed) and start with 📋 "Issue #N", so they stand apart from PR rows. Open or merged linked PRs are linked after the title. The legend lists the issue statuses.
• The JSON snapshot gains issue_stats and a kind field on each row.
• Added tests for issue status, status filtering, untracked and private repos, row grouping, PR links, and issue counts.

Known limits

• An issue is listed under the month it was opened, even when it was fixed later. PRs work the same way on main.

Testing

• (agent) python3 -m unittest discover -s __test__ -p 'test_*.py': 46 tests pass.
• (agent) Ran generate_readme.py against GitHub. It found 9 Kilo issues (6 open, 3 fixed) and rendered the new table and rows. The regenerated README.md and README_DATA.json are not committed, so the scheduled CI run produces them.

How to test

1. Run the Update README from JSON config workflow from the Actions tab after merge.
2. Open README.md. Under the PR stats table there is a Kilo Code row with 🟡 Open, ✅ Fixed, and Total Reported counts.
3. In the October 2026 section, a 🟡 row lists 📋 Issue #... items, some followed by → #<PR> links.