Audit and upstream policy

Oh My QEMU is a local workflow toolkit, not a QEMU upstream contribution branch. Its skills help collect evidence and keep QEMU-related work reviewable.

Audit boundary

For a non-trivial task that writes to a QEMU workspace, keep task artifacts in:

.oh-my-qemu/<task-slug>/
├── audit.md
├── commands.md
├── logs/
├── scripts/
└── output/

audit.md records scope, cited sources, decisions, assumptions, and verification. commands.md records reproducible commands and their outcomes. Raw logs belong in logs/, temporary helpers in scripts/, and generated deliverables or non-QEMU binaries in output/.

Build boundary

QEMU build output belongs only in a named source-root directory such as builds/build-aarch64/. Third-party artifacts and non-QEMU binaries belong in the task’s output/ directory. Source files change only when they are the requested deliverable.

Git boundary

Before writing audit data or configuring QEMU, ensure the repository-local file returned by git rev-parse --git-path info/exclude contains an effective entry for each of:

.agents/
.oh-my-qemu/
builds/

Preserve existing entries, avoid adding slash-variant duplicates, never stage these directories, and verify they are absent from git status --short at handoff. Stage or commit only when the user explicitly requests that separate Git action.

QEMU upstream boundary

QEMU’s official GitLab and mailing lists are upstream project channels. For patches, follow the recipients and lists selected through MAINTAINERS: sending a patch there is a QEMU upstream contribution. Do not prepare or send agent-generated code or documentation for that mailing-list submission.

Creating a local branch, commit, or patch file, pushing a branch, or opening a pull request is not by itself a QEMU upstream contribution. Perform those Git actions only when requested and follow the workspace’s Git policy. Research, debugging, static analysis, local-only experiments, and verification remain valid.