v0.4.24

This release restores the ORP CI and npm publish path after recent workflow failures, while preserving the existing user-facing CLI surface.

Fixed:

• Hardened hosted keychain sync tests so Ubuntu CI does not require the macOS security binary.
• Made source-checkout update tests force the intended unsafe/safe states instead of depending on ambient GitHub Actions checkout behavior.
• Moved quick kernel benchmark unittest coverage to deterministic report-shape and functional-evidence checks, leaving committed benchmark threshold policy in the dedicated kernel CI checker.
• Stabilized runner work completion sync so the touched linked-session timestamp and runner sync payload share one completion timestamp.

Published package: open-research-protocol@0.4.24

v0.2.1

ORP 0.2.1 switches the public Problem 857 sync path to the public sunflower-lean repository. In PROBLEM857_SOURCE_MODE=public_repo, ORP now syncs https://github.com/SproutSeeds/sunflower-lean into sunflower_lean/ and generates the ORP-owned 857 bridge files it needs on top of that public repo.\n\nThis release also updates the Problem 857 public-repo profile, packet/atomic-context parsing, docs, and regression coverage so the empty-repo -> public sync -> Problem 857 workflow is honest and reproducible.

v0.2.0

Full Changelog: v0.1.6...v0.2.0

v0.1.6

ORP 0.1.6 improves the public Problem 857 workflow.

Highlights:

• replaces the starter spec_faithfulness stub with a real public consistency check
• validates that the synced erdos_problem.857.json, installed scope YAML, and starter board agree on the target problem
• upgrades the problem857 pack profile so spec_faithfulness is evidence-bearing while the remaining starter gates stay explicitly marked as scaffold or stub
• updates pack install guidance and pack docs to tell users to sync Problem 857 before running the discovery lane

Validated locally and in a clean-room repo with live Erdos data, then published from GitHub Actions.

v0.1.5

ORP 0.1.5

ORP 0.1.5 tightens the epistemic clarity of starter workflows for both humans and agents.

Highlights

• Added explicit starter/stub/evidence markers to generated configs, RUN.json, packets, and run summaries.
• Added packet repo.git.present so non-git workspaces no longer look like “missing” git metadata.
• Added explicit evidence-status fields for gates and packet-level strongest evidence paths.
• Marked starter board scaffolding directly in generated board JSON.

Why this matters

The public problem857 starter flow is intentionally scaffolded. 0.1.5 makes that fact machine-readable instead of forcing agents to infer it from prose or stub files.

That means a careful agent can now answer:

• which parts of a run are starter scaffolding,
• which gates are still stubs,
• where the strongest current evidence files live,
• and whether the workspace is even a git checkout.

Public package

• npm: https://www.npmjs.com/package/@sproutseeds/orp-cli
• repo: https://github.com/SproutSeeds/orp

v0.1.4

ORP 0.1.4

ORP 0.1.4 is the first explicitly agent-first release of the public CLI.

This release makes ORP easier for agentic systems to discover, understand, and operate without scraping human-oriented terminal output.

Highlights

• Added orp about --json as a machine-readable discovery surface for tool metadata, artifact paths, schemas, supported commands, and bundled packs.
• Added root llms.txt so agents scanning a repo or package can find the right entry points quickly.
• Added docs/AGENT_LOOP.md as the canonical operating rhythm for agent-led ORP workflows.
• Added native --json output to the full basic agent loop: orp init, orp gate run, orp packet emit, orp report summary, orp erdos sync, orp pack list, orp pack install, and orp pack fetch.
• Updated npm metadata and repo docs so ORP is more searchable and legible for AI-agent use cases.

Why this matters

ORP has always had stable artifact paths and process boundaries. 0.1.4 makes those affordances first-class for automated systems:

• discovery via llms.txt and orp about --json
• stable machine-readable outputs via --json
• a clear operating loop for agents in docs/AGENT_LOOP.md

This is meant to make ORP usable not just by humans running commands manually, but by agentic systems acting as the primary operator in research workflows.

Install

npm i -g @sproutseeds/orp-cli
orp about --json

Public package

• npm: https://www.npmjs.com/package/@sproutseeds/orp-cli
• repo: https://github.com/SproutSeeds/orp

v0.1.0

Initial public release.