Skip to content

Screenshots: Canceling a membership (6 placeholders, customer-side) #92

Closed

Description

@superdav42

For #64.

Problem

docs/user-guide/client-management/canceling-a-membership.md references 6 distinct concepts but every image points to /img/admin/memberships-list.png. The doc covers customer self-service cancellation via the account page's Danger Zone, the deletion confirmation modal, the logged-out state, and what the customer record looks like in Network Admin afterwards.

docs/user-guide/client-management/canceling-a-membership.md
  L16 ![Account page Danger Zone with Delete Account button](/img/admin/memberships-list.png)
  L20 ![Confirm Account Deletion dialog](/img/admin/memberships-list.png)
  L24 ![Logged out after account deletion](/img/admin/memberships-list.png)
  L26 ![Membership canceled confirmation](/img/admin/memberships-list.png)
  L30 ![Customer still exists in the network after cancellation](/img/admin/memberships-list.png) | ![Customer with no active memberships](/img/admin/memberships-list.png)

L30 packs two images on one line — split during the edit pass.

Captures required

Setup: a real test customer with an active membership. Capture the customer-side flow from a customer subsite session; capture the post-cancellation state from Network Admin.

# Doc line Capture target New filename
1 L16 Customer account page Danger Zone with Delete Account button visible static/img/account-page/danger-zone.png (share with #68 if not already filed)
2 L20 Confirm Account Deletion modal with the irreversible warning static/img/account-page/delete-account-confirm.png
3 L24 Logged-out state after account deletion (login screen / "you have been logged out") static/img/account-page/logged-out-after-delete.png
4 L26 "Membership canceled" confirmation toast / banner — capture whichever surface UM uses now static/img/account-page/membership-canceled.png
5 L30a Network Admin → Customers showing the customer record still present after cancellation static/img/admin/customer-after-cancel.png
6 L30b Network Admin → Memberships filtered to show the customer with no active memberships static/img/admin/memberships-customer-empty.png

Capture at 1280×800, crop to the relevant card. Customer-side captures from a non-admin browser. < 200 KB.

Doc edit

Update every line in docs/user-guide/client-management/canceling-a-membership.md to its new path, split L30 into two separate ![...](...) lines, and refine alt text.

Done when

  • All 6 new PNGs added.
  • docs/user-guide/client-management/canceling-a-membership.md updated, L30 split.
  • Customer-side vs admin-side captures clearly distinguishable.
  • PR opened with Resolves for this issue and Ref #64.

Activity

  1. superdav42 commented on May 20, 2026

    @superdav42
    ContributorAuthor

    DISPATCH_CLAIM nonce=a01b36888b36f50be3da8e3d36ad9528 runner=superdav42 ts=2026-05-20T05:16:52Z max_age_s=1800 version=3.17.1 opencode_version=1.15.5

  2. self-assigned this
    on May 20, 2026
  3. superdav42 commented on May 20, 2026

    @superdav42
    ContributorAuthor

    Dispatching worker (deterministic).

  4. superdav42 commented on May 20, 2026

    @superdav42
    ContributorAuthor

    CLAIM_RELEASED reason=worker_failed runner=dave ts=2026-05-20T05:18:07Z aidevops_version=3.17.1 opencode_version=1.15.5

  5. added and removed
    status:queuedWorker dispatched, not yet started
    on May 20, 2026
  6. removed their assignment
    on May 20, 2026
  7. superdav42 commented on May 20, 2026

    @superdav42
    ContributorAuthor

    Worker failed: orphan worktree detected (crash_type=no_work, 0 commits). Cleared for re-dispatch.


    aidevops.sh v3.17.1 automated scan.

  8. superdav42 commented on May 20, 2026

    @superdav42
    ContributorAuthor

    DISPATCH_CLAIM nonce=af9e4f69e10dc62d96303a4b6ab7c84c runner=superdav42 ts=2026-05-20T09:05:35Z max_age_s=1800 version=3.17.1 opencode_version=1.15.5

  9. added
    status:queuedWorker dispatched, not yet started
    and removed on May 20, 2026
  10. self-assigned this
    on May 20, 2026
  11. 12 remaining items

  12. superdav42 commented on May 20, 2026

    @superdav42
    ContributorAuthor

    CLAIM_RELEASED reason=worker_noop runner=dave ts=2026-05-20T09:17:00Z aidevops_version=3.17.1 opencode_version=1.15.5

  13. superdav42 commented on May 20, 2026

    @superdav42
    ContributorAuthor

    Tier Escalation Skipped: Infrastructure Failure (no_work)

    Trigger: 1 worker failure(s) classified as no_work — the worker exited during setup without reading any target files.
    Action: Tier escalation skipped. The issue stays at its current tier so the next retry can succeed cheaply once the infrastructure issue resolves.
    Reason: worker_noop_zero_output

    Why no cascade: no_work means the worker never produced reliable implementation evidence — it crashed during runtime setup (FD exhaustion, plugin init failure, branch naming race, auth refresh race) or stale-recovery falsely concluded no progress. A more expensive model cannot fix an infrastructure problem it never reached. Cascading to tier:thinking would burn opus tokens on a problem sonnet (or haiku) will handle once the infra clears.

    After 3 consecutive no_work failures the per-issue no_work circuit breaker (t2769) applies needs-maintainer-review with a cost-circuit-breaker:no_work_loop marker that _nmr_application_is_circuit_breaker_trip (t2386) recognises, so auto-approval correctly preserves NMR.

    Automated by escalate_issue_tier() no_work skip (t2387) in worker-lifecycle-common.sh


    aidevops.sh v3.17.1 plugin for Claude Code v2.1.144

  14. superdav42 commented on May 20, 2026

    @superdav42
    ContributorAuthor

    Stale recovery tick 1/2 (t2008)


    aidevops.sh v3.17.2 automated scan.

  15. removed their assignment
    on May 20, 2026
  16. superdav42 commented on May 20, 2026

    @superdav42
    ContributorAuthor

    Stale assignment recovered (GH#15060)

    Previously assigned to: superdav42
    Reason: dispatch claim 1541s old, last activity 1169s old (threshold=600s, interactive=false)
    Threshold: 600s

    The assigned runner had no active worker process and produced no progress within the threshold. Unassigned and relabeled status:available for re-dispatch.

    This recovery prevents the orphaned-assignment deadlock where offline runners permanently block all dispatch.


    aidevops.sh v3.17.2 automated scan.

  17. superdav42 commented on May 20, 2026

    @superdav42
    ContributorAuthor

    DISPATCH_CLAIM nonce=2e755bcdd21dd8b416d8a9485b13c2f6 runner=superdav42 ts=2026-05-20T09:37:16Z max_age_s=1800 version=3.17.2 opencode_version=1.15.5

  18. added
    status:queuedWorker dispatched, not yet started
    and removed on May 20, 2026
  19. self-assigned this
    on May 20, 2026
  20. superdav42 commented on May 20, 2026

    @superdav42
    ContributorAuthor

    Dispatching worker (deterministic).

  21. added a commit that references this issue on May 20, 2026
    2f4f240
  22. unlocked this conversation on May 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

documentationImprovements or additions to documentationhelp wantedExtra attention is neededstatus:queuedWorker dispatched, not yet started

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions