repo: rename operating contract to REPO.md

Promote REPO.md to the canonical repo contract, update live references away from repo-operating-model.md, and remove the unused rustfmt install from CI.

project: hwping
agent: codex-20260409-repo-contract-rename
role: worker
artifacts: DEC-20260409-001, DEC-20260409-002, LOG-20260409-001

Author: LPFchan

.github/skills/weekly-upstream-intake/SKILL.md

@@ -10,7 +10,7 @@ Use this skill when Hwping needs a repeatable review of upstream `rhwp` work.
 
 ## Canonical Sources
 
-- [repo-operating-model.md](../../../repo-operating-model.md)
+- [REPO.md](../../../REPO.md)
 - [upstream-intake/README.md](../../../upstream-intake/README.md)
 - [upstream-intake/intake-method.md](../../../upstream-intake/intake-method.md)
 - [upstream-intake/weekly-upstream-intake-template.md](../../../upstream-intake/weekly-upstream-intake-template.md)

.github/workflows/ci.yml

@@ -22,7 +22,7 @@ jobs:
       - name: Install Rust toolchain
         uses: dtolnay/rust-toolchain@stable
         with:
-          components: clippy, rustfmt
+          components: clippy
 
       - name: Cache cargo registry & build
         uses: actions/cache@v4

AGENTS.md

@@ -2,12 +2,12 @@
 
 Hwping is a macOS-focused downstream fork of upstream `rhwp`.
 
-Use this file as the repo-root entrypoint for agent behavior. The canonical operating rules still live in `repo-operating-model.md`.
+Use this file as the repo-root entrypoint for agent behavior. The canonical operating rules live in `REPO.md`.
 
 ## Read First
 
 - `README_EN.md` for the repo's scope and product boundary
-- `repo-operating-model.md` for routing, artifact rules, and commit provenance
+- `REPO.md` for routing, artifact rules, and commit provenance
 - `SPEC.md`, `STATUS.md`, `PLANS.md`, and `INBOX.md` for current project truth
 - the local `README.md` or template for any surface you are about to edit
 
@@ -54,7 +54,7 @@ Reference paths:
 
 ## Commit Discipline
 
-- New commits should carry the provenance trailers required by `repo-operating-model.md`.
+- New commits should carry the provenance trailers required by `REPO.md`.
 - Local hook and CI enforcement live in `.githooks/commit-msg` and `.github/workflows/commit-standards.yml`.
 - Do not bypass commit checks with ad hoc formatting or `--no-verify`.
 - Treat bootstrap or migration commits as explicit exceptions only.

CONTRIBUTING.md

@@ -28,7 +28,7 @@ Hwping adopts `LPFchan/repo-template` as its canonical repository operating mode
 - `mydocs/` remains the detailed technical, troubleshooting, and manual layer that supports the root truth docs.
 - Stable IDs and commit provenance trailers are now part of the expected workflow.
 
-For the repository-specific rules, see [repo-operating-model.md](repo-operating-model.md), [DEC-20260409-001-repo-template-full-adoption.md](records/decisions/DEC-20260409-001-repo-template-full-adoption.md), and [DEC-20260409-002-retire-mydocs-hwping-namespace.md](records/decisions/DEC-20260409-002-retire-mydocs-hwping-namespace.md).
+For the repository-specific rules, see [REPO.md](REPO.md), [DEC-20260409-001-repo-template-full-adoption.md](records/decisions/DEC-20260409-001-repo-template-full-adoption.md), and [DEC-20260409-002-retire-mydocs-hwping-namespace.md](records/decisions/DEC-20260409-002-retire-mydocs-hwping-namespace.md).
 
 ## Contribution Rules
 

PLANS.md

@@ -72,7 +72,7 @@ This document contains accepted future direction only.
 
 - Initiative: institutionalize the root truth docs and provenance workflow
   - Why now: the operating model needs to become normal before more migration and product work accumulates
