chore: update repo references after migration to traverse-framework

.agents/skills/traverse-ops/SKILL.md

@@ -37,7 +37,7 @@ Use a lean-by-default operating style so long-running Traverse ops sessions do
 not waste context on raw logs.
 
 - Prefer targeted GitHub queries over full board dumps. For Ready work, use
-  `gh project item-list 1 --owner enricopiovesan --format json --limit 300 --jq '...'`
+  `gh project item-list 1 --owner traverse-framework --format json --limit 300 --jq '...'`
   and return only issue number, title, labels, and item id.
 - Do not paste full `gh project item-list`, `gh pr checks --watch`, test, clippy,
   coverage, or CI logs into the conversation. Summarize pass/fail counts and

AGENTS.md

@@ -68,7 +68,7 @@ security, traceability, accessibility, or required tests.
 ### 1. Check for Claude Code claim
 
 ```bash
-gh issue view <NUMBER> --repo enricopiovesan/Traverse --json labels
+gh issue view <NUMBER> --repo traverse-framework/Traverse --json labels
 ```
 
 If the labels include `agent:claude` → **STOP**. Report:
@@ -87,10 +87,10 @@ If a `claude/issue-<NUMBER>-*` branch exists → **STOP**. Report:
 
 ```bash
 # Add label
-gh issue edit <NUMBER> --repo enricopiovesan/Traverse --add-label "agent:codex"
+gh issue edit <NUMBER> --repo traverse-framework/Traverse --add-label "agent:codex"
 
 # Get project item ID with bounded output
-gh project item-list 1 --owner enricopiovesan --format json --limit 300 \
+gh project item-list 1 --owner traverse-framework --format json --limit 300 \
   --jq '.items[] | select(.content.number == <NUMBER>) | .id'
 
 # Set Agent → Codex

CONTRIBUTING.md

@@ -26,7 +26,7 @@ Please read:
 1. Start from the governing approved spec.
 2. Confirm whether an issue already exists.
 3. Open or link the work item in the project board:
-   [GitHub Project 1](https://github.com/users/enricopiovesan/projects/1/)
+   [GitHub Project](https://github.com/orgs/traverse-framework/projects)
 4. If needed, add or update an ADR before implementation.
 5. Implement with tests and validation evidence.
 6. Make sure the change passes the required validation flow.

README.md

@@ -1,4 +1,4 @@
-[![Traverse](https://github.com/user-attachments/assets/aeafaaf8-650d-4489-bf5e-bd386f0bcaf0)](https://enricopiovesan.com/)
+[![Traverse](https://github.com/user-attachments/assets/aeafaaf8-650d-4489-bf5e-bd386f0bcaf0)](https://traverse-framework.com)
 
 
 # Traverse

SUPPORT.md

@@ -13,7 +13,7 @@ Questions, bug reports, and contribution discussions should generally go through
 - Use GitHub issues for bugs, features, and task discussion
 - Use pull requests for implementation review
 - Use the project board for task tracking:
-  [GitHub Project 1](https://github.com/users/enricopiovesan/projects/1/)
+  [GitHub Project](https://github.com/orgs/traverse-framework/projects)
 
 ## Security Issues
 

docs/multi-thread-workflow.md

@@ -82,10 +82,10 @@ For parallel work to be valid:
 
 For the current expedition artifact work, the cleanest split is:
 
-- Workstream 1: [#42](https://github.com/enricopiovesan/Traverse/issues/42) event contracts
-- Workstream 2: [#44](https://github.com/enricopiovesan/Traverse/issues/44) atomic capability contracts
-- Workstream 3: [#43](https://github.com/enricopiovesan/Traverse/issues/43) composed capability contract
-- Workstream 4: [#45](https://github.com/enricopiovesan/Traverse/issues/45) workflow artifact
+- Workstream 1: [#42](https://github.com/traverse-framework/Traverse/issues/42) event contracts
+- Workstream 2: [#44](https://github.com/traverse-framework/Traverse/issues/44) atomic capability contracts
+- Workstream 3: [#43](https://github.com/traverse-framework/Traverse/issues/43) composed capability contract
+- Workstream 4: [#45](https://github.com/traverse-framework/Traverse/issues/45) workflow artifact
 
 If we only have one active dev thread, these should remain `Ready`.
 
@@ -129,13 +129,13 @@ Use this dev thread prompt:
 Act as a Traverse dev thread for issue #NN.
 
 Pre-flight (run before any work):
-1. gh issue view NN --repo enricopiovesan/Traverse --json labels
+1. gh issue view NN --repo traverse-framework/Traverse --json labels
    If labels include "agent:claude" → STOP. Report: "Issue #NN is claimed by Claude Code."
 2. git ls-remote --heads origin | grep "issue-NN-"
    If a claude/issue-NN-* branch exists → STOP. Report: "A Claude Code branch exists for #NN."
 
 Claim (only if pre-flight passes):
-1. gh issue edit NN --repo enricopiovesan/Traverse --add-label "agent:codex"
+1. gh issue edit NN --repo traverse-framework/Traverse --add-label "agent:codex"
 2. Set Agent → Codex and Status → In Progress on Project 1 for this issue.
    Project ID: PVT_kwHOAEZXvs4BS6Ns
    Agent field: PVTSSF_lAHOAEZXvs4BS6NszhBK-Qk, Codex option: 34d6db7d

docs/tutorial-index.md

@@ -10,6 +10,7 @@ Pick the path that matches your goal before reading further:
 |---|---|
 | Register and invoke a capability end to end | [docs/getting-started.md](getting-started.md) |
 | Consume Traverse from a browser app | [quickstart.md](../quickstart.md) |
+| Plan Traverse reference apps across web, cloud, mobile, and desktop | [docs/reference-app-roadmap.md](reference-app-roadmap.md) |
 | Follow the full ordered onboarding sequence | Continue below |
 
 All three paths are documented in this repo. The descriptions above tell you which one to open first; the ordered sequence below links them all together when you are ready for more.
@@ -41,7 +42,8 @@ Use it in sequence unless you already know the slice you need:
 21. [docs/multi-thread-workflow.md](multi-thread-workflow.md)
 22. [docs/project-management.md](project-management.md)
 23. [docs/troubleshooting.md](troubleshooting.md)
-24. [docs/adr/README.md](adr/README.md)
+24. [docs/reference-app-roadmap.md](reference-app-roadmap.md)
+25. [docs/adr/README.md](adr/README.md)
 
 ## How To Read It
 

scripts/ci/project_state_audit.sh

@@ -2,9 +2,9 @@
 
 set -euo pipefail
 
-repo="enricopiovesan/Traverse"
+repo="traverse-framework/Traverse"
 
-project_items_json=$(gh project item-list 1 --owner enricopiovesan --limit 500 --format json)
+project_items_json=$(gh project item-list 1 --owner traverse-framework --limit 500 --format json)
 
 failures=0
 

specs/188-codex-agent-coordination/plan.md

@@ -53,15 +53,15 @@ Two steps prepended to the existing prompt:
 **Pre-flight (runs before any work):**
 ```
 Before starting any work on issue #<NUMBER>:
