orion-handoff 0.1.0__tar.gz

orion_handoff-0.1.0/CHANGELOG.md

@@ -0,0 +1,17 @@
+# Changelog
+
+## 0.1.0 candidate
+
+Explicit local stores, immutable task revisions and bounded JSON/text inspection.
+Pickup separates matching, integrity, observed recency and acceptance claims;
+every result carries no authority. No provider adapters or runtime integration.
+
+Release review corrections:
+
+- Reject numeric timezone offsets outside hour 00–23 / minute 00–59 before
+  normalization, including timestamps inside claims, evidence and stored records.
+- Preserve candidate identity for uncertain publication when lock or descriptor
+  cleanup fails. Attempt all descriptor cleanup and preserve original operation
+  faults. Inspect the candidate before retrying.
+
+Supported evidence is limited to the environments recorded in the release packet.

orion_handoff-0.1.0/CONTRIBUTING.md

@@ -0,0 +1,20 @@
+# Development and conformance
+
+Use an isolated checkout and disposable environments. No test may use a real handoff store, native hook, transcript, account, phone or browser. Keep source and installed runtime separate.
+
+```sh
+python3.11 -m venv .venv-dev
+.venv-dev/bin/python -m pip install -r requirements-build.txt
+.venv-dev/bin/python -m pip install --no-deps --no-build-isolation .
+.venv-dev/bin/python -m unittest discover -s tests -v
+ruff check src tests
+.venv-dev/bin/python -m build
+```
+
+Reinstall after changing source. These are non-editable installs. Child CLI processes use temporary homes/stores and run outside the checkout. For release conformance, install the exact wheel and sdist separately into fresh Python 3.11/3.13 environments, run the tests outside the source tree, and retain artifact hashes and exit logs.
+
+The installed CLI is the primary test seam. Real subprocesses exercise contention. Test-only launchers target interruption stages without shipping any public fault controls. Exact clock equality and otherwise unreachable output-buffer caps use narrow deterministic checks against installed internal modules; this does not establish a supported Python import API.
+
+Implement one observable scenario RED→GREEN at a time. Update the living spec with contract changes and the operator runbook with operational changes. Tests are standard-library unittest; Ruff and pinned build tools are development-only. A pinned four-combination CI workflow is prepared locally; no hosted run or publishing workflow is active for this private candidate.
+
+Keep examples synthetic, preserve applicable notices, and document provenance for new copied code. This private implementation was written from the reviewed behavior spec; private runtime files and history are not redistributed.

orion_handoff-0.1.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Dan Mercede
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

orion_handoff-0.1.0/MANIFEST.in

@@ -0,0 +1,9 @@
+include README.md LICENSE SECURITY.md CONTRIBUTING.md CHANGELOG.md RELEASE_CHECKLIST.md requirements-build.txt
+recursive-include src *.py
+recursive-include specs *.md
+recursive-include docs *.md
+recursive-include examples *.json
+recursive-include tests *.py
+prune .private
+prune .venv-dev
+global-exclude __pycache__ *.py[cod]

orion_handoff-0.1.0/PKG-INFO

