Refresh portable CiteWire continuity from current main

.claude/orchestration/execution-state.yaml

@@ -0,0 +1,96 @@
+schema_version: 3
+artifact: citewire-orchestration-execution-state
+as_of: "2026-08-23"
+claim_status: Verified
+
+canonical:
+  repository: Openly-Useful/citewire
+  main_commit: e12d9b6e8efed725a085a32e935e63e35241859a
+  website: https://citewire.org/
+  website_status: "HTTPS 200"
+  community_version: 0.2.0
+  npm_latest: 0.1.0
+  tests: 119
+  release_checks: 5
+  node_ci: [18, 22]
+
+merged_foundations:
+  pull_requests: [2, 3, 4, 6, 7, 8]
+  capabilities:
+    - source registry and rights policy
+    - RSS and MCP projections
+    - optional local Studio
+    - credential-reference and connector boundaries
+    - deterministic classifier calibration
+    - fail-closed editorial shadow engine
+  safety_boundary: "Sources and connectors are inert by default; classifier and editorial engine cannot publish."
+
+open_drafts:
+  orchestration:
+    repository: Openly-Useful/citewire
+    pull_request: 1
+    state: "draft; refresh in progress"
+  openly_useful_link:
+    repository: Openly-Useful/openlyuseful.org
+    pull_request: 8
+    head: e48d6069e33f84a85d41ad397bc4ef74d3906451
+    state: "draft, clean, CI green"
+  karaya_link:
+    repository: MeekPhills/karayagroup
+    pull_request: 17
+    head: 004a8e09cfe146324bfe481664a5b68c182dc6b2
+    state: "draft, clean, CI green, read-aloud approval pending"
+  cloud:
+    repository: MeekPhills/citewire-cloud
+    pull_request: 1
+    head: 69068275ca0e332e36304533aa0f6b5d2e291405
+    state: "draft, clean, Node 18/22 green, undeployed"
+    community_pin: 10aee95ac95bb437b4607723cd20fa5c8f9d1879
+
+linear:
+  launch_parent: "OU-143 In Progress"
+  completed_foundations:
+    - "OU-145 Done"
+    - "OU-180 Done"
+    - "OU-181 Done"
+    - "OU-182 Done"
+    - "OU-183 Done"
+  immutable_release: "OU-149 Todo"
+  karaya_truth: "KAR-69 In Progress"
+
+karaya_observation:
+  registered_sources: 49
+  monitored_sources: 27
+  directory_only_sources: 22
+  visible_items_seven_days: 6
+  newest_item_age_hours: 60.6
+  cron: "POST /api/cron/ingest returned 200 at 15-minute cadence"
+  unknowns:
+    - source-level fetch results
+    - queue age
+    - held volume
+    - migration state
+
+protected_state:
+  untracked_owner_screenshots: 41
+  dirty_worktrees:
+    - parked CiteWire prototype
+    - Karaya editorial-shadow proposal
+    - Karaya navigation work
+  rule: "Preserve exactly; never stage, clean, move, delete, or credit as completed work."
+
+next_safe_sequence:
+  - validate and keep orchestration PR 1 draft
+  - obtain separate merge approval for Openly Useful PR 8
+  - obtain Luis read-aloud and merge approval for Karaya PR 17
+  - complete KAR-69 read-only production truth
+  - sequence Karaya shadow policy, exceptions console, and reversible canary
+  - obtain separate immutable-release approval for OU-149
+
+hard_stops:
+  - failed check or unexpected diff
+  - secret or protected asset
+  - paid-service decision
+  - provider, source, or connector activation
+  - migration or production data/configuration mutation
+  - merge, deployment, DNS change, tag, package publish, release, or registry submission without explicit approval

.claude/orchestration/recovery-ledger.yaml

@@ -0,0 +1,56 @@
+schema_version: 3
+artifact: citewire-orchestration-recovery-ledger
+as_of: "2026-08-23"
+
+claim_status_legend:
+  Verified: "Reproduced locally or read directly from the current remote or public endpoint."
+  Historical: "Recorded evidence that must be refreshed before a mutation."
+  Unknown: "Not established; do not infer authority or safety."
+
+verified:
+  - id: REC-001
+    claim: "Openly-Useful/citewire is the canonical public repository at main e12d9b6."
+    boundary: "Repository existence does not authorize release or registry actions."
+  - id: REC-002
+    claim: "citewire.org serves the CiteWire landing page over HTTPS with status 200."
+    boundary: "No DNS or deployment change is authorized by this record."
+  - id: REC-003
+    claim: "Community main passes 119 tests and five release checks with zero package dependencies."
+    boundary: "This is not publication evidence."
+  - id: REC-004
+    claim: "Public source, Studio, connector, classifier, and editorial foundations are merged and inert by default."
+    boundary: "Do not activate providers, connectors, credentials, or publishing."
+  - id: REC-005
+    claim: "Openly Useful PR 8 and Karaya PR 17 are current clean green drafts."
+    boundary: "Each merge remains separately owner-gated; Karaya also requires read-aloud approval."
+  - id: REC-006
+    claim: "Cloud PR 1 is a clean undeployed draft at 6906827 with Node 18/22 CI green and the Community archive pinned to 10aee95."
+    boundary: "Do not deploy or migrate to npm before immutable Community publication."
+  - id: REC-007
+    claim: "npm latest is citewire 0.1.0 and no CiteWire GitHub release or tag exists."
+    boundary: "OU-149 remains an immutable-release gate."
+  - id: REC-008
+    claim: "Karaya cron requests returned 200 every 15 minutes while the newest visible item was about 60.6 hours old."
+    boundary: "Finish KAR-69 read-only truth before changing data, sources, thresholds, policy, or migrations."
+  - id: REC-009
+    claim: "Forty-one untracked owner screenshots and unrelated dirty worktrees remain protected."
+    boundary: "Never stage, edit, move, clean, delete, or use them as an implementation baseline."
+
+unknowns:
+  - id: REC-401
+    topic: "Karaya source-level failures, queue age, held volume, and migration state"
+    boundary: "Read-only investigation only under KAR-69."
+  - id: REC-402
+    topic: "Cloud operator, tenants, support/privacy, retention, billing, credentials, and deployment"
+    boundary: "Separate owner decisions and account-isolation review required."
+  - id: REC-403
+    topic: "Immutable npm, GitHub release, MCP registry, and catalog sequence"
+    boundary: "Separate explicit approval required for every irreversible step."
+
+safety_state:
+  contains_credentials: false
+  contains_private_transcript: false
+  contains_local_paths: false
+  provider_activation_authorized: false
+  publication_authorized: false
+  production_mutation_authorized: false

.claude/orchestration/streams/WS-001.md

@@ -0,0 +1,13 @@
+# WS-001 — Orchestration continuity
+
+- Status: active refresh.
+- Dependencies: none.
+- Ownership: `CLAUDE.md`, `PROJECT_HANDOFF.md`,
+  `CLAUDE_CODE_LAUNCH_PROMPT.md`, and `.claude/orchestration/`.
+- Verified state: canonical main is `e12d9b6`; the previous orchestration
+  snapshot was stale and PR #1 remains draft.
+- Done when: portable artifacts parse, describe exactly 17 streams, contain no
+  secrets or local paths, match current remote truth, and pass Node 18/22 CI.
+- Next action: validate and push this continuity-only refresh.
+- Stop for: product-code diff, secret, protected asset, failed check, merge, or
+  any external mutation beyond the already authorized tracking refresh.

.claude/orchestration/streams/WS-002.md

@@ -0,0 +1,12 @@
+# WS-002 — Canonical identity and authority
+
+- Status: complete.
+- Dependencies: WS-001.
+- Ownership: identity and governance metadata.
+- Verified state: CiteWire is the public brand, `citewire` is the technical
+  token, and `Openly-Useful/citewire` is the canonical repository.
+- Done when: repository, package, server metadata, documentation, and website
+  use the same identity. That condition is met on main.
+- Next action: preserve identity consistency.
+- Stop for: repository transfer, archive, rename, package publication,
+  registry submission, or Cloud operator inference without separate approval.

.claude/orchestration/streams/WS-003.md

@@ -0,0 +1,12 @@
+# WS-003 — Repository route and history
+
+- Status: complete for the current public route.
+- Dependencies: WS-002.
+- Ownership: repository-route evidence only.
+- Verified state: the canonical public repository exists under Openly Useful
+  and current main is reproducible at `e12d9b6`.
+- Done when: the chosen public route is reachable and its current history is
+  preserved. No legacy archive or transfer is required by this checkpoint.
+- Next action: none.
+- Stop for: history rewrite, mirror, transfer, archive, deletion, or visibility
+  change without explicit approval and a rollback plan.

.claude/orchestration/streams/WS-004.md

@@ -0,0 +1,12 @@
+# WS-004 — Community 0.2 candidate
+
+- Status: complete and unpublished.
+- Dependencies: WS-002.
+- Ownership: package and release-candidate metadata.
+- Verified state: version `0.2.0` is merged on canonical main and passes 119
+  committed tests plus five release checks.
+- Done when: exact main passes isolated install, tests, release checks, package
+  inspection, syntax, diff, and Node 18/22 CI.
+- Next action: keep unpublished until WS-008 receives exact approval.
+- Stop for: failed check, version collision, tag, publish, release, or registry
+  action.

.claude/orchestration/streams/WS-005.md

