merge: reconcile context rollover with resume policy

Generated-By: looper 0.11.8 (runner=fixer, agent=codex)

Author: Siri-Ray

.claude-plugin/marketplace.json

@@ -5,12 +5,12 @@
     "name": "nexu-io",
     "url": "https://github.com/nexu-io/open-design"
   },
-  "description": "Open Design — local-first design app exposed to coding agents over MCP. Install once with your agent's plugin command and projects/files/skills are reachable through stdio.",
+  "description": "OpenDesign — local-first design app exposed to coding agents over MCP. Install once with your agent's plugin command and projects/files/skills are reachable through stdio.",
   "plugins": [
     {
       "name": "open-design",
       "source": "./plugins/open-design",
-      "description": "Open Design MCP server (stdio). 139 skills + projects/files/preview tools, served by your local `od` daemon. Requires `od` on PATH (brew / npm / DMG)."
+      "description": "OpenDesign MCP server (stdio). 139 skills + projects/files/preview tools, served by your local `od` daemon. Requires `od` on PATH (brew / npm / DMG)."
     }
   ]
 }

.claude/skills/od-contribute/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: od-contribute
-description: One-click contribution flow for Open Design (nexu-io/open-design) — even for non-coders. Pick one of four cards (ship a Skill or Design System you made with OD; translate docs; fix a typo / write a blog; report a bug), the agent validates and opens a PR (or issue) for you. Trigger words contribute to open design, ship my OD skill, ship my OD design system, translate OD docs, report an OD bug, od-contribute.
+description: One-click contribution flow for OpenDesign (nexu-io/open-design) — even for non-coders. Pick one of four cards (ship a Skill or Design System you made with OD; translate docs; fix a typo / write a blog; report a bug), the agent validates and opens a PR (or issue) for you. Trigger words contribute to open design, ship my OD skill, ship my OD design system, translate OD docs, report an OD bug, od-contribute.
 allowed-tools:
   - Bash
   - Read
@@ -12,7 +12,7 @@ allowed-tools:
   - WebFetch
 ---
 
-# od-contribute — first-contribution flow for Open Design
+# od-contribute — first-contribution flow for OpenDesign
 
 Locked to `nexu-io/open-design`. Branches by **contribution type**, not by issue. Replaces the dev-loop with type-specific no-code validators. Designed so a product user with zero coding background can ship a real PR.
 
@@ -317,4 +317,4 @@ Print the PR URL on its own line. Done.
 ## When NOT to use this skill
 
 - The user wants to fix a daemon / web bug or add a feature with code changes → use `auto-github-contributor` instead (it has the TDD loop). This skill deliberately doesn't run lint/typecheck/tests because content paths don't need them.
-- The user wants to *generate* a Skill / Design System from scratch → that's Open Design itself. Run OD first, get an artifact, then come back here to ship it.
+- The user wants to *generate* a Skill / Design System from scratch → that's OpenDesign itself. Run OD first, get an artifact, then come back here to ship it.

.claude/skills/od-contribute/agents/openai.yaml

@@ -3,9 +3,9 @@
 # Not required — Codex loads SKILL.md regardless.
 
 interface:
-  display_name: "Open Design — Contribute"
+  display_name: "OpenDesign — Contribute"
   short_description: "Ship a Skill / Design System / translation / typo fix to nexu-io/open-design without writing code."
-  default_prompt: "I want to contribute to Open Design."
+  default_prompt: "I want to contribute to OpenDesign."
 
 policy:
   # Allow Codex to surface this skill when the user mentions OD contribution

.claude/skills/od-contribute/install.sh

@@ -122,15 +122,15 @@ cyan "How to use it:"
 cat <<'EOF'
 
   In Claude Code:  type  /od-contribute  in any chat.
-  In Codex CLI:    type  @od-contribute  or pick "Open Design — Contribute" from /skills.
+  In Codex CLI:    type  @od-contribute  or pick "OpenDesign — Contribute" from /skills.
   In other agents: ask the agent to follow ~/.claude/skills/od-contribute/SKILL.md
 
 The skill walks you through one of:
 
-  * shipping a Skill or Design System you made with Open Design
+  * shipping a Skill or Design System you made with OpenDesign
   * translating a doc to a new language
   * fixing a typo or writing a use-case blog
   * reporting a clean bug
 
-Need help? Open Design Discord:  https://discord.gg/qhbcCH8Am4
+Need help? OpenDesign Discord:  https://discord.gg/qhbcCH8Am4
 EOF

.claude/skills/od-contribute/scripts/validate-design-system.sh

@@ -1,5 +1,5 @@
 #!/usr/bin/env bash
-# Validate a user-supplied DESIGN.md (Open Design "design system" submission).
+# Validate a user-supplied DESIGN.md (OpenDesign "design system" submission).
 # Usage: validate-design-system.sh <DESIGN.md path> [--reference <existing-DESIGN.md>]
 #
 # Strategy: instead of hardcoding a schema, we read 1-3 existing DESIGN.md files

.claude/skills/od-contribute/templates/ISSUE-BODY-bug.md

@@ -10,7 +10,7 @@
 
 {{EXPECTED}}
 
-### Open Design version
+### OpenDesign version
 
 {{OD_VERSION}}
 

.github/AGENTS.md

@@ -11,8 +11,9 @@ Before changing GitHub automation, read the current versions of:
 - `.github/workflows/autofix.atom.yml`
 - `.github/workflows/report.atom.yml`
 - `.github/scripts/handoff.py`
