Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Present, Draw and Persona successes pin an orange alert in the menu-bar panel

Open
  • Is something wrong?
#333 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
22/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
swift
Domain
desktop

Research direction

The panel's orange row is driven by StageKitController.notices (around :497-501) and StageNotice (:683-686) in StageKitController.swift, rendered in WorkbenchQuickPanel.swift at :142 and :316-325. Success notices are raised at call sites in AppCoordinator.swift, DemoScenes.swift, SceneSharing.swift, Persona.swift and StageKitController.swift:407. Start by adding a tone to StageNotice and checking the NoticeOwnerTests expectations. Done when a nil-completed screenshot leaves no panel notice, errors and copyBoard with no board remain problems, and the mutation check fails when the filter is removed.

Written by the indexing model from the issue text.

Description

bug

Outcome: routine successes stay on their page. The panel's orange recovery row shows only problems, and a stale success can no longer hide a live one.

Evidence (main edc15df)
  • StageKitController.notices merges notices with no tone (:497-501; StageNotice :683-686).
  • The panel turns any stage notice into an orange warning row (WorkbenchQuickPanel.swift:142, :316-325).
  • Successes are posted as notices at:
    • AppCoordinator.swift:406, 428 and 460-461
    • DemoScenes.swift:499, 645, 677 and 972
    • SceneSharing.swift:17 and 37
    • StageKitController.swift:407
    • Persona.swift:707, 752 and 1337
  • A Draw success takes precedence over a later Live Camera failure.
  • This conflicts with docs/workbench.md:119 (Fit 7) and #134 T5.
Change
  • Give StageNotice a tone (problem by default).
  • Add post(_:on:tone:). The screenshot completion splits on error == nil.
  • Scenes and personas get noticeIsDone (reset in didSet) plus confirm(_:), used only for the listed successes.
  • The panel-facing notice takes the first problem. Pages keep every notice.
Acceptance

NoticeOwnerTests:

  • a nil-completed screenshot leaves no panel notice, while the Draw page keeps it;
  • an error is a problem;
  • copyBoard with no board is still a problem;
  • a done notice does not hide a scene problem;
  • saveMyDevice is done.
  • Mutation check: these tests fail when the filter is removed.
Value before scope
  1. Outcome: a presenter sees only real problems. Evidence: the call sites above.
  2. Simpler route: classify where each notice is raised.
  3. Owner: StageKitController notices.
  4. Complexity: one tone field.
  5. Verified by: StageKitLegacy tests.

Grammar: Quality.

Refs #134

Build-ready record from the overnight lead session of 15 Oct 2026, verified against main edc15df by an independent skeptic per item. Implementation follows on a claude/* branch; this issue closes only after native acceptance.

Dominant language
Swift
Stars
0
Forks
1
Avg merge
8h 5m
Merged PRs (30d)
215

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Ship-Work/workbench

All issues in Ship-Work/workbench

Similar issues

More Swift issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.