@@ -0,0 +1,12 @@
+# WS-005 — CiteWire landing and HTTPS
+
+- Status: complete.
+- Dependencies: WS-002 and WS-004.
+- Ownership: `site/` and its committed regression test.
+- Verified state: `https://citewire.org/` returns HTTPS 200 with the CiteWire
+  landing page and strict response headers.
+- Done when: canonical content, HTTPS, assets, robots, sitemap, and outbound
+  links are healthy. The availability gate is met.
+- Next action: none.
+- Stop for: DNS, certificate, hosting, or deployment change without separate
+  owner approval.

.claude/orchestration/streams/WS-006.md

@@ -0,0 +1,12 @@
+# WS-006 — Openly Useful CiteWire link
+
+- Status: ready draft, unmerged.
+- Dependencies: WS-005.
+- Ownership: the CiteWire card in `open-source.html` and its committed site
+  validator.
+- Verified state: PR #8 head `e48d606` is clean, mergeable, and green. Its
+  exact two-file diff targets `https://citewire.org`.
+- Done when: the focused diff is separately approved and merged.
+- Next action: obtain merge approval.
+- Stop for: expanded diff, invalid HTTPS, failed CI, merge, or deploy without
+  approval.

.claude/orchestration/streams/WS-007.md

@@ -0,0 +1,13 @@
+# WS-007 — Karaya CiteWire bridge
+
+- Status: ready draft, owner-gated.
+- Dependencies: WS-005.
+- Ownership: the bridge document, About-page CiteWire link, and committed
+  compliance regression.
+- Verified state: PR #17 head `004a8e0` is clean and green; 432 tests, build,
+  registry, audit, compliance, and the live target passed.
+- Done when: Luis approves the exact visible copy by read-aloud, then separately
+  approves merge and production verification.
+- Next action: present the visible copy for approval.
+- Stop for: visible copy without approval, protected screenshots, failed
+  check, merge, or deployment.

.claude/orchestration/streams/WS-008.md

@@ -0,0 +1,12 @@
+# WS-008 — Immutable Community release
+
+- Status: blocked on explicit owner approval.
+- Dependencies: WS-003, WS-004, and WS-005.
+- Ownership: release workflow, changelog, distribution, and release docs.
+- Verified state: npm latest is `citewire@0.1.0`; no CiteWire tag or GitHub
+  release exists. Community `0.2.0` is not published.
+- Done when: an approved tag, npm integrity and provenance, GitHub release,
+  support/security URLs, and registry records are independently verified.
+- Next action: keep OU-149 Todo until exact immutable-step approval.
+- Stop for: tag, npm publish, GitHub release, registry or catalog submission,
+  version collision, or missing provenance.

.claude/orchestration/streams/WS-009.md

@@ -0,0 +1,12 @@
+# WS-009 — Cloud archive-pin alignment
+
+- Status: complete, preserve-only.
+- Dependencies: WS-001.
+- Ownership: evidence only.
+- Verified state: Cloud PR #1 head `6906827` pins Community commit `10aee95`,
+  passes 15 tests and Node 18/22 CI, and remains a clean undeployed draft.
+- Done when: Cloud docs and lockfile agree without implying availability or
+  deployment. That condition is met.
+- Next action: preserve the current draft.
+- Stop for: provider, participant, credential, paid service, domain,
+  deployment, or runtime decision.

.claude/orchestration/streams/WS-010.md

@@ -0,0 +1,13 @@
+# WS-010 — Cloud npm migration
+
+- Status: blocked on WS-008.
+- Dependencies: WS-008.
+- Ownership: Cloud `package.json` and `package-lock.json` only.
+- Verified state: Cloud still uses the exact Community archive pin; the
+  required public npm `0.2.0` artifact does not exist.
+- Done when: npm provenance and MCP identity are verified, then isolated
+  install, all tests, syntax, direct HTTP smoke, concurrent account-isolation,
+  diff, and Node 18/22 CI pass while Cloud stays draft and undeployed.
+- Next action: retain the archive pin.
+- Stop for: wrong provenance, lockfile surprise, failed account isolation,
+  publication, or deployment.

.claude/orchestration/streams/WS-011.md

@@ -0,0 +1,13 @@
+# WS-011 — Cloud private-alpha operations
+
+- Status: blocked on owner decisions.
+- Dependencies: WS-002 and WS-009.
+- Ownership: Cloud auth, HTTP, plan, tool, test, and owner-decision surfaces.
+- Verified state: Cloud PR #1 is fail-closed, account-isolated, draft, and
+  undeployed. Operator, tenant, support/privacy, domain, retention, billing,
+  OAuth, participant, and rollback decisions remain unresolved.
+- Done when: those decisions are approved and committed account-isolation and
+  security tests pass. Deployment remains a separate gate.
+- Next action: maintain the decision checklist.
+- Stop for: credential delivery, paid service, provider activation, privacy or
+  legal commitment, account-isolation failure, or deployment.

