You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Clean-user-profile validation is queued until several ready checks can be completed together in one intentional Apple Silicon session, without disturbing the primary user's Markover reviews, handlers, preferences, or active development instances.
Session trigger
Schedule a session when at least two queued checks are ready against compatible exact release candidates. A task is ready only when its own prerequisites identify the immutable build, workflow, and behavior to test.
Profile setup checklist
Select the ready issues, exact immutable release or candidate for each, and an execution order that preserves required first-launch evidence.
Create or log in to a dedicated standard macOS user profile; use a newly created profile whenever a task requires genuinely fresh Gatekeeper or first-registration state.
Record sanitized sw_vers and uname -m output, excluding usernames, serial numbers, account details, and unrelated host information.
Confirm the test profile has no ~/Library/Caches/Markover, ~/Library/Application Support/Markover, installed Markover.app, or previously registered Markover URL handler required by the selected checks.
Confirm Node.js 22.13.0 or newer and the network access required by the public launcher, without copying credentials from the primary profile.
Put neutral Markdown and image fixtures in a test-only location that contains no private project or account data.
Run first-download, Gatekeeper, and first-registration observations before any action that grants an override or creates Markover state.
Complete the remaining compatible checks as one user journey. If another check independently requires fresh state, use another new profile rather than describing a reused profile as clean.
Transfer only sanitized evidence and exact digests to the owning GitHub issues.
Verify every owning issue has recorded its result or a linked blocker before removing test-only apps, caches, Application Support data, fixtures, and disposable profiles.
Add an existing issue directly when it already owns the complete clean-profile result.
Create a focused follow-up issue when the parent owns implementation but the clean-profile manual evidence is independently schedulable.
Keep each validation issue in its source launch-gate milestone; this umbrella intentionally has no milestone because it batches work across gates.
Do not move a queue item to In Progress merely because it appears here. Its future execution thread must claim it through the normal work-intent workflow.
Scope boundaries
This issue coordinates sessions and setup only; it does not own product fixes or acceptance evidence.
Do not reset, move, or delete the primary profile's Markover state for these checks.
Outcome
Clean-user-profile validation is queued until several ready checks can be completed together in one intentional Apple Silicon session, without disturbing the primary user's Markover reviews, handlers, preferences, or active development instances.
Session trigger
Schedule a session when at least two queued checks are ready against compatible exact release candidates. A task is ready only when its own prerequisites identify the immutable build, workflow, and behavior to test.
Profile setup checklist
sw_versanduname -moutput, excluding usernames, serial numbers, account details, and unrelated host information.~/Library/Caches/Markover,~/Library/Application Support/Markover, installedMarkover.app, or previously registered Markover URL handler required by the selected checks.Validation queue
Queue maintenance
Scope boundaries