@@ -0,0 +1,87 @@
+Metadata-Version: 2.4
+Name: orion-handoff
+Version: 0.1.0
+Summary: Carry bounded, unverified task context between local sessions
+Author: Dan Mercede
+License-Expression: MIT
+Requires-Python: >=3.11
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Dynamic: license-file
+
+# Orion Handoff
+
+Carry bounded task context between local sessions. A producer records what it observed; another session selects the intended task and reviews what remains uncertain. Handoff data never grants permission to execute the next step.
+
+**Version 0.1.0. MIT licensed.** The installed CLI is the supported interface; internal Python imports are not a public API.
+
+## Install and select an isolated store
+
+Use CPython 3.11 or 3.13 on Linux x86_64 and a supported local filesystem. Validation covers WSL2 with an ext4-backed store. Native Windows, Windows-mounted stores, network filesystems and cross-host writers are unsupported. Exact interpreter and artifact proof belongs in the release receipt.
+
+```sh
+python3 -m venv .venv
+.venv/bin/python -m pip install orion-handoff==0.1.0
+.venv/bin/orion-handoff --json --version
+.venv/bin/orion-handoff --store /absolute/owned/scratch/handoff-demo --json init
+```
+
+Select an existing writable parent and a new store path. Every stateful invocation requires `--store` or the new `ORION_HANDOFF_STORE` environment variable. There is no implicit home, and the private tool's `ORION_HANDOFF_HOME` is ignored. Package installation creates no store, hook, service or harness pointer.
+
+For a complete wheel-only walkthrough with a synthetic generator and recovery checks, read the [guide](https://www.danmercede.com/guides/hand-off-local-agent-tasks).
+
+## A two-session walkthrough
+
+In the producer session, review `examples/record-input.json`. It is synthetic and has fixed historical times; supply actual observation times for a new demonstration. A new timestamp does not reverify an old result.
+
+```sh
+.venv/bin/orion-handoff --store /absolute/owned/scratch/handoff-demo --json record --input - < examples/record-input.json
+```
+
+In another session:
+
+```sh
+.venv/bin/orion-handoff --store /absolute/owned/scratch/handoff-demo --json pickup --task sample-task-alpha
+.venv/bin/orion-handoff --store /absolute/owned/scratch/handoff-demo --json list --task sample-task-alpha
+.venv/bin/orion-handoff --store /absolute/owned/scratch/handoff-demo --json show FULL_RECORD_ID
+```
+
+Task keys are explicit opaque identities. A project-resume selection needs exactly one current task; two tasks remain ambiguous even if one is newer, stale or done. Pickup with no selector returns provisional context without reading any records.
+
+To revise a task, send a **complete** new input with `predecessor` set to its current record ID. All existing records remain immutable. A competing update returns conflict; inspect and reconcile rather than automatically overwriting it. Marking context stale or done is a successor record, not a PM task transition.
+
+## Read results honestly
+
+JSON reports task match, structural integrity, context recency, recorded acceptance and disposition separately. `context_available` remains unverified. `inspect_only` has a selected record but no usable continuation. Missing, ambiguous or invalid context stays provisional; there is no fallback to an older baseline.
+
+Every result states `authority: none`. References, actor labels, acceptance claims, evidence and next steps are recorded data. References are never opened or fetched. Freshness describes the supplied observation time, not current source compatibility or permission. The core performs no network requests, subprocess actions, session/history reads or integration with another tool's private store.
+
+| Exit | Meaning |
+|---|---|
+| 0 | Named operation established; no execution authority. |
+| 2 | Usage/configuration error. |
+| 10 | Matched context needs inspection. |
+| 11 | Missing or ambiguous requested context. |
+| 65 | Invalid submitted input; no record committed. |
+| 69 | Store/platform/I/O unavailable. |
+| 73 | Busy, predecessor conflict or ID collision. |
+| 74 | Integrity/compatibility/budget failure or unknown commit. Inspect before retry. |
+
+## Limits and recovery
+
+Inputs and records are at most 64 KiB, the body at most 16 KiB, and a store retains at most 512 committed records. Reads are bounded and reject invalid stores rather than report partial selection as healthy. There is no automatic deletion, archive, import, migration or current-task pointer. A malformed committed record blocks selected pickup until an operator recovers the store.
+
+Locks coordinate cooperative local clients. This is not authentication or protection from malicious same-user processes. Process-interruption tests do not establish physical power-loss behavior on every filesystem.
+
+Read the [operator runbook](docs/runbooks/local-handoff-store.md) for stopped-writer backup, exact-store restore, unknown commits and retention. Uninstall preserves the store. The first version's recovery uses the exact artifact and matching backup; no prior public version exists to downgrade to.
+
+## Contracts and development
+
+- [Living implementation spec](specs/orion-handoff-core-spec.md)
+- [Release checklist](RELEASE_CHECKLIST.md)
+- [Security scope](SECURITY.md)
+- [Contribution and test instructions](CONTRIBUTING.md)
+
+The core has no runtime dependencies outside the Python standard library. PM, browser, phone, Remote Hands and vendor harness integrations are separate packages. An optional future starter profile needs exact component pins and its own combined proof. Releasing this package does not migrate an installed estate.
+
+MIT. Copyright 2026 Dan Mercede.

orion_handoff-0.1.0/README.md

@@ -0,0 +1,76 @@
+# Orion Handoff
+
+Carry bounded task context between local sessions. A producer records what it observed; another session selects the intended task and reviews what remains uncertain. Handoff data never grants permission to execute the next step.
+
+**Version 0.1.0. MIT licensed.** The installed CLI is the supported interface; internal Python imports are not a public API.
+
+## Install and select an isolated store
+
+Use CPython 3.11 or 3.13 on Linux x86_64 and a supported local filesystem. Validation covers WSL2 with an ext4-backed store. Native Windows, Windows-mounted stores, network filesystems and cross-host writers are unsupported. Exact interpreter and artifact proof belongs in the release receipt.
+
+```sh
+python3 -m venv .venv
+.venv/bin/python -m pip install orion-handoff==0.1.0
+.venv/bin/orion-handoff --json --version
+.venv/bin/orion-handoff --store /absolute/owned/scratch/handoff-demo --json init
+```
+
+Select an existing writable parent and a new store path. Every stateful invocation requires `--store` or the new `ORION_HANDOFF_STORE` environment variable. There is no implicit home, and the private tool's `ORION_HANDOFF_HOME` is ignored. Package installation creates no store, hook, service or harness pointer.
+
+For a complete wheel-only walkthrough with a synthetic generator and recovery checks, read the [guide](https://www.danmercede.com/guides/hand-off-local-agent-tasks).
+
+## A two-session walkthrough
+
+In the producer session, review `examples/record-input.json`. It is synthetic and has fixed historical times; supply actual observation times for a new demonstration. A new timestamp does not reverify an old result.
+
+```sh
+.venv/bin/orion-handoff --store /absolute/owned/scratch/handoff-demo --json record --input - < examples/record-input.json
+```
+
+In another session:
+
+```sh
+.venv/bin/orion-handoff --store /absolute/owned/scratch/handoff-demo --json pickup --task sample-task-alpha
+.venv/bin/orion-handoff --store /absolute/owned/scratch/handoff-demo --json list --task sample-task-alpha
+.venv/bin/orion-handoff --store /absolute/owned/scratch/handoff-demo --json show FULL_RECORD_ID
+```
+
+Task keys are explicit opaque identities. A project-resume selection needs exactly one current task; two tasks remain ambiguous even if one is newer, stale or done. Pickup with no selector returns provisional context without reading any records.
+
+To revise a task, send a **complete** new input with `predecessor` set to its current record ID. All existing records remain immutable. A competing update returns conflict; inspect and reconcile rather than automatically overwriting it. Marking context stale or done is a successor record, not a PM task transition.
+
+## Read results honestly
+
+JSON reports task match, structural integrity, context recency, recorded acceptance and disposition separately. `context_available` remains unverified. `inspect_only` has a selected record but no usable continuation. Missing, ambiguous or invalid context stays provisional; there is no fallback to an older baseline.
+
+Every result states `authority: none`. References, actor labels, acceptance claims, evidence and next steps are recorded data. References are never opened or fetched. Freshness describes the supplied observation time, not current source compatibility or permission. The core performs no network requests, subprocess actions, session/history reads or integration with another tool's private store.
+
+| Exit | Meaning |
+|---|---|
+| 0 | Named operation established; no execution authority. |
+| 2 | Usage/configuration error. |
+| 10 | Matched context needs inspection. |
+| 11 | Missing or ambiguous requested context. |
+| 65 | Invalid submitted input; no record committed. |
+| 69 | Store/platform/I/O unavailable. |
+| 73 | Busy, predecessor conflict or ID collision. |
+| 74 | Integrity/compatibility/budget failure or unknown commit. Inspect before retry. |
+
+## Limits and recovery
+
+Inputs and records are at most 64 KiB, the body at most 16 KiB, and a store retains at most 512 committed records. Reads are bounded and reject invalid stores rather than report partial selection as healthy. There is no automatic deletion, archive, import, migration or current-task pointer. A malformed committed record blocks selected pickup until an operator recovers the store.
+
+Locks coordinate cooperative local clients. This is not authentication or protection from malicious same-user processes. Process-interruption tests do not establish physical power-loss behavior on every filesystem.
+
+Read the [operator runbook](docs/runbooks/local-handoff-store.md) for stopped-writer backup, exact-store restore, unknown commits and retention. Uninstall preserves the store. The first version's recovery uses the exact artifact and matching backup; no prior public version exists to downgrade to.
+
+## Contracts and development
+
+- [Living implementation spec](specs/orion-handoff-core-spec.md)
+- [Release checklist](RELEASE_CHECKLIST.md)
+- [Security scope](SECURITY.md)
+- [Contribution and test instructions](CONTRIBUTING.md)
+
+The core has no runtime dependencies outside the Python standard library. PM, browser, phone, Remote Hands and vendor harness integrations are separate packages. An optional future starter profile needs exact component pins and its own combined proof. Releasing this package does not migrate an installed estate.
+
+MIT. Copyright 2026 Dan Mercede.

orion_handoff-0.1.0/RELEASE_CHECKLIST.md

@@ -0,0 +1,13 @@
+# Release checklist
+
+MIT. Selected source rights confirmed by the author. Release approval covers the exact recorded candidate and destinations.
+
+- Verify wheel/sdist on CPython 3.11 and 3.13 with the installed CLI outside source.
+- Confirm explicit-store isolation, task matching, observed recency, immutable revision integrity and uncertain-commit receipts.
+- Validate backed-up stores, uninstall/reinstall preservation and future-version refusal.
+- Bind distribution files to SHA256SUMS; verify the manifest before uploading. Never rebuild inside the publishing job.
+- Require CI, secret scans, dependency review, protected human review and the PyPI environment approval.
+- Verify source, package install, site assets, Works routing and canonical guide at their public consumer boundaries.
+- A package release performs no estate integration, native hook installation or migration.
+
+See [release operations](docs/runbooks/release.md) and [local recovery](docs/runbooks/local-handoff-store.md).

orion_handoff-0.1.0/SECURITY.md

@@ -0,0 +1,11 @@
+# Security scope
+
+The core records unverified local task context. It does not authenticate actors, grant execution authority, validate approval, execute next steps or fetch references. Record prose and evidence are untrusted data.
+
+The supported coordination model is cooperating processes under one local user on a tested Linux local filesystem. Other processes with that user's access can modify files or bypass advisory locks. Cross-host fencing, network filesystems and adversarial same-user isolation are outside the contract.
+
+Core commands require an explicit store. They reject unsafe paths, ownership/modes, unrecognized entries, invalid revision chains and bounded-I/O failures. Those checks reduce accidental escape and corruption; they are not a sandbox. Do not place secrets in synthetic examples or send a real handoff store as a bug report.
+
+Report vulnerabilities privately through [GitHub security advisories](https://github.com/OrionArchitekton/orion-handoff/security/advisories/new). Provide the candidate version, platform/filesystem, a minimal synthetic reproduction and the observed exit/JSON. Exclude tokens, transcripts, personal paths, approvals and private task content.
+
+No security contact, hosted reporting service or notification workflow is installed by the package.

orion_handoff-0.1.0/docs/runbooks/local-handoff-store.md

@@ -0,0 +1,73 @@
+---
+verified: 2026-10-17
+review_after: 2026-11-17
+topics:
+  - orion-handoff
+  - private-extraction
+  - local-store-recovery
+references:
+  - ../../specs/orion-handoff-core-spec.md
+  - ../../README.md
+  - ../../RELEASE_CHECKLIST.md
+---
+
+# Local handoff core: operator runbook
+
+The installed CLI has passed isolated synthetic conformance. Published checksums bind the release artifacts; validation covers CPython 3.11 and 3.13 on WSL2 Linux x86_64/ext4. Select a new user-owned store for a trial. This runbook neither installs native hooks nor migrates existing handoffs.
+
+## Rollout and isolated use
+
+Use an owned scratch parent, a fresh virtual environment and a new explicit store. Record the artifact digest and interpreter/filesystem combination before use. Install the reviewed wheel into that environment; verify `orion-handoff --version` before selecting state. Installation/help/import must create no handoff store or harness integration.
+
+Example flow for this candidate, one invocation at a time:
+
+```text
+orion-handoff --store /owned/scratch/sample-handoff --json init
+orion-handoff --store /owned/scratch/sample-handoff --json record --input -
+orion-handoff --store /owned/scratch/sample-handoff --json list --task sample-task-alpha
+orion-handoff --store /owned/scratch/sample-handoff --json pickup --task sample-task-alpha
+orion-handoff --store /owned/scratch/sample-handoff --json show FULL_RECORD_ID
+```
+
+The `record` invocation receives the reviewed synthetic JSON on stdin; reference strings are not opened. The [example input](../../examples/record-input.json) has fixed historical times and will naturally age. For a fresh demonstration, the producer must supply its actual observation time. Changing a timestamp is not a way to reverify old work. Copy a **complete** successor input and set predecessor to the observed current record ID when revising; there is no patch inheritance or status mutation command.
+
+## Validation and monitoring
+
+Check parsed JSON and exit status together. Exit 0 only establishes its named operation; context_available remains unverified. Inspect-only (10), no-match/ambiguity (11), conflict/busy (73) and integrity/unknown commit (74) are intentional distinct outcomes. No hook-compatible fail-open mode is provided.
+
+Observe current record IDs, chain integrity, record count, selected-task dimensions and warnings through the CLI. No background monitor is installed. Listing is bounded and reports truncation; it is not a complete export when truncated. A store limit refuses new writes and never triggers deletion. Null/future observations and unchecked references remain review work.
+
+## Backup and restore
+
+1. Stop all cooperating producers and readers for the selected synthetic/user-owned store. A filesystem copy during active publication is not the supported backup procedure.
+2. Copy the complete selected store, including version marker and empty lock file, with modes preserved into a new private directory. Do not follow symlinks; unsafe objects require inspection. Backup access must remain restricted to the owner. Preserve hard links if present; otherwise validate the restored structure before use.
+3. Record original record byte hashes and the complete expected record count (at most 512). Preserve temporary files as evidence; never silently discard them in backup.
+4. Restore to a fresh explicit path on a supported local filesystem. Verify ownership/modes, compatible versions and all expected IDs/hashes, then inspect current context through the reviewed CLI. Keep the original untouched until this comparison succeeds.
+5. Re-enable only the selected cooperating users/processes. Native estate hooks are not part of this core procedure.
+
+No command writes another tool's private state. The core does not search for a backup, import old Markdown packs or select a “nearest” compatible record automatically.
+
+## Failure and recovery decisions
+
+| Observation | Action |
+|---|---|
+| Conflict | Inspect current record. Reconcile the whole successor deliberately; do not automatically replace the winning context. |
+| Busy | Check live cooperating processes. Retry after the holder exits; never delete or recreate the lock file to break a lock. |
+| Commit unknown / writer killed without receipt | Preserve output if present, inspect candidate ID and current task chain. Compare committed content with intended input before deciding on any new successor. Unlock/close acknowledgement errors after attempted publication also return `commit_unknown` (74) with the candidate ID. Never infer that exit 74 means nothing was written, and never blindly resend. |
+| Recognized orphan temporary warning | Stop writers, back up the whole store, inspect final ID/inode relationships. Remove only specifically identified orphan names after verifying committed record integrity; this manual cleanup is not an automatic core command. Keep the backup. |
+| Incomplete initialization | Preserve the incomplete directory for inspection. Select a fresh empty store path for a retry; do not initialize over unknown files. |
+| Corrupt/unsafe/over-limit store | Stop writes and preserve evidence. Inspect a known compatible backup in a fresh path; do not delete an inconvenient record to make pickup look healthy. |
+| Incompatible version | Use the matching reviewed artifact against a copy, or restore its matching backup. No automatic downgrade/migration. |
+| Unsupported filesystem | Select a newly initialized store on a tested local filesystem; moving production state is a separate backed-up operation. |
+
+## Retention and removal
+
+v0.1 retains every committed record, including stale/done/historical revisions, until the operator explicitly disposes of the selected store outside the CLI. There is no sweep, scheduled cleanup or auto-expiry deletion. Near capacity, preserve/retire a complete store and deliberately begin a new one; previous task context is not implicitly carried across. A future archive/import feature needs its own spec and lineage proof.
+
+Uninstall removes package files from the selected environment, preserving the store. To undo the isolated trial, stop its processes, preserve receipts/backup, uninstall or remove only the owned test environment, and remove only the explicitly owned synthetic store if no longer wanted. Never use recursive cleanup against `.orion`, `.claude` or `.codex`.
+
+## Limits of rollback
+
+At the first public version there is no previous public artifact to downgrade to. Recovery means reinstalling the exact reviewed artifact, selecting a validated backup/copy, or removing the isolated trial. Later upgrades must declare store compatibility and add actual upgrade/downgrade proof. Publication rollback and users' installed copies are separate from local store restore; future release notes must explain both.
+
+No estate adoption is performed by a package release. An eventual adapter migration needs a fresh inventory, explicit activation and reversal instructions, authority checks, native binding proof and a separate approval checkpoint.

orion_handoff-0.1.0/docs/runbooks/release.md

@@ -0,0 +1,19 @@
+---
+verified: 2026-10-17
+review_after: 2026-11-17
+topics: [release, pypi, github]
+references: [../../.github/workflows/release.yml, ../../.github/release-manifest.json, ../../requirements-build.txt]
+---
+# Release operations
+
+Release from a human-reviewed protected main. CI validates installed wheel and sdist separately on CPython 3.11/3.13, plus lint, secrets and dependency changes.
+
+Build distributions outside the publishing job, run the exact-artifact conformance suite, inspect exports and bind bytes to the release manifest and SHA256SUMS. If packaging documentation changes, record the new hashes and prove runtime module bytes unchanged from the approved implementation.
+
+Upload wheel, sdist, source archive and checksums to the corresponding GitHub release. Configure a PyPI Trusted Publisher scoped to OrionArchitekton/orion-handoff, release.yml, environment pypi. The protected environment requires a human reviewer. No package password or API token is needed.
+
+Dispatch release.yml from main after verifying the public GitHub release. Its verify job and publish job each download the named release files and check the fixed manifest hashes; the publishing job never checks out source, builds, or installs dependencies. It submits only wheel/sdist to PyPI. Never overwrite published version bytes.
+
+Validate public GitHub/PyPI metadata, downloaded hashes, clean installs and the installed CLI's version/pickup behavior. Monitor the exact workflow, version and artifacts; a workflow success alone is not consumer proof.
+
+Rollback: stop an unapproved pending environment deployment or future release workflow. If a public package is defective, preserve receipts, consider yanking and publish a corrected version after review. Do not delete/reuse release versions or roll back user stores automatically. Site/hub reversions are separate. No estate hooks, runtime, stores or scheduled jobs are changed by publishing.

orion_handoff-0.1.0/examples/record-input.json

@@ -0,0 +1,32 @@
+{
+  "record_version": 1,
+  "task_key": "sample-task-alpha",
+  "predecessor": null,
+  "project_key": "sample-project",
+  "title": "Inspect the sample report",
+  "status": "active",
+  "actor": "sample-producer",
+  "request_id": "sample-request-1",
+  "context_as_of": "2026-10-17T23:00:00Z",
+  "last_observed_outcome": "The synthetic report contained the expected heading.",
+  "unfinished_step": "Review the report against the current request.",
+  "recorded_next_step": "Read the current request and obtain any authority needed for further work.",
+  "remaining_authority": "This record grants no authority.",
+  "acceptance_claims": [
+    {
+      "baseline": "sample-baseline-1",
+      "reference": "sample://review/1",
+      "accepted_at": "2026-10-17T22:59:00Z"
+    }
+  ],
+  "evidence": [
+    {
+      "source": "synthetic-demo",
+      "artifact": "sample-report-1",
+      "observed_at": "2026-10-17T23:00:00Z",
+      "scope": "The heading was visible; no broader behavior was tested.",
+      "reference": "sample://report/1"
+    }
+  ],
+  "body": "Synthetic context for a private example. Recheck the current task before taking action."
+}

orion_handoff-0.1.0/pyproject.toml

@@ -0,0 +1,23 @@
+[build-system]
+requires = ["setuptools==84.0.0"]
+build-backend = "setuptools.build_meta"
+
+[project]
+name = "orion-handoff"
+version = "0.1.0"
+description = "Carry bounded, unverified task context between local sessions"
+readme = "README.md"
+requires-python = ">=3.11"
+dependencies = []
+authors = [{name = "Dan Mercede"}]
+license = "MIT"
+
+[project.scripts]
+orion-handoff = "orion_handoff.cli:main"
+
+[tool.setuptools.packages.find]
+where = ["src"]
+
+[tool.ruff]
+target-version = "py311"
+line-length = 100

orion_handoff-0.1.0/requirements-build.txt

@@ -0,0 +1,5 @@
+build==1.6.1
+packaging==26.3
+pyproject-hooks==1.3.3
+setuptools==84.0.0
+wheel==0.48.0

orion_handoff-0.1.0/setup.cfg

@@ -0,0 +1,4 @@
+[egg_info]
+tag_build = 
+tag_date = 0
+