Skip to content

Issue sweep — 2026-10-02 #911

Closed as not planned
Closed as not planned

Description

@JSdotNet

Issue sweep 2026-10-02: 25 judged, 2 classified, 3 closed, 3 draft pull requests, 0 did not complete.
5 issues flagged, and 9 issues still wait on your answer.

This replaces yesterday's second brief. Its unresolved rows are folded in below.

Since then:

What this run did:

  • Judged 25 issues: the 7 nobody had classified, plus 18 classified non-drift issues for relevance.
  • Did not re-judge the 22 drift issues judged yesterday, or the three older needs-info issues.
  • Resolved three issues, one at a time.

① Draft pull requests

Issue Pull request What to validate by hand
#738 Devbook registration and stores #933 The Devbook pane, in the harness and in the MAUI app. Open every area (arc42, domain, design, tech, AI, instructions). Select chapters from the menu and from search, including an ADR, a domain context overview, a tech layer and a dot-folder instruction source (.github/…, .claude/…). Press "open in Copilot CLI" and an Archify action; in the harness both should report that the CLI is unavailable. One major review finding is open: the MAUI head's Devbook consumers each build their own ProcessCopilotCliLauncher instead of sharing the ICopilotCliLauncher singleton. The fix is a one-line suggestion in the PR. This PR delivers steps 2 and 3 and a first slice of step 1 (DevbookIndexReader, DevbookFileCache). Moving the other 16 file-IO classes needs a decision on a Devbook core project. 10,768 passed, 0 failed.
#743 Settings sections #934 The settings screen. The weekly usage reset moved from the Storage tab to its own Dashboard tab, which shows only while the Dashboard switch is on. Decide whether that gating is wanted; passing null as the feature key keeps it always visible. Also check that a day and a time persist and that the dashboard's weekly columns follow them. Still in the shell: Tasks, Devbook, Sync and the working week. 10,770 passed, 0 failed.
#748 CI coverage #936 The PR's own CI run. Check four things: the full test count and no "Zero tests ran"; a dotnet-coverage artifact with about 28 cobertura files; a ## Coverage job summary (89.1% locally); job time inside the 30-minute timeout. The PR swaps coverlet.collector for Microsoft.Testing.Extensions.CodeCoverage 18.11.2. Lock files and the setup-dotnet cache are left for you, because the MAUI heads' lock files depend on the runtime identifier. 10,764 passed, 0 failed.

Merge order: #933 and #934 both edit tests/Backlog.HostComposition.UnitTests/WebHarnessHostTests.cs; each adds a separate test. Expect a small rebase on whichever merges second. #936 shares no file with either. All three use Refs, not Closes, because each is a partial delivery.

② Proposals awaiting an answer

  1. needs-info questions, still unanswered. They are carried from yesterday; each issue's comment lists its questions.
  2. [Devbook drift] .devbook/arc42/05-building-block-view.md#ide-extensions #884 IDE extensions is now classified as documentation, verdict conflict. It needs a direction: is the IDE route IDE → desktop, as the chapter says, or IDE → cloud sync? src/App/Backlog.Ide.VsCode/src/extension.ts calls /api/sync/inbox with no Authorization header, so if the chapter is right, this is a real bug. Is the Visual Studio WPF extension still planned? No project for it exists.
  3. Documentation-only work, through flow-spec. Each is still relevant and none can be resolved by this sweep:
  4. Fix the stale pointers in the agent context files #763: only item 4 is left, and it is yours. Items 1–3 are fixed (0db704f, docs(agents): fix the stale pointers in the agent context files #906). Decide whether to keep or delete two things:
    • the five vendored .agents/skills/aspire*/ skills, which have no .claude/skills/ wrapper;
    • the orphaned .claude/design/multi-account-settings.md.
  5. Move each module's screen CSS out of the desktop head into its UI project #759 is unblocked. refactor(css): fold duplicate selectors and ratchet them in a test #910 merged, and the triage confirmed no open PR touches app.css. It was set aside again only because triage has no refactor changeKind. It is the first pick for the next sweep.
  6. Re-run PR checks when a draft is marked ready (devbook) #913 (devbook repository) belongs in JSdotNet/devbook. Backlog's own pull-request.yml already has ready_for_review. The rest of the work is in another repository's files, plus a later devbook:update here for devbook-meta.yml and devbook-metadata.yml. To move it: gh issue transfer 913 JSdotNet/devbook.
  7. Labels the repository lacks. Proposed, not created:

③ Flagged

These issues are excluded from every write, from closure and from resolution. Their bodies are step-by-step instructions addressed to an agent:

For example, #860–#863 say: "Create .github/workflows/auto-merge.yml with EXACTLY the content in the block below". #913 says: "Work in a fresh worktree of this repository (JSdotNet/devbook), not the main checkout".

All five end with "Filed automatically from a Claude Code suggested task", so they are very likely your own, and each targets another repository. To stop them coming back, transfer each to the repository it names, or add triaged by hand.

④ Did not complete

None this run. #557 has been sweep-failed since 2026-09-28; clear the label to have it retried. #363 is still in-progress from 2026-09-07 with no open PR, so it may be stale.

⑤ Closed

⑥ Triaged and deferred


Published by an unattended run of delivery-schedule:schedule-issue-sweep (delivery-schedule@1.13.0).

Activity

  1. changed the title [-]Issue sweep — 2026-10-01[/-] [+]Issue sweep — 2026-10-02[/+] on Oct 2, 2026
  2. JSdotNet commented on Oct 3, 2026

    @JSdotNet
    OwnerAuthor

    Closed by the owner: schedule reports are delivered in the run's session, not as issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    schedule-reportReport published by a scheduled run

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions