Skip to content

Screenshots: Upgrading a plan (8 placeholders, customer + admin) #91

Closed

Description

@superdav42

For #64.

Problem

docs/user-guide/client-management/upgrading-a-plan.md references 8 distinct concepts across two recycled images. Lines 16–36 use memberships-list.png for five different customer-facing subsite views (account page, Your Membership card, upgrade checkout, upgrade summary, no-change message). Lines 50–56 use product-upgrades.png for three admin product-config screens.

docs/user-guide/client-management/upgrading-a-plan.md
  L16 ![Customer dashboard with Account page link](/img/admin/memberships-list.png)
  L20 ![Your Membership section with Change button](/img/admin/memberships-list.png)
  L26 ![Checkout form showing available plans and packages](/img/admin/memberships-list.png)
  L32 ![Upgrade payment summary with credit and next billing amount](/img/admin/memberships-list.png)
  L36 ![Message when selected plan does not change the subscription](/img/admin/memberships-list.png)
  L50 ![Up and Downgrades tab with Plan Group field](/img/config/product-upgrades.png)
  L54 ![Free Plan with High End plan group assigned](/img/config/product-upgrades.png)
  L56 ![Premium Plan with High End plan group assigned](/img/config/product-upgrades.png)

The customer-side captures (L16–L36) must come from a logged-in customer subsite, not Network Admin.

Captures required

Setup: at least two plans configured in the same plan group (e.g. "Standard" and "Premium"). A customer subscribed to the lower plan with one active membership. Log in as that customer to the subsite to capture L16–L36.

# Doc line Capture target New filename
1 L16 Customer subsite dashboard with Account menu link visible static/img/account-page/account-menu.png (share with #68 if not already filed)
2 L20 Account page Your Membership card with Change button static/img/account-page/membership-change-button.png
3 L26 Upgrade picker showing available plans / packages on the customer side static/img/account-page/upgrade-picker.png
4 L32 Upgrade payment summary — credit applied + next billing amount static/img/account-page/upgrade-summary.png
5 L36 "Plan does not change the subscription" notice when the same plan is selected static/img/account-page/upgrade-no-change.png
6 L50 Product edit → Up and Downgrades tab with Plan Group field static/img/config/product-upgrades-plan-group.png
7 L54 Free Plan product page with High End plan group assigned static/img/config/product-upgrades-free.png
8 L56 Premium Plan product page with High End plan group assigned static/img/config/product-upgrades-premium.png

If static/img/account-page/account-menu.png is created here, share the same file with the canceling-a-membership / downgrading-a-plan / client-websites gap issues.

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/upgrading-a-plan.md to its new path and refine alt text.

Done when

  • All 8 new PNGs added.
  • docs/user-guide/client-management/upgrading-a-plan.md updated.
  • Customer-side captures clearly from the subsite, not Network Admin.
  • PR opened with Resolves for this issue and Ref #64.

Activity

  1. superdav42 commented on May 20, 2026

    @superdav42
    ContributorAuthor

    DISPATCH_CLAIM nonce=9157c6ee8e22b1c1dfea1ceda223f475 runner=superdav42 ts=2026-05-20T05:16:44Z 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

    Worker Status: BLOCKED

    This task requires 8 new screenshot files to be captured from a live Ultimate Multisite customer interface. As a headless worker without browser automation or screenshot capture capabilities, I cannot autonomously:

    1. Access a running Ultimate Multisite instance
    2. Log in as a customer with an active subscription
    3. Navigate through the upgrade flow
    4. Capture screenshots at 1280×800 resolution
    5. Crop and optimize images to <200KB

    What was searched:

    • Issue comments: no screenshots provided
    • Repository static/img/: only product-upgrades.png exists (admin-side)
    • Git history: recent screenshot work follows the pattern of adding pre-captured images

    Next steps:

    1. Manual capture: Follow the specifications in the issue to capture the 8 required screenshots and place them in static/img/ with the specified filenames
    2. Re-dispatch: After screenshots are added, re-dispatch this issue for markdown updates
    3. Alternative: If a test instance is available, use agent-browser skill to automate screenshot capture

    The issue explicitly requires: "Customer-side captures from a non-admin browser" and "Log in as that customer to the subsite to capture L16–L36."

  5. superdav42 commented on May 20, 2026

    @superdav42
    ContributorAuthor

    CLAIM_RELEASED reason=worker_noop runner=dave ts=2026-05-20T05:36:30Z aidevops_version=3.17.1 opencode_version=1.15.5

  6. added and removed
    status:queuedWorker dispatched, not yet started
    on May 20, 2026
  7. 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

  8. superdav42 commented on May 20, 2026

    @superdav42
    ContributorAuthor

    DISPATCH_CLAIM nonce=e1c4a14ce94cf1a5777a4168b1ad4f1e runner=superdav42 ts=2026-05-20T05:47:41Z 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. locked as resolved and limited conversation to collaborators on May 20, 2026
  11. 32 remaining items

  12. added and removed
    status:queuedWorker dispatched, not yet started
    on May 20, 2026
  13. unlocked this conversation on May 20, 2026
  14. superdav42 commented on May 20, 2026

    @superdav42
    ContributorAuthor

    Cascade Tier Escalation: tier:standard → tier:thinking

    Trigger: 2 consecutive worker failures at tier:standard (threshold: 2)
    Action: Added tier:thinking label — next dispatch will use thinking-tier model.
    Reason: local_error

    Previous attempts at tier:standard failed to produce a PR. Escalating to a more capable model with accumulated context from prior attempts.

    The next worker should review prior attempt comments on this issue for context on what was tried and where it got stuck.

    Automated by escalate_issue_tier() cascade dispatch in worker-lifecycle-common.sh


    aidevops.sh v3.17.2 automated scan.

  15. superdav42 commented on May 20, 2026

    @superdav42
    ContributorAuthor

    DISPATCH_CLAIM nonce=1381a67549fb4ced0f26dbf38d25e6ba runner=superdav42 ts=2026-05-20T09:57:32Z max_age_s=1800 version=3.17.2 opencode_version=1.15.5

  16. added
    status:queuedWorker dispatched, not yet started
    and removed on May 20, 2026
  17. locked as resolved and limited conversation to collaborators on May 20, 2026
  18. superdav42 commented on May 20, 2026

    @superdav42
    ContributorAuthor

    Dispatching worker (deterministic).

  19. added
    status:in-reviewNon-draft PR ready for review/merge
    and removed
    status:queuedWorker dispatched, not yet started
    on May 20, 2026
  20. unlocked this conversation on May 20, 2026
  21. superdav42 commented on May 20, 2026

    @superdav42
    ContributorAuthor

    CLAIM_RELEASED reason=worker_complete runner=dave ts=2026-05-20T10:04:01Z aidevops_version=3.17.2 opencode_version=1.15.5

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:in-reviewNon-draft PR ready for review/mergetier:thinkingRoute to opus-tier model for dispatch

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions