orlix-upstream-conformance

Use when building, running, triaging, or claiming success for upstream Linux, upstream mlibc, Coreutils, or other upstream project test suites in Orlix. Requires pristine upstream sources and upstream tests; failures must be routed to the owning Orlix layer instead of editing generated upstream trees or adapted tests.

Zur Installation springen

Repository: rudironsoni/Orlix
Letzte Quellaktivität: 15. Juli 2026 um 12:26
Erkannte Sprache von SKILL.md: Englisch
Sterne: 0
Forks: 0

Installationsoptionen

Standardmäßig ist der Prompt ausgewählt, der zuerst die Quelle prüft. Sie können zu einem direkten Befehl wechseln oder eine lokale Kopie herunterladen.

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

Ein direkter Befehl überspringt den Prüf-Prompt. Prüfen Sie die Quelle, bevor Sie ihn ausführen.

npx skills add https://github.com/rudironsoni/Orlix --skill orlix-upstream-conformance

Der Befehl bleibt in einer Zeile. Scrollen Sie horizontal, um ihn vor dem Kopieren vollständig zu prüfen.

Sie bevorzugen eine lokale Kopie? Laden Sie die Dateien herunter, die SkillsMP derzeit vorliegen.

Quelldateien prüfen

Lesen Sie SKILL.md und alle von SkillsMP angezeigten Begleitdateien, bevor Sie sich für eine Installation entscheiden.

SKILL.md

Quellanweisungen · Schreibgeschützte Vorschau

Zurück zur Suche Zurück zur Installation

Orlix Upstream Conformance

Upstream conformance work proves that Orlix matches upstream-owned behavior. The upstream source and upstream tests are authoritative.

Rules

Use pristine upstream sources and tests.

Do not edit, filter, adapt, or reinterpret upstream tests as success.

Do not modify upstream tests through durable patch stacks used by conformance schemes. Extra regressions belong in Orlix-owned tests, not in patched upstream test trees.

Do not patch generated upstream trees such as Build/OrlixMLibC, Build/OrlixOS, or Build/OrlixKernel/src/linux-*-port. Read them freely for diagnosis; route durable changes to owning Orlix inputs.

Compare failures against upstream Linux, upstream mlibc, or the relevant package behavior before changing Orlix.

Treat every durable upstream patch and package feature override as suspect until root cause is proven. Before adding or changing one, prove the lower owning layers are correct: Linux/kernel syscall and filesystem behavior, OrlixOS rootfs/package inputs, and reviewed package toolchain configuration.

Route fixes by ownership: kernel semantics to OrlixKernel, libc behavior to OrlixMLibC/Sources, upstream package/rootfs assembly and delivered OS payload/session wiring to OrlixOS, and private iOS mechanics to OrlixHostAdapter.

Test runners may consume the OrlixOS session surface to collect upstream output, but they must not patch, filter, skip, or reinterpret upstream tests.

Do not disable upstream package features, suppress upstream tests, or force configure/libtool with ad hoc LD overrides to pass cross builds; fix reviewed OrlixOS package-toolchain inputs and prove the unchanged upstream behavior.

Evidence

Record exact commands, upstream versions and commits, logs, failures, skips, crash checks, final markers, and the patch or override root-cause chain in the workflow's structured report under Build/AgentHarness/.

For Coreutils full-suite claims, success requires the upstream suite marker with zero failures and zero skips for the expected test count. Partial or targeted runs are not full proof.