.claude/orchestration/streams/WS-012.md

@@ -0,0 +1,13 @@
+# WS-012 — Karaya production truth
+
+- Status: in progress, read-only.
+- Dependencies: WS-001.
+- Ownership: the dated production-truth evidence packet only.
+- Verified state: 49 sources are registered, 27 monitored, 22 directory-only,
+  and six items appeared in seven days. The newest was about 60.6 hours old.
+  Ingest cron requests returned 200 every 15 minutes.
+- Done when: deployed commit, migrations, source and circuit-breaker health,
+  queue age, held volume, corpus drift, and vendor provenance are reconciled.
+- Next action: complete KAR-69 with authorized read-only evidence.
+- Stop for: database write, migration, source or provider activation, policy or
+  threshold change, corpus rewrite, secret, or rights ambiguity.

.claude/orchestration/streams/WS-013.md

@@ -0,0 +1,13 @@
+# WS-013 — Community source and projection contract
+
+- Status: complete.
+- Dependencies: WS-002 and WS-004.
+- Ownership: Community registry, rights, RSS/MCP projections, schemas, tests,
+  and documentation.
+- Verified state: merged PR #6 supplies versioned fail-closed source, rights,
+  attribution, canonical-link, RSS, and MCP contracts.
+- Done when: invalid or ambiguous rights hold, defaults stay inert, and legacy
+  `news.*` behavior remains compatible. The committed suite proves this state.
+- Next action: preserve compatibility.
+- Stop for: provider activation, credentials, Karaya-specific policy,
+  publication, registry action, or breaking contract.

.claude/orchestration/streams/WS-014.md

@@ -0,0 +1,14 @@
+# WS-014 — Karaya deterministic shadow policy
+
+- Status: blocked on WS-012.
+- Dependencies: WS-012.
+- Ownership: future Karaya policy and non-publishing shadow paths.
+- Verified state: Community has a merged generic fail-closed editorial engine,
+  but the Karaya-specific policy is not complete. The dirty Karaya proposal
+  remains uncredited and its migration is unapplied.
+- Done when: deterministic replay, bounded run identity, complete pagination,
+  safe retries, convergent writes, rights traces, and no-publish behavior pass
+  against verified production schema.
+- Next action: derive the ADR from KAR-69 truth, not the dirty proposal.
+- Stop for: migration, threshold or model-cost choice, source activation,
+  automatic publishing, or failed replay.

.claude/orchestration/streams/WS-015.md

@@ -0,0 +1,13 @@
+# WS-015 — Karaya exceptions console
+
+- Status: blocked on WS-014.
+- Dependencies: WS-014.
+- Ownership: future Karaya admin, UI, authorization, pause, and control paths.
+- Verified state: public Studio is an optional local foundation. It is not the
+  Karaya approval console and does not supply Karaya authentication or policy.
+- Done when: the console is exceptions-only, account-isolated, authorized,
+  auditable, globally pausable, accessible, and its visible tiers and reason
+  tags receive Luis's read-aloud approval.
+- Next action: write the implementation specification after WS-014.
+- Stop for: generic Studio substitution, routine review queue, unapproved copy,
+  missing pause proof, threshold choice, or data mutation.

.claude/orchestration/streams/WS-016.md

@@ -0,0 +1,12 @@
+# WS-016 — Karaya reversible canary
+
+- Status: blocked on WS-015.
+- Dependencies: WS-015.
+- Ownership: future Karaya rollout configuration and canary runbooks.
+- Verified state: no Karaya threshold change, autonomous publishing rollout,
+  canary, or rollback drill is authorized.
+- Done when: Luis approves bounded metrics, monitoring, pause, rollback, and
+  canary; independent safety checks and recovery proof pass.
+- Next action: no-change canary design only after WS-015.
+- Stop for: missing metrics, absent pause proof, deploy, threshold/source/data
+  change, provider activation, paid service, or irreversible action.

.claude/orchestration/streams/WS-017.md

@@ -0,0 +1,16 @@
+# WS-017 — Community product foundations
+
+- Status: complete and inert.
+- Dependencies: WS-004 and WS-013.
+- Ownership: Community, editorial, security, optional Studio, focused tests,
+  and product documentation.
+- Verified state: merged PRs #6, #7, and #8 provide the source registry,
+  optional Studio, credential-reference and connector boundaries, calibrated
+  classifier, and fail-closed editorial shadow engine. Main passes 119 tests.
+- Done when: all foundations remain read-only or shadow-only, default-disabled,
+  credential-safe, attribution-first, and unable to publish. That condition is
+  met on current main.
+- Next action: activate nothing without an explicit product and security gate.
+- Stop for: breaking contract, real credential storage, provider or connector
+  activation, hosted control-plane expansion, Karaya/Cloud leakage,
+  scheduling, publishing, release, registry, or deployment.