Add PR-based backlog workflow (start/submit/landed) #359

Closed
opened 2026-06-07 23:11:05 +00:00 by steve · 0 comments
Owner

Describe the issue.

Problem

Goal

Scope

Non-goals

Acceptance Criteria

Implementation Notes

Suggested Files or Specs To Inspect

Validation Commands

Follow-up Tasks

Implementation Summary

Added PR-based backlog workflow: backlog:start/submit/pr-status/landed commands, Forgejo PR client, issue branch/PR metadata, CI aggregate check hardening, verify-commit --mode pr, PR-aware doctor, and updated agent docs. Validated with pnpm check:all and script unit tests.

Describe the issue. ## Problem ## Goal ## Scope ## Non-goals ## Acceptance Criteria ## Implementation Notes ## Suggested Files or Specs To Inspect ## Validation Commands ## Related Issues ## Follow-up Tasks ## Implementation Summary Added PR-based backlog workflow: backlog:start/submit/pr-status/landed commands, Forgejo PR client, issue branch/PR metadata, CI aggregate check hardening, verify-commit --mode pr, PR-aware doctor, and updated agent docs. Validated with pnpm check:all and script unit tests. <!-- backlog:task_id=TASK-BACKLOG-PR-WORKFLOW source_spec=spec/src/80-maintenance/issues-backlog.md -->
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
lapis-notes/lapis#359
No description provided.