Make Omacom's policy and docs authoritative; fix Intel shim build

.github/copilot-instructions.md

@@ -1 +1 @@
-AGENTS.md
+../AGENTS.md

AGENTS.md

@@ -1,13 +1,26 @@
-# SiliconForest Mesa maintenance
+# Omacom Mesa assistant policy
 
-This is iconidentify's personally maintained downstream fork. The owner has
-authorized AI-assisted research, review, source integration and development here.
-The upstream community's contribution policy still applies to submissions there;
-do not open upstream issues, comments or merge requests without explicit owner
-instructions.
+This is the policy for AI coding assistants working in omacom/mesa. This file
+is the only assistant instruction file the tree carries: `CLAUDE.md`,
+`GEMINI.md` and `.github/copilot-instructions.md` are symlinks to it.
+Upstream projects' instruction files are not carried here. To change the
+policy, edit this file in a reviewed pull request.
 
-Preserve contributor identities, original commits, licenses and source provenance.
-Label newly generated commits with `Generated-by: LLM`. Record which exact source
-was built and tested. Host or drm-shim checks do not prove hardware correctness.
-Do not enable an unqualified GPU, weaken firmware/ABI admission, install into a
-host system, or reboot a test machine as a side effect of a source build.
+## Rules
+
+- Only public code goes in. Never copy code from proprietary sources.
+- Preserve contributor identities, original commits, licenses and source
+  provenance. Land imports with merge commits, not squashes or rebases.
+- `integration/aurora` is the Apple Silicon integration branch. `main` and
+  `26.2` mirror stock Mesa; never force-push or rewrite them.
+- Changes land through a reviewed pull request with a green `ci / result`.
+  CPU and drm-shim checks do not prove hardware correctness.
+- Hardware qualification happens on the edge package channel, on the affected
+  machines, before a change is promoted beyond edge. Record the exact source
+  commit that was built and tested.
+- Keep identity, firmware and kernel-ABI admission checks fail-closed. Admit a
+  GPU only for an exact, supported identity and kernel contract, and never
+  weaken admission to make another one start. Hardware qualification of an
+  admitted GPU can still be pending on edge.
+- A source build must not install Mesa, change a boot stack or reboot a
+  machine as a side effect.

MAINTAINING.md

@@ -1,49 +1,36 @@
-# Maintaining SiliconForest Mesa
-
-The default integration is `siliconforest/next`. Keep original contributor
-commits and licensing intact; use merges or `git cherry-pick -x` with a written
-record of any conflict resolution. Label newly generated commits as described
-in `AGENTS.md`.
-
-## Reviewing a source update
-
-1. Check the source repository's visibility before including its refs or code in
-   a publication. For GitHub, use `gh api repos/OWNER/REPO --jq .visibility`.
-   Private-source work stays in local research refs and notes. This public
-   integration contains public-source code only.
-2. Pin the exact source SHA, compare divergence against the current integration,
-   and review dependencies and duplicate implementations. A newer topic name is
-   not proof that it includes another branch's fixes.
+# Maintaining Omacom Mesa
+
+`integration/aurora` is the integration branch. Changes land through a pull
+request with a green `ci / result` and an approval of the latest push, as a
+merge commit. Until an admin adds the branch ruleset, maintainers enforce this
+by hand. Keep original contributor commits and licensing
+intact; when a change needs adapting, use `git cherry-pick -x` and record how
+the conflict was resolved.
+
+## Taking a source update
+
+1. Check that the source repository is public before pulling its refs or code
+   in. This tree contains public code only.
+2. Pin the exact source SHA. Compare it against `integration/aurora` and review
+   dependencies and duplicate implementations. A newer topic branch is not proof
+   that it includes another branch's fixes.
 3. Keep identity, topology, USC, HAL and kernel-ABI admission checks intact.
    Hardware recognition and shader encoding alone do not establish support.
-4. Update `SILICONFOREST-SOURCES.json` and the review ledger. Source tags preserve
-   evidence; their existence does not mean every experiment is approved for the
-   default build.
-
-## Checking the integration
-
-Run the quick checks, build the affected drivers and all registered Asahi test
-dependencies, and run the host suite. For changes around device setup, mappings
-or synchronization, also run the Vulkan drm-shim regression probe with Khronos
-validation enabled. Commands and the exact baseline results are in
-`SILICONFOREST-VALIDATION.md`.
+4. Update `SILICONFOREST-SOURCES.json` and the review ledger when the source
+   inventory changes.
 
-`check.py --check-git` works with local maintainer branches or the corresponding
-`origin/*` refs in a fresh full clone. It verifies exact source tags and the
-limited changes to compatibility profiles. The quick GitHub workflow runs
-without requiring all historical source tags or a complete Mesa build.
+## Checking
 
-## Publishing source
+CI builds both architectures and runs the host suite and drm-shim probes on
+every non-documentation pull request. For changes around device setup,
+mappings or synchronization, also read the drm-shim probe output, not just the
+gate result. Changes to `.github/workflows/` or `.github/mesa-ci/` can change
+what the gate checks, so review them as carefully as driver code.
 
-Push explicit branch/tag refs from the reviewed source manifest. Do not use an
-unrestricted `--mirror`, `--all` or `--tags` push from a research checkout that
-also holds private or unreviewed refs. For a new repository, keep it private until
-its remote ref set and source access checks match the intended public inventory.
-Cancelling a local wrapper process is not proof that its upload children stopped.
+## Shipping
 
-Keep experimental firmware/driver profiles separate. Before publishing installable
-packages, qualify the exact board, firmware, m1n1 handoffs and kernel ABI on
-hardware, run the relevant CTS and compositor/application checks, and record the
-results against a pinned source. Host CPU tests and drm-shim checks do not replace
-that hardware qualification. Source maintenance must not install Mesa or alter a
-working boot stack as a side effect.
+Packages live in omacom/omarchy-pkgs (`pkgbuilds/mesa-aurora`). To ship a
+change, pin the exact merged `integration/aurora` commit there, build the split
+packages and release on edge. Qualification on the affected machines happens on
+edge, before promotion beyond it. CPU tests and drm-shim checks do not replace
+that.