-  - Dependencies: `repo-operating-model.md`, contributor docs, and the seed `DEC-*` and `LOG-*` records
+  - Dependencies: `REPO.md`, contributor docs, and the seed `DEC-*` and `LOG-*` records
   - Related ids: `DEC-20260409-001`, `LOG-20260409-001`
 - Initiative: keep advancing the app-facing facade, FFI, and preview boundaries
   - Why now: Hwping still needs real product surfaces beyond the current smoke path

README_EN.md

@@ -114,7 +114,7 @@ Hwping adopts `LPFchan/repo-template` as its canonical repository operating mode
 - `mydocs/` remains the deeper technical, troubleshooting, and manual layer that supports the root truth docs.
 - New commits are expected to carry repo-template provenance trailers.
 
-For the repository-specific rules, see [repo-operating-model.md](repo-operating-model.md), [DEC-20260409-001-repo-template-full-adoption.md](records/decisions/DEC-20260409-001-repo-template-full-adoption.md), and [DEC-20260409-002-retire-mydocs-hwping-namespace.md](records/decisions/DEC-20260409-002-retire-mydocs-hwping-namespace.md).
+For the repository-specific rules, see [REPO.md](REPO.md), [DEC-20260409-001-repo-template-full-adoption.md](records/decisions/DEC-20260409-001-repo-template-full-adoption.md), and [DEC-20260409-002-retire-mydocs-hwping-namespace.md](records/decisions/DEC-20260409-002-retire-mydocs-hwping-namespace.md).
 
 ## Documentation
 

repo-operating-model.md REPO.mdrepo-operating-model.md renamed to REPO.md

@@ -1,6 +1,6 @@
-# Hwping Repo Operating Model
+# Hwping REPO Contract
 
-This document is the canonical rules layer for Hwping's adoption of `LPFchan/repo-template`.
+This document is the canonical repo contract for Hwping's adoption of `LPFchan/repo-template`.
 
 ## Purpose
 

records/agent-worklogs/LOG-20260409-001-repo-template-migration-bootstrap.md

@@ -28,11 +28,11 @@ Implement the full `LPFchan/repo-template` operating model in the Hwping reposit
 - Checks run: repository tree review and scaffold inspection
 - Output: confirmed that `upstream-intake/` was already present but the root truth docs and provenance folders were still missing
 - Blockers: none
-- Next: add `repo-operating-model.md`, the root truth stack, and the provenance directories
+- Next: add the canonical repo contract (`REPO.md`, originally introduced as `repo-operating-model.md`), the root truth stack, and the provenance directories
 
 ## Entry 2026-04-09 05-29-07 KST
 
-- Action: added `repo-operating-model.md`, `SPEC.md`, `STATUS.md`, `PLANS.md`, `INBOX.md`, `research/`, and `records/`
+- Action: added the canonical repo contract (`REPO.md`, originally introduced as `repo-operating-model.md`), `SPEC.md`, `STATUS.md`, `PLANS.md`, `INBOX.md`, `research/`, and `records/`
 - Files touched: new root operating-model and provenance surfaces
 - Checks run: repository tree verification
 - Output: seeded `DEC-20260409-001` and this worklog so the migration itself is recorded inside the new model

records/decisions/DEC-20260409-002-retire-mydocs-hwping-namespace.md

@@ -71,7 +71,7 @@ It also reduces sync noise by removing a product-specific subtree whose main pur
 
 ## Migration Mapping
 
-- `hwping_repo_template_adoption.md` -> `repo-operating-model.md` and `DEC-20260409-001`
+- `hwping_repo_template_adoption.md` -> `REPO.md` (canonical contract; originally introduced as `repo-operating-model.md`) and `DEC-20260409-001`
 - `hwping_repo_sync_plan.md` -> `DEC-20260409-005`, `SPEC.md`, `PLANS.md`, and contributor guidance
 - `hwping_macos_milestone_plan.md` -> `PLANS.md`
 - `hwping_system_architecture.md` -> `DEC-20260409-003`, `SPEC.md`, and `PLANS.md`

skills/README.md

@@ -12,4 +12,4 @@ What lives here:
   - companion workflow for the canonical upstream-review module
 
 Keep skills procedural.
-Do not duplicate the canonical rules from `repo-operating-model.md` inside them.
+Do not duplicate the canonical rules from `REPO.md` inside them.