chore(C-373 PR-2): repo hygiene — remove workshop artifacts, normalize identity

[kaizencycle]

C-373 PR-2: Repo Hygiene

Handoff: ATLAS HANDOFF C-373 (ledger_id: mobius:epicon:mvp-extraction-c373)

---

Witness verification (pre-merge ground truth, 2026-07-15)

Claim	Verified state
"README v2 on main"	✅ TRUE — origin/main at 67bbcd6 has truth-only README (raw.githubusercontent.com confirms)
"PR #19 open/unmerged"	❌ STALE — #19 merged d53ad24; #20 merged 67bbcd6
"PR #5 status"	✅ MERGED (fix-v1-install-ref)
"v1 tag exists"	✅ TRUE — git ls-remote --tags origin v1 → c0e5e10
"v1 points at current Action"	⚠️ DRIFT — v1 is 15+ commits behind main; @v1 installs pre-guard-core refactor (PR-4 scope)
"No releases"	❌ STALE — GitHub Release v1.1 exists
"Validator not on main"	❌ STALE — src/validate.mjs, packages/guard-core/ present
"8 commits on main"	❌ STALE — 48 commits
"HTML 84% = no JS"	⚠️ MISLEADING — website/ dominates language stats; JS validator exists
Workshop files on main	✅ TRUE (this PR removes them)

Diagnosis: The scrutiny fetch was a timing snapshot before #19/#20 landed. The deeper lesson stands: agent completion reports described state that lagged public main by ~1 hour. Witness checks must hit origin/main SHA, not agent memory.

---

This PR

• Remove ATLAS_MISSION_COMPLETE.md, REPOSITORY_SUMMARY.md
• Rewrite CONTRIBUTING.md (truth-only, Action test commands)
• package.json: Mobius Substrate identity, GitHub homepage
• ci.yml: Mobius-Substrate canon link (no epicon.dev)

Not in scope (follow-up PRs): QUICK_START.md, SETUP.md, docs/PRODUCT_SPEC.md vapor; v1 tag retag (PR-4); demo repo (PR-5)

---

Tests

• node test/classify.test.mjs — 11/11
• node test/policy-ref.test.mjs — 9/9

---

Intent Publication

epicon_id: EPICON_C-373_CORE_repo-hygiene_v1
ledger_id: mobius:epicon:mvp-extraction-c373
scope: core
mode: normal
issued_at: 2026-07-15T00:00:00Z
expires_at: 2026-08-15T00:00:00Z
justification:
  VALUES INVOKED: integrity, transparency, accountability
  REASONING: Public repo storefront must pass its own integrity standard.
    Workshop artifacts (ATLAS_MISSION_COMPLETE, REPOSITORY_SUMMARY) and stale
    identity strings (epicon.dev, Mobius Systems) contradict the truth-only
    README merged in C-367. PR-2 of C-373 handoff.
  ANCHORS:
    - ATLAS HANDOFF C-373 MVP extraction
    - README.md truth-only standard (merged #19/#20)
  BOUNDARIES: Hygiene only — no validator logic, no chain, no demo repo
  COUNTERFACTUAL: If federation Guard runs regress, halt C-373 and restore
counterfactuals:
  - If workshop file removal breaks CI references, patch in same PR
  - If identity normalization misses a user-facing surface, file follow-up issue

---

"Intent precedes authority."

  

[cursor]

Bugbot is not enabled for your account, so this pull request was not reviewed.

Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 5165c3b41c

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Align PR guidance with the legacy CI gate

This new guidance tells contributors to include only a canonical fenced intent block, but the CI workflow that still runs for PRs (.github/workflows/ci.yml lines 98-102) fails unless the PR body contains the literal EPICON INTENT PUBLICATION. A PR following this document and the README will satisfy the shipped Guard but still fail the epicon-check job, so either align the legacy job with canonical intent extraction or document the extra marker until that job is removed.

Useful? React with 👍 / 👎.