Repository navigation
[ADHD] v0.6.0 — scheduled Git fetch and post-push refresh #52
Description
Parent: #51
Goal
Remove routine manual repository fetching while preserving every draft and unpushed Git commit.
Focus
Verify per-repository automatic fetch settings on current main: opt-out and a custom interval in Overview → Automatic fetching, then close #52.
Next
- Confirm scheduled fetch, post-push refresh and per-repository policy behave on
main(or the v0.6.0 build from release PR chore(main): release 0.6.0 #41). - Close [ADHD] v0.6.0 — scheduled Git fetch and post-push refresh #52 and tick it in parent [ADHD] v0.6.0 — automatic Git sync, deployment routing & dashboard #51.
- Keep inbound webhooks ([ADHD] v0.6.0 — signed Git forge push receiver #53), deployment routing ([ADHD] v0.6.0 — per-stack deployment bindings and manual trigger #54–[ADHD] v0.6.0 — selective deploy routing and idempotency #55), dashboard ([ADHD] v0.6.0 — calm, actionable workspace dashboard #56) and release/security gate ([ADHD] v0.6.0 — release verification and documentation #57) in their own slices.
Resume
Check out main at or after da55d99 and open Overview → Automatic fetching for one repository. docs/internal/automatic-fetch-review.md has the timing, migration and queue/lock notes.
Done
- PR #59 merged: global polling, dedicated attempt/failure/change timestamps, durable post-push follow-up and Git/queue safety regressions.
- Follow-up [ADHD] Automatic fetch — per-repository policy follow-up #60 implemented in PR #62: persisted per-repository enabled/nullable interval settings, precedence, strict API/service validation, effective policy, compact accessible controls, safe migration and docs.
- PR #62 merged on main as
da55d99(2026-10-20), closing [ADHD] Automatic fetch — per-repository policy follow-up #60. It is listed in the pending v0.6.0 release PR chore(main): release 0.6.0 #41.
Remaining completion gate
- Global scheduled and durable post-push fetching implemented and merged (feat(sync): schedule background Git fetches and refresh after push #59).
- Per-repository settings implemented, tested, documented and merged (feat(sync): add per-repository automatic fetch settings #62).
- Verify on main before closing [ADHD] v0.6.0 — scheduled Git fetch and post-push refresh #52.
No release, image publication or production deployment has been performed. #52 remains open.
Made with ADHD Progress Hub
Activity
uniskela commentedon Oct 20, 2026
Done
PR #59 remediation is pushed at 1848cb5: deterministic post-push race fix with one durable coalesced job, workspace/repository failure isolation, dedicated attempt/failure/change timestamps and focused repository status. Local check/build/migration/audit passed; Playwright 33 passed with 9 intentional platform skips. Controlled Docker integration: 61 passed; public-clone smoke, restart, disabled worker and missing-key rejection passed. All original Kody threads have individual evidence-based replies; another code/business review is requested.
Next
Review new CI/Kody results on #59. Implement repository-specific fetch policy in immediate follow-up #60; this issue remains open until that acceptance work is done. Security findings are being handled separately, without mixing changes into #59.
Resume
Open PR #59 at 1848cb5 and its validation comment; read
docs/internal/automatic-fetch-review.mdfor queue semantics, benchmark decision and crash-lock limits. Continue from the first outstanding CI/review item, then #60. Do not merge/release or deploy production without approval.uniskela commentedon Oct 20, 2026
Done: PR #59 remediation is pushed at
bc85555; all current GitHub checks, Kody review and Sonar quality gate pass. All three original Kody threads are answered/resolved; business validation found no MUST_FIX findings. Dedicated sync timestamps, durable post-push follow-up and failure isolation are implemented. Verification: 377 tests; browser 33 passed/9 intentional skips; controlled rootless-Docker integration 61 passed, plus build/migrations/smoke checks.Next: review #59. Per-repository policy remains the immediate follow-up #60; #52 stays open for that work. Independent security hardening is #61 (
8266e33), also all-green.Resume: start with
docs/internal/automatic-fetch-review.mdon #59, then #60's acceptance criteria. No merge, release or production deployment was performed.uniskela commentedon Oct 20, 2026
Drift check: PR #62 merged on 2026-10-20 (
da55d99, closing #60) after this issue was last edited, so Focus/Next/Resume now point at verifying the per-repository fetch settings onmainbefore closing #52. Both fetch PRs are in pending release PR #41 (v0.6.0).uniskela commentedon Oct 22, 2026
Verified on
main(8333dd8), release audit #57Acceptance criteria checked against the code and tests on
main:STACK_MANAGER_WORKER_ENABLEDandSTACK_MANAGER_AUTO_FETCH_ENABLED, and waits a full interval after a failure. Duplicate jobs are prevented by the active-job dedupe key, and overlapping scans are coalesced. Unit tests pass, plus a new scanner test (fix: harden v0.6.0 release audit labels, tests and upgrade docs #67) proving nothing is scanned or queued when the worker or server auto-fetch is off.STACK_MANAGER_AUTO_FETCH_ENABLED=falseand passed.refs/remotes/origin/*. Drafts (DB) and unpushed commits (refs/stack-manager/heads/*) survive failed fetches and the v0.5.0 → v0.6.0 upgrade (verified with a database seeded by v0.5.0 code). A new integration test shows one repository's failing fetch does not block another.Evidence:
pnpm check656/656 onmain, 667/667 with #67; full browser/axe 43 passed / 13 intentional skips; reportdocs/internal/releases/v0.6.0-readiness.mdin #67.Not verified here: a live external push picked up by polling on the operator's own instance. That is step 4 of the v0.6.0 acceptance checklist, tracked in #57.
Closing as verified on
main.