-- `scripts/scopes.ts`
-- `specs/current/ci.md` when changing scope rules, confidence tiers, or guards
+- `.github/config/runners.json`, `.github/config/scopes.json`, and `.github/config/hash.json`
+- `.github/scripts/runners.py`, `.github/scripts/scopes.py`, and `.github/scripts/hash.py`
+- `specs/current/ci.md` when changing scope rules, confidence tiers, or planner invariants
 - `e2e/tests/packaged-smoke-workflow.test.ts`
 - `scripts/approve-fork-pr-workflows.ts` and `e2e/tests/scripts/approve-fork-pr-workflows.test.ts` when touching fork PR approval behavior
 
@@ -26,7 +27,7 @@ Business layer:
 
 - Business workflows decide what happened and what should be requested next.
 - `ci.yml` is the main low-privilege PR, merge-queue, and manual validation gate (application merge bar only).
-- `ci.yml` should run validation, decide scopes, and produce typed handoff artifacts.
+- `ci.yml` should resolve runners, compose scope and hash decisions in its Linux `plan` job, run validation, and produce typed handoff artifacts.
 - Packaging checks are standalone and outside the merge gate: `nix.yml` (flake check) and `docker-image.yml` (image validate + publish). Do not re-attach them to `Validate workspace`.
 - Business workflows should not perform trusted writes to PR comments or branches when a capability workflow can do it.
 
@@ -51,6 +52,21 @@ Default rule: do not add a new domain-specific follow-on workflow such as `foo.c
 
 New workflow-owned helpers should usually live under `.github/scripts/`. Prefer TypeScript for project-owned scripts in general, but Python is acceptable for small GitHub runner glue when stdlib portability and low setup cost matter. Keep such exceptions narrow and covered by `pnpm guard` policy.
 
+The CI control plane is deliberately Linux-only and stdlib-only. Runner classes,
+scope rules, and hash declarations live in `.github/config/`; their Python
+entrypoints initialize metadata before workload runners start. A Windows job
+must never invoke these scripts. Keep the four layers independent: runner
+placement, changed-file scopes, input hashes, and fine-grained commands inside
+a workload.
+
+`hash.py` is a static comparison register, not a success cache. It reads the
+previous identity-to-hash map restored by Actions cache, computes the current
+map from Git inputs, and replaces the local state immediately. The plan carries
+that pending map to `validate`, which publishes it only after the gate succeeds;
+a failed run therefore cannot authorize identical-input skips on a fresh retry.
+Only a workload's YAML `if` gives the comparison skip semantics; cache loss or
+corruption starts cold.
+
 ## Handoff contract
 
 Use `.github/scripts/handoff.py` for all CI follow-on artifact names and paths. The canonical layout is:
@@ -125,13 +141,14 @@ Keep `.github/workflows/ci.yml` as the only approved workflow path unless a main
    - Same-repo patch: produce `handoff/autofix` and let `autofix.atom.yml` consume it.
    - Rich/generated comment: produce `handoff/report` and let `report.atom.yml` materialize and upsert it.
    - New naming, paths, or metadata: update `.github/scripts/handoff.py`.
-2. Update scope routing in `scripts/scopes.ts` when a workflow/script should trigger a validation lane.
-3. Update topology coverage in `e2e/tests/packaged-smoke-workflow.test.ts` or the relevant script test.
-4. Run the focused checks:
+2. Update scope routing in `.github/config/scopes.json`, then run `python3 .github/scripts/scopes.py validate`.
+3. Declare workload input closure in `.github/config/hash.json`; use `"*"` until a narrower set has high-confidence evidence.
+4. Update topology coverage in `e2e/tests/packaged-smoke-workflow.test.ts` or the relevant script test.
+5. Run the focused checks:
    - `python3 .github/scripts/handoff.py self-check`
    - `actionlint -color`
    - `pnpm --filter @open-design/e2e test tests/packaged-smoke-workflow.test.ts`
-5. Run repo-level checks before handing off:
+6. Run repo-level checks before handing off:
    - `pnpm guard`
    - `pnpm typecheck`
 

.github/ISSUE_TEMPLATE/bug-report.yml

@@ -1,5 +1,5 @@
 name: 🐛 Bug report
-description: Something isn't working as expected in Open Design.
+description: Something isn't working as expected in OpenDesign.
 title: "[Bug]: "
 labels: ["bug"]
 body:
@@ -37,7 +37,7 @@ body:
       label: Steps to reproduce
       description: Minimal steps that reliably reproduce the problem.
       placeholder: |
-        1. Open Open Design
+        1. Open OpenDesign
         2. Click ...
         3. See error
     validations:
@@ -54,7 +54,7 @@ body:
   - type: input
     id: version
     attributes:
-      label: Open Design version
+      label: OpenDesign version
       description: Find this in the app's About menu, or run `od --version`.
       placeholder: e.g. 0.8.0 or 0.8.0-preview.2
     validations:

.github/ISSUE_TEMPLATE/config.yml

@@ -8,7 +8,7 @@ contact_links:
     about: Have a half-formed idea you want to chew on before opening a formal feature request? Start a thread in Ideas.
   - name: 🙌 Show what you've made
     url: https://github.com/nexu-io/open-design/discussions/categories/show-and-tell
-    about: Built something cool with Open Design? Share it in Show and tell.
+    about: Built something cool with OpenDesign? Share it in Show and tell.
   - name: 🗣 General discussion
     url: https://github.com/nexu-io/open-design/discussions/categories/general
     about: Anything else — chat, suggestions, community talk.

.github/ISSUE_TEMPLATE/feature-request.yml

@@ -1,5 +1,5 @@
 name: 💡 Feature request
-description: Suggest a new feature or improvement for Open Design.
+description: Suggest a new feature or improvement for OpenDesign.
 labels: ["enhancement"]
 body:
   - type: markdown