chore(wiki): rename wiki pages to UPPERCASE to match .sf/ convention

All .sf/ operational files use UPPERCASE (DECISIONS.md, KNOWLEDGE.md, etc.).
Wiki pages now follow the same convention: INDEX.md, ARCHITECTURE.md,
WORKFLOWS.md, SUBSYSTEMS.md, GLOSSARY.md.

Also updates sf-wiki SKILL.md and system.md prompt references.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

.sf/wiki/GLOSSARY.md

@@ -114,6 +114,6 @@ Project-specific terms only. General software terms not listed.
 
 ## W
 
-**Wiki** (`.sf/wiki/`) — Human-curated + agent-generated reference pages injected into every SF system context turn. Tracked in git (not gitignored). Hand edits persist across commits and clones. Lowercase filenames (`index.md`, `architecture.md`, etc.).
+**Wiki** (`.sf/wiki/`) — Human-curated + agent-generated reference pages injected into every SF system context turn. Tracked in git (not gitignored). Hand edits persist across commits and clones. Uppercase filenames (`INDEX.md`, `ARCHITECTURE.md`, etc.) matching the `.sf/` operational file convention.
 
 **YOLO** — A flag on top of Build mode that disables all safety confirmations (no git prompts, no write-gate approvals). Enabled via `Ctrl+Y` or `/mode yolo`. Not a third mode — it does not appear as a `Shift+Tab` stop.

.sf/wiki/INDEX.md

@@ -1,6 +1,6 @@
 # singularity-forge — Index
 
-*Generated: 2026-05-11 | Commit: see `git rev-parse HEAD` | Commands: see workflows.md*
+*Generated: 2026-05-11 | Commit: see `git rev-parse HEAD` | Commands: see WORKFLOWS.md*
 
 ## What this repo is
 
@@ -36,8 +36,8 @@ npm run copy-resources # rebuild dist/resources/ (extension JS/prompts)
 | Understand SF's architecture decisions | `docs/adr/` |
 | Understand spec-first TDD doctrine | `docs/SPEC_FIRST_TDD.md` |
 | Understand the runtime state model | `.sf/PROJECT.md`, `AGENTS.md` |
-| Find a subsystem | `subsystems.md` |
-| Build/test commands | `workflows.md` |
+| Find a subsystem | `SUBSYSTEMS.md` |
+| Build/test commands | `WORKFLOWS.md` |
 | Understand SF autonomous mode | `src/resources/extensions/sf/` |
 | Understand the Pi SDK packages | `packages/` |
 

src/resources/extensions/sf/prompts/system.md

@@ -78,11 +78,11 @@ Titles live inside file content (headings, frontmatter), not in file or director
   KNOWLEDGE.md          (append-only register of project-specific rules, patterns, and lessons learned)
   CODEBASE.md           (generated fallback codebase map cache — auto-refreshed when tracked files change)
   wiki/                 (generated + hand-curated reference wiki — tracked in git; use sf-wiki skill to generate)
-    index.md            (what this repo is, how to run it, where to start)
-    architecture.md     (major subsystems and data/control flow)
-    workflows.md        (build, test, release, autonomous/SF flows)
-    subsystems.md       (table of subsystem, path, purpose, owner, tests)
-    glossary.md         (project terms only)
+    INDEX.md            (what this repo is, how to run it, where to start)
+    ARCHITECTURE.md     (major subsystems and data/control flow)
+    WORKFLOWS.md        (build, test, release, autonomous/SF flows)
+    SUBSYSTEMS.md       (table of subsystem, path, purpose, owner, tests)
+    GLOSSARY.md         (project terms only)
   OVERRIDES.md          (user-issued overrides that supersede plan content via /steer)
   QUEUE.md              (append-only log of queued milestones via /queue)
   STATE.md
@@ -126,7 +126,7 @@ In all modes, slices commit sequentially on the active branch; there are no per-
 - **DECISIONS.md** is an append-only register of architectural and pattern decisions - read it during planning/research, append to it during execution when a meaningful decision is made
 - **KNOWLEDGE.md** is an append-only register of project-specific rules, patterns, and lessons learned. Read it at the start of every unit. Append to it when you discover a recurring issue, a non-obvious pattern, or a rule that future agents should follow.
 - **CODEBASE.md** is a generated fallback snapshot of the tracked repository. SF may inject it when available, but healthy Sift is the preferred live code index. Use CODEBASE only when Sift is unavailable, cold, degraded, or when you need a durable overview. Use `/codebase update` only when you need to force an immediate refresh.
-- **wiki/** (`.sf/wiki/`) contains generated and hand-curated codebase reference pages — injected automatically when present. Contains `index.md`, `architecture.md`, `workflows.md`, `subsystems.md`, and `glossary.md`. Read it at the start of any planning or research unit for fast repo orientation. Generate or refresh with the `sf-wiki` skill; pages are tracked in git so hand edits persist.
+- **wiki/** (`.sf/wiki/`) contains generated and hand-curated codebase reference pages — injected automatically when present. Contains `INDEX.md`, `ARCHITECTURE.md`, `WORKFLOWS.md`, `SUBSYSTEMS.md`, and `GLOSSARY.md`. Read it at the start of any planning or research unit for fast repo orientation. Generate or refresh with the `sf-wiki` skill; pages are tracked in git so hand edits persist.
 - **CONTEXT.md** files (milestone or slice level) capture the brief — scope, goals, constraints, and key decisions from discussion. When present, they are the authoritative source for what a milestone or slice is trying to achieve. Read them before planning or executing.
 - **Milestones** are major project phases (M001, M002, ...)
 - **Slices** are demoable vertical increments (S01, S02, ...) ordered by risk. After each slice completes, the roadmap is reassessed before the next slice begins.

src/resources/skills/sf-wiki/SKILL.md

@@ -33,11 +33,11 @@ directory is skipped, record the reason in one sentence.
 
 Keep the wiki small by default:
 
-- `index.md`: what this repo is, how to run it, where to start.
-- `architecture.md`: major subsystems and data/control flow.
-- `workflows.md`: build, test, release, autonomous/SF flows.
-- `subsystems.md`: table of subsystem, path, purpose, owner signal, tests.
-- `glossary.md`: project terms only.
+- `INDEX.md`: what this repo is, how to run it, where to start.
+- `ARCHITECTURE.md`: major subsystems and data/control flow.
+- `WORKFLOWS.md`: build, test, release, autonomous/SF flows.
+- `SUBSYSTEMS.md`: table of subsystem, path, purpose, owner signal, tests.
+- `GLOSSARY.md`: project terms only.
 
 Add subsystem pages only when the table would become unreadable.