open-research-protocol 0.3.0 → 0.4.1

package/docs/DISCOVER.md

@@ -12,7 +12,8 @@ The first concrete surface is a GitHub profile scanner:
 - hand off the strongest match into `orp collaborate`
 
 Today ORP scans public GitHub owner space by default. If richer access policy
-or profile governance exists later, that belongs in Coda rather than in ORP.
+or profile governance exists later, ORP should still own the portable profile
+format and the resulting scan artifacts.
 
 ## Commands
 
@@ -52,18 +53,13 @@ GitHub scans write:
 
 These are process-only recommendation artifacts, not evidence.
 
-## Coda Relationship
+## Ownership
 
-ORP should own the portable discovery profile format and the scanning
-artifacts.
+ORP owns:
 
-If `coda-cli` exists later, the clean role for Coda is:
+- the portable discovery profile format
+- GitHub scanning
+- ranked discovery artifacts
 
-- manage active profiles
-- switch between operator contexts
-- wrap ORP commands for a smoother operator UX
-
-That keeps ORP as the protocol/runtime while letting Coda become a higher-level
-profile manager if it earns its place.
-
-For the fuller boundary, see `docs/CODA_ORP_CONTRACT.md`.
+Other tools may read or trigger ORP discovery, but ORP does not depend on a
+wrapper to manage active context or profile selection.

package/docs/NPM_RELEASE_CHECKLIST.md

@@ -15,11 +15,11 @@ Use this checklist to publish professional, versioned ORP CLI releases.
 1. Ensure `main` is green and local tests pass:
    - `python3 -m unittest discover -s tests -v`
    - `npm pack --dry-run --cache /tmp/orp-npm-cache`
-2. Bump version in `package.json` (for example `0.1.1`).
+2. Bump version in `package.json` (for example `0.4.0`).
 3. Commit and push the version bump to `main`.
 4. Create and push a matching tag:
-   - `git tag v0.1.1`
-   - `git push origin v0.1.1`
+   - `git tag v0.4.0`
+   - `git push origin v0.4.0`
 5. Watch workflow:
    - `.github/workflows/npm-publish.yml`
    - tag push is the normal publish trigger
@@ -32,8 +32,8 @@ Use this checklist to publish professional, versioned ORP CLI releases.
 Tag version must match `package.json` exactly.
 
 - Example:
-  - tag: `v0.1.1`
-  - package version: `0.1.1`
+  - tag: `v0.4.0`
+  - package version: `0.4.0`
 
 The publish workflow hard-fails if these differ.
 
@@ -48,8 +48,8 @@ If automation is temporarily unavailable:
 3. Publish:
    - `npm publish --access public`
 4. Create and push the matching tag:
-   - `git tag v0.1.1`
-   - `git push origin v0.1.1`
+   - `git tag v0.4.0`
+   - `git push origin v0.4.0`
 5. Add release notes.
 
 The tag-triggered workflow will still validate the version and will skip `npm publish` if that exact npm version already exists.

package/docs/ORP_PUBLIC_LAUNCH_CHECKLIST.md

@@ -0,0 +1,64 @@
+# ORP Public Launch Checklist
+
+Use this checklist when releasing ORP as the unified public CLI and product surface.
+
+## 1. CLI readiness
+
+- Run:
+  - `python3 -m unittest discover -s tests -v`
+  - `npm pack --dry-run --cache /tmp/orp-npm-cache`
+- Smoke-test in a fresh directory:
+  - `npm i -g open-research-protocol`
+  - `orp about --json`
+  - `orp auth login`
+  - `orp whoami --json`
+  - `orp ideas list --json`
+
+## 2. Hosted workspace readiness
+
+- Confirm the hosted workspace base URL is reachable.
+- Confirm login / verify / whoami still work from the published `orp` binary.
+- Confirm at least one real hosted idea can be:
+  - listed
+  - shown
+  - world-bound
+  - checkpoint-queued
+
+## 3. Worker loop readiness
+
+- Confirm one bound world can complete:
+  - `orp checkpoint queue --idea-id <idea-id> --json`
+  - `orp agent work --once --json`
+- Confirm the checkpoint response lands back in the hosted workspace.
+
+## 4. Package release
+
+- Bump `package.json` version.
+- Commit and push `main`.
+- Tag and push:
+  - `git tag vX.Y.Z`
+  - `git push origin vX.Y.Z`
+- Publish if needed:
+  - `npm publish --access public`
+
+## 5. Transition messaging
+
+- Treat ORP as the primary CLI surface.
+- Point old `coda-cli` users toward:
+  - `npm i -g open-research-protocol`
+  - `orp`
+- Legacy `@sproutseeds/coda-cli` package is deprecated with a migration note to `open-research-protocol`.
+
+## 6. Post-release checks
+
+- `npm view open-research-protocol version`
+- `npm i -g open-research-protocol`
+- `orp -h`
+- `orp about --json`
+
+## 7. Web app rollout coordination
+
+- Keep the web app and CLI rollout loosely coupled.
+- Launch the ORP CLI first if the web app/domain transition is still in progress.
+- Do not change domain, auth, runner, and package names all in one step unless all staging checks are green.
+- Follow [ORP_WEB_DOMAIN_TRANSITION_PLAN.md](/Users/codymitchell/Documents/code/orp/docs/ORP_WEB_DOMAIN_TRANSITION_PLAN.md) for the hosted cutover sequence.

