Repository navigation
Close delivered pm items and keep in progress for active work only - #178
Merged
Merged
Conversation
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
There was a problem hiding this comment.
Your trial has ended. Reactivate Greptile to resume code reviews.
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars.
 |
Reviewer's guide (collapsed on small PRs)Reviewer's GuideThis tracker-only sweep verifies PM items against merged PRs, acceptance evidence, and repository history, closing proven deliveries, reopening incomplete or unsupported work, releasing stale claims, and updating append-only audit records and changelog placement; it does not change production functions. Flow diagram for tracker item closeout reviewflowchart TD
A[In-progress and open PM items] --> B[Inspect tracker records]
B --> C[Verify merged PR and acceptance evidence]
C --> D{Delivery fully proven?}
D -->|Yes| E[Set status to closed]
D -->|No| F{Active work remains?}
F -->|Yes| G[Keep status in_progress]
F -->|No| H[Set status to open]
C --> I[Release stale claims]
E --> J[Append audit history and update changelog]
G --> J
H --> J
I --> J
File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
The in-progress sweep closed delivered items with completed_at set to the reconciliation time. Analytics that read completed_at as the delivery time (cycle time, recall utility, burndown) then see work finish up to weeks late. Each closure now carries the cited PR's merge time as completed_at; closed_at keeps the tracker reconciliation time. Recorded with pm update --completed-at, so the correction is an appended history event.
There was a problem hiding this comment.
Your trial has ended. Reactivate Greptile to resume code reviews.
Owner
Author
|
Orchestrator review of this sweep (done by hand; review bots here are rate-limited or not enabled):
Merging once CI is green on this head. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Close verified deliveries and keep in progress reserved for active work. Every original in-progress and open item was checked against full tracker records and merged/open PR claims, comments and acceptance criteria. Incomplete or ambiguous work remains open. Current stale assignments are released; historical claim identities remain provenance.
Blocked by the pinned SDK; owner compatibility decision pending:
pm-github-f1ev(in_progress): Verified delivered, but the repository-pinned SDK refuses all mutations with project_runtime_item_format_incompatible: existing linked-test update metadata requires format 2 while the consumer floor remains 2026.10.5. The prepared 2026.10.10 peer/manifest minimum change awaits owner approval; no safeguard or evidence was removed.pm-github-2o9k(in_progress): Verified delivered, but the repository-pinned SDK refuses all mutations with project_runtime_item_format_incompatible: existing linked-test update metadata requires format 2 while the consumer floor remains 2026.10.5. The prepared 2026.10.10 peer/manifest minimum change awaits owner approval; no safeguard or evidence was removed.Retained open after review:
pm-github-4a03: No implementing merged PR establishes full delivery of the recorded scope.pm-github-4cuz: No implementing merged PR establishes full delivery of the recorded scope.pm-github-vhi6: PR 174 raises the c8 heap allowance and reduces fixtures, but explicitly leaves bounded coverage aggregation unfinished; no active work.Validation: package changelog generation/check, pinned strict tracker health with required merge drivers under isolated Git identity, changed-item history verification, independent original-history prefix checks, linked
git diff --check, and public added-text/scope checks passed. Existing history records are unchanged. No production function changed, so source-function revert proof is inapplicable; mainline ancestry, acceptance and lifecycle/history checks provide the evidence.Where strict health required it, the repository-pinned
pm merge installregenerated the extension merge fence. Existing historical advisories are retained; no history normalization or repair was used. The pm-vcs text self-host archive is regenerated and independently checked when applicable.The PR CI runs complete
npm run release:checkandbun run release:check(nativejust release-checkfor Rust). Final exact-head CI results are reported separately; pending, skipped and neutral review checks are not approval.Commit:
ae4f8f3b82e1141b720b7fb5fd42e48124b3831e. The sweep audit remains open with its claim released for orchestrator review. No PR is merged.Summary by Sourcery
Reconcile project-management records so delivered work is closed, active work remains in progress, and incomplete or blocked items stay open for follow-up.
Enhancements:
CI:
Chores: