Review every repository
Start from the Night Summary or select the Feature in the Pulse. Follow each repository’s pull request link to GitHub. Compare the changed files with the intended Feature, the Cards in this repository list, recorded Checks, and Verification, clause by clause. A multi-repository Feature can have several pull requests. Review the whole Feature rather than treating one repository’s green CI as evidence that the customer outcome is complete. A repository with no pushed branch can have no pull request; inspect the Feature’s explicit no-pull-request notes and landing failures when an expected link is absent.Recognize a Partial Landing
Planned screenshot
A Partial Landing pull requestPoint out where a pull request identifies incomplete Work Cards and unmet clauses.
partial roll-up, the Night stamp and Feature Card link, Incomplete Cards (every repository), Definition of Done clauses unmet, and the carried-forward list. Use a result that has at least one completed Card and one unfinished Card; include a held Todo Card if demonstrating sequential work. Use a second capture for the clause-by-clause Verification section if it cannot fit legibly. A rehearsal can demonstrate the board records, but cannot produce this GitHub screenshot because it never opens pull requests. Remove private repository names and sensitive content from the demonstration data before capture.
A Partial Landing explicitly lists unfinished work across all repositories, its state and reason, and unmet completion clauses. A later Card held behind an earlier Card can remain Todo and still be named as unfinished. Read not checked clauses separately from unmet clauses: an unavailable check is not a successful check.
The pull request body records the Night it describes and links to the live Feature Card. Merging all the Feature’s pushed-repository pull requests closes a Partial Landing unverified and archives its Cycle. Merging only some does not close the Feature. Unfinished work can be carried forward for later Adoption; merging does not declare those clauses complete.
Review stacked pull requests in order
Several Features can land sequentially in one Night. A successor pull request can target the predecessor Feature Branch instead of the repository’s default branch. Read the Stacked on notice and inspect the base branch in GitHub. Merge the predecessor first. If you merge the successor first, it merges into the predecessor branch and only reaches mainline when the predecessor does. If the predecessor has merged but the successor still targets its branch, change the successor’s base to the default branch before merging. The Feature group and its Inspector show awaiting-merge Features, predecessor links, and which repositories are in mainline. Leaving Features unmerged can fillunmerged_features_max and pause further authoring.