-1. gh issue view <NUMBER> --repo enricopiovesan/Traverse --json labels
+1. gh issue view <NUMBER> --repo traverse-framework/Traverse --json labels
    If labels include "agent:claude" → STOP. Report: "Issue #<NUMBER> is claimed by Claude Code."
 2. git ls-remote --heads origin | grep "issue-<NUMBER>-"
    If a claude/issue-<NUMBER>-* branch exists → STOP. Report: "A Claude Code branch exists for #<NUMBER>."
 ```
 
 **Claim step (runs only if pre-flight passes):**
 ```
-1. gh issue edit <NUMBER> --repo enricopiovesan/Traverse --add-label "agent:codex"
+1. gh issue edit <NUMBER> --repo traverse-framework/Traverse --add-label "agent:codex"
 2. Retrieve project item ID for issue #<NUMBER> from Project 1, then:
    gh project item-edit --project-id PVT_kwHOAEZXvs4BS6Ns --id <ITEM_ID> \
      --field-id PVTSSF_lAHOAEZXvs4BS6NszhBK-Qk --single-select-option-id 34d6db7d

specs/governance/approved-specs.json

@@ -8,7 +8,6 @@
       "immutable": true,
       "path": "specs/001-foundation-v0-1/spec.md",
       "governs": [
-        "README.md",
         ".specify/memory/constitution.md",
         "docs/quality-standards.md",
         "docs/compatibility-policy.md",