Repository navigation
Close delivered pm items and keep in progress for active work only - #114
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 sweep removes all active in-progress claims by closing five deliveries verified through merged PR evidence, reopening or retaining items whose acceptance is incomplete or ambiguous, releasing stale ownership, and recording the append-only audit history while regenerating the changelog. No production code changes are included; validation covers tracker integrity, history prefixes, changelog generation, whitespace, privacy/scope, and release checks. Flow diagram for evidence-based tracker status sweepflowchart LR
A[Audit tracker items] --> B{Complete merged evidence?}
B -->|Yes| C[Close item]
B -->|No or ambiguous| D[Keep or reopen as open]
A --> E{Stale ownership?}
E -->|Yes| F[Release claim]
E -->|No| G[Retain ownership state]
C --> H[Append history and regenerate changelog]
D --> H
F --> H
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.
Retained open after review:
pm-rust-b4yl: No merged implementation establishes completion of the recorded scope; retain the existing open work.pm-rust-u4al: No merged implementation establishes completion of the recorded scope; retain the existing open work.pm-rust-crash-harness: Returned to open in the 2026-10-24 sweep: Open PR Detect crash recovery divergence with replayable native and published checks #104 carries the reusable kill-corpus harness; merged PR 105 fixes lock recovery but is not complete harness delivery. Review and full harness acceptance remain pending, with no active agent established.pm-rust-s6j4: Returned to open in the 2026-10-24 sweep: Later benchmark evidence still records unsupported workspace-memory rollups on large trackers, which are explicitly within this orientation task; PR 98 does not establish full acceptance.pm-rust-local-packet-deadline: No merged implementation establishes completion of the recorded scope; retain the existing open work.pm-rust-wdj4: Returned to open in the 2026-10-24 sweep: PR 102 supplies measured optimization and preserves native before/after behavior, but reports only 2/27 native/oracle output matches and 0/9 write-storage matches. The recorded byte-parity criterion is ambiguous, so performance evidence alone cannot close it.pm-rust-bench-workflow: No merged implementation establishes completion of the recorded scope; retain the existing open work.pm-rust-comment-lock-receipt: No merged implementation establishes completion of the recorded scope; retain the existing open work.pm-rust-qhem: Returned to open in the 2026-10-24 sweep: PR 101 certifies its targeted parity suite, but later item comments record native/oracle differences in ordinary read/write outputs and all nine write artifacts. Complete parity acceptance remains ambiguous and is retained for review.pm-rust-wc8b: No merged implementation establishes completion of the recorded scope; retain the existing open work.pm-rust-9bci: No merged implementation establishes completion of the recorded scope; retain the existing open work.pm-rust-4jq3: No merged implementation establishes completion of the recorded scope; retain the existing open work.pm-rust-bu9t: No merged implementation establishes completion of the recorded scope; retain the existing open work.pm-rust-vuwe: No merged implementation establishes completion of the recorded scope; retain the existing open work.pm-rust-373x: No merged implementation establishes completion of the recorded scope; retain the existing open work.pm-rust-tdps: No merged implementation establishes completion of the recorded scope; retain the existing open 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:
9c5cdf3e1a667cb95fd397349200477d8ec446d9. The sweep audit remains open with its claim released for orchestrator review. No PR is merged.Summary by Sourcery
Reconcile project-management records so verified deliveries are closed, incomplete work remains open, and active ownership reflects only current work.
New Features:
Bug Fixes:
Enhancements:
Documentation:
Tests: