zeekay
1b367e2b62
The tree was a debranded snapshot of upstream taken around 2026-02-20, and upstream has moved about five months since. This replaces it with upstream master, mechanically re-derived: bin/debrand does the rename, and the pipeline and squashed migrations are restored from the shipped tree. Not a merge. The previous import replaced the tree wholesale in a single commit, so there is no shared content history to merge against. Reproducing the rename on the new tree is what actually converges. What survives: .hanzo/workflows, the Dockerfiles and bin/docker* entrypoints, compose files, LLM.md, and insights/migrations. The squashed initial migration is load-bearing — the live database records it by name, so upstream's ~918 individual migrations cannot come back. Nine products are dropped as unreferenced. Twenty-one more that we do not run are kept anyway because the core app still imports them; unpicking those is a refactor and does not belong in a rebase. This base does not build yet, and the reasons are not in the rename: upstream now wants Python 3.13.13 against our 3.12.12 and Django 5.2 against our 4.2, and the dependency manifests still name upstream packages that we republish under our own names. Those are decisions, not renames.
3.3 KiB
Cleanup
Use this reference after the final report is written and any approved PR comment, upload, or push handling is complete.
It also applies to every early exit. If the run aborts at any point after a checkout happened, a browser session opened, or generated local config appeared, still restore the original branch, close the browser session, and remove agent-generated hunks before returning. A skipped cleanup leaves a dirty tree that blocks the next PR-mode run at its clean-tree gate.
Checkout
Before switching branches, remove agent-generated local config hunks (see Generated Local Files below): a modified tracked file carries across git checkout and would silently land on the developer's own branch. Then PR mode always attempts to restore the original branch:
git checkout "$original_branch"
If the run started from a detached HEAD, $original_branch is the SHA recorded at preflight; never run git checkout with an empty argument.
Keep the run directory for debugging, but mind the branch: where .qa-frontend/ is not gitignored (any branch cut before this skill merged), an in-repo run directory dirties the tree and blocks the next PR-mode run's clean-tree gate - move it out of the repo (for example $TMPDIR/qa-frontend-runs/) and tell the user where it went. Confirm git status --porcelain is clean. Unpushed local fix commits never show in status; list them with git log <pr-branch> --not origin/<pr-branch> and mention them in the report if the push was rejected or skipped.
Local mode did not check out a PR branch, so there is nothing to restore. Leave the run directory in place.
Overrides
If the run set a theme override or feature-flag overrides, restore them (theme back to the original theme_mode, overrideFeatureFlags(false)) before closing the browser session, as the matching sections in browser-mcp-patterns.md describe.
Browser Session
After the final report is written, end the browser automation session if the browser MCP/tooling exposes a close-page, close-context, close-browser, or end-session action. This prevents stale Chromium sessions from blocking later QA runs.
Do not close the user's visible browser windows. If a stale headless Chromium process from a previous agent blocks the run and no MCP close action is available, ask the user before killing it, and target only agent-started browser processes. Agent-started browser processes commonly include command-line markers such as ms-playwright, mcp-chrome-, remote-debugging-pipe, or playwright-mcp; visible user browsers usually use the normal browser profile instead. If you inspect processes, use these markers to explain exactly what you plan to terminate before asking for approval.
Stack
If STACK_STARTED_BY_AGENT=1, stop only the stack the agent started during cleanup unless the user explicitly asked to keep it running. Use the matching repo-recommended stop command for the approved startup path. For example, when the approved startup path was bin/insightscli up -d, stop it with:
bin/insightscli down -y
If the user started the stack themselves, do not stop or restart it without explicit approval.
Generated Local Files
If insightscli auto-adds a local phrocs command to insightscli.yaml, remove only that generated hunk during cleanup. Do not commit it as part of a QA run.