package/docs/ORP_WEB_DOMAIN_TRANSITION_PLAN.md

@@ -0,0 +1,106 @@
+# ORP Web Domain Transition Plan
+
+Use this as the rollout record and future reference for the hosted ORP web app domain transition from `codacli.com` to the ORP-aligned domains.
+
+## Target shape
+
+- Primary branded domain: `orp.earth`
+- Full-name support domain: `openresearchprotocol.com`
+- Legacy redirect domain: `codacli.com`
+
+## Current live state
+
+- CLI/package is already public as:
+  - `open-research-protocol`
+  - `orp`
+- Hosted app canonical browser host:
+  - `https://orp.earth`
+- Support domain:
+  - `https://openresearchprotocol.com`
+- Legacy redirect domain:
+  - `https://codacli.com`
+- CLI default hosted base URL:
+  - `https://orp.earth`
+- Browser redirects are live:
+  - `www.orp.earth` -> `orp.earth`
+  - `openresearchprotocol.com` -> `orp.earth`
+  - `www.openresearchprotocol.com` -> `orp.earth`
+  - `codacli.com` -> `orp.earth`
+  - `www.codacli.com` -> `orp.earth`
+
+## What is complete
+
+- `orp.earth` and `openresearchprotocol.com` are attached to the Vercel project.
+- Namecheap DNS points all new domains at Vercel.
+- `orp.earth` is the canonical browser/app host.
+- Browser traffic from the legacy domains redirects to `orp.earth`.
+- ORP CLI now defaults to `https://orp.earth`.
+- `ORP_BASE_URL` / `CODA_BASE_URL` overrides still work.
+
+## Rollout order
+
+### 1. Domain attachment
+
+- Add `orp.earth` and `www.orp.earth` to the Vercel project.
+- Add `openresearchprotocol.com` and `www.openresearchprotocol.com` to the same project.
+- Keep `codacli.com` attached during the transition.
+- Point Namecheap DNS at the Vercel records exactly as issued.
+
+### 2. Canonical browser host
+
+- Make `orp.earth` the canonical browser/app host.
+- Update:
+  - app metadata
+  - canonical URLs
+  - OG/Twitter metadata
+  - sitemap / robots
+- Treat `openresearchprotocol.com` as a support/canonical-name domain, not necessarily the primary user-facing host.
+
+### 3. Auth and email
+
+- Update auth base URLs and callback URLs for `orp.earth`.
+- Update magic-link / verification email links to `orp.earth`.
+- Confirm cookies and session behavior work cleanly on the new canonical host.
+- Avoid running two browser-session domains in parallel longer than necessary.
+
+### 4. Runner / websocket / terminal paths
+
+- Inventory every host reference used by:
+  - runner
+  - websocket
+  - TTY / terminal pairing
+  - agent worker loops
+- Move those to ORP-aligned hosts only after staging verification.
+- If needed, use dedicated subdomains rather than mixing them into the app host.
+
+### 5. Redirects
+
+- Redirect browser traffic from `codacli.com` to `orp.earth`.
+- Keep legacy API/worker compatibility only where needed during transition.
+- Redirect `openresearchprotocol.com` to `orp.earth` unless there is a deliberate reason to keep it browsable.
+
+### 6. CLI cutover
+
+- After the hosted app is stable on `orp.earth`, update the CLI default hosted base URL.
+- Keep `ORP_BASE_URL` / `CODA_BASE_URL` overrides working during the transition.
+- Verify:
+  - `orp auth login`
+  - `orp whoami --json`
+  - `orp ideas list --json`
+  - `orp world bind ...`
+  - `orp checkpoint queue ...`
+  - `orp agent work --once --json`
+
+## Verification checklist
+
+- `orp.earth` serves the app correctly.
+- Email verification links open on `orp.earth`.
+- Existing users can log in without session confusion.
+- Runner/worker flows still connect and post responses.
+- `codacli.com` redirects cleanly.
+- `openresearchprotocol.com` resolves as intended.
+
+## Rollback
+
+- If auth or runner behavior breaks, revert the canonical host before changing the CLI default.
+- Keep `codacli.com` attached until the new host has passed real-user verification.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "open-research-protocol",
-  "version": "0.3.0",
+  "version": "0.4.1",
   "description": "ORP CLI (Open Research Protocol): agent-friendly research workflows, runtime, reports, and pack tooling.",
   "license": "MIT",
   "repository": {

package/docs/CODA_ORP_CONTRACT.md

@@ -1,222 +0,0 @@
-# Coda to ORP Contract
-
-This document defines the boundary between:
-
-- `codacli.com` / `coda-cli`
-- `ORP`
-
-The goal is to let both systems work together without turning ORP into an app
-backend or turning Coda into a second protocol runtime.
-
-## Repository Split
-
-Recommended shape:
-
-- `orp` repo
-  - protocol/runtime
-  - discovery execution
-  - collaboration execution
-  - packets, run records, summaries
-  - portable local-first CLI
-- `coda-cli` repo
-  - operator-facing wrapper
-  - active profile selection
-  - auth/session handling
-  - Coda export retrieval
-  - convenience commands layered over ORP
-- `codacli.com`
-  - authenticated web product
-  - user database
-  - idea cards
-  - feature scaffolds
-  - notes/detail sections
-  - export surface for agents and `coda-cli`
-
-## Ownership Boundary
-
-Coda owns:
-
-- user identity
-- database records
-- idea cards
-- categories
-- feature scaffolds
-- note/detail sections
-- active context selection
-- export APIs / export files
-
-ORP owns:
-
-- portable discovery profile format
-- GitHub discovery scans
-- collaboration workflows
-- gate execution
-- packets
-- run summaries
-- process artifacts
-
-In short:
-
-- Coda answers: "What does this user care about right now?"
-- ORP answers: "How do we discover, structure, and execute the work?"
-
-## MVP Rule
-
-The MVP should be read-only from Coda into ORP.
-
-That means:
-
-- Coda exports context
-- ORP consumes derived context
-- ORP produces scan/run artifacts
-- Coda may read those artifacts later
-- ORP does not write back into Coda yet
-
-This keeps the first integration simple and auditable.
-
-## Canonical Coda Export
-
-Coda should expose a canonical export that reflects the app's richer data
-model.
-
-Example shape:
-
-```json
-{
-  "schema_version": "1.0.0",
-  "user": {
-    "id": "user_123",
-    "handle": "cody"
-  },
-  "active_context": {
-    "idea_id": "idea_problem857",
-    "title": "Sunflower formalization work",
-    "categories": ["math", "lean", "formalization"]
-  },
-  "ideas": [
-    {
-      "id": "idea_problem857",
-      "title": "Sunflower formalization work",
-      "summary": "Look for repos and issues aligned with Problem 857 work.",
-      "tags": ["sunflower", "lean", "proof"],
-      "feature_scaffold": {
-        "areas": ["balance", "container", "docs"],
-        "notes": ["Prefer public repos first."]
-      }
-    }
-  ]
-}
-```
-
-ORP should not depend directly on the full Coda export schema.
-
-## Derived ORP Inputs
-
-`coda-cli` should derive smaller ORP-native inputs from the richer Coda export.
-
-The first derived input is an ORP discovery profile.
-
-Example:
-
-```json
-{
-  "schema_version": "1.0.0",
-  "profile_id": "idea_problem857",
-  "notes": [
-    "Derived from Coda active context."
-  ],
-  "discover": {
-    "github": {
-      "owner": {
-        "login": "SproutSeeds",
-        "type": "org"
-      },
-      "signals": {
-        "keywords": ["sunflower", "formalization", "proof"],
-        "repo_topics": ["lean", "math"],
-        "languages": ["Lean"],
-        "areas": ["balance", "container", "docs"],
-        "people": []
-      },
-      "filters": {
-        "include_repos": [],
-        "exclude_repos": [],
-        "issue_states": ["open"],
-        "labels_any": [],
-        "exclude_labels": [],
-        "updated_within_days": 180
-      },
-      "ranking": {
-        "repo_sample_size": 30,
-        "max_repos": 12,
-        "max_issues": 24,
-        "max_people": 12,
-        "issues_per_repo": 30
-      }
-    }
-  }
-}
-```
-
-Other future derived inputs may include:
-
-- collaboration bootstrap hints
-- target repo selection
-- issue lane selection
-- preferred adapters
-
-## ORP Outputs Coda May Read
-
-For the first integration, Coda should treat ORP outputs as read-only runtime
-artifacts.
-
-Useful outputs:
-
-- `orp/discovery/github/<scan_id>/SCAN.json`
-- `orp/discovery/github/<scan_id>/SCAN_SUMMARY.md`
-- `orp/artifacts/<run_id>/RUN.json`
-- `orp/artifacts/<run_id>/RUN_SUMMARY.md`
-- `orp/packets/<packet_id>.json`
-
-These let Coda display:
-
-- recommended repos/issues/people
-- latest collaboration run results
-- packetized process context
-
-## CLI Relationship
-
-`coda-cli` should be a thin wrapper over ORP, not a second workflow engine.
-
-Good examples:
-
-- `coda profile export`
-- `coda profile use <idea-id>`
-- `coda discover`
-- `coda collaborate init`
-
-Under the hood, those should call ORP's JSON surfaces such as:
-
-- `orp discover profile init --json`
-- `orp discover github scan --json`
-- `orp collaborate init --json`
-- `orp collaborate run --json`
-
-## Non-Goals For ORP
-
-ORP should not own:
-
-- authenticated user databases
-- profile sharing semantics
-- team/private visibility policy
-- app-level note editing
-- direct mutation of Coda records
-
-Those belong in Coda.
-
-## Practical Rule
-
-When in doubt:
-
-- if it is portable execution or protocol data, keep it in ORP
-- if it is user/app context or authenticated product state, keep it in Coda