Blocking this release PR for staleness. The branch is 8 commits behind current master and only adds CHANGELOG.md for an older v1.1.0 snapshot. Since then, master has gained additional merged work including the developer testing guide (#81), shared API pagination/failure handling (#83), LLM-Agent-SHA Phase 0 (#87), and Jenkins read-only design docs (#88). A release/version PR should be rebased or regenerated from current master so the changelog/release contents reflect the actual release surface before merge. I did not run the full release checks because this needs refresh first.
007b5dad14
Merge pull request 'docs: Jenkins read-only build status tools design (#72)' (#88) from docs/issue-72-jenkins-readonly-design into master
Reviewed PR #88. Checks passed: py_compile for mcp_server.py/manage_labels.py/gitea_auth.py, bash -n scripts/clear-provenance, full pytest suite, and git diff --check. Manual review confirms this is documentation/design only, read-only Phase 1 only, no Jenkins implementation code, credentials remain isolated from Gitea MCP, console tail behavior is bounded/redacted, mapping is deferred to #77, and triggers/deploys/rebuilds/parameterized launches are excluded.
Discussion: Proposed LLM-Agent-SHA Decision and Implementation Shape
This is LLM feedback for discussion only. It is not yet the final owner decision.
1. Recommended Direction
Adopt…
53e061bafd
Merge pull request 'fix: add shared API pagination and failure handling (#67)' (#83) from fix/issue-67-api-pagination-failures into master
Reviewed PR #83 at cfe3ff67556a159d54c9f02da3ff94928ea3b385. Scope is limited to shared Gitea API reliability/pagination handling and tests. Changed files match expected, pagination is wired only into list PRs/issues/labels, targeted and full test suites pass, and no auth/profile/merge/review/tracker behavior or Jenkins/GlitchTip work is included.