coordination: agent-x5p2 backfill issue loopx-project#6710 and PR loopx-project#6716

Signed-off-by: JasonBuildAI <jasonbuildai@gmail.com>

Author: JasonBuildAI

.codex-coordination/claims.md

@@ -93,3 +93,4 @@
 - coordination: agent-c8v3 | 2026-10-17T04:49:28Z | follow-up: PR #6712 head amended in place (no reviewer comment existed) 772bfed09 -> 878a21249053152c413e800878cd8f9e31dff365 after an independent adversarial subagent review with no blocker. Findings resolved: (1) the discovery regression test was inert (the bare python candidate is appended unconditionally, so any PATH satisfied it) and was replaced by one that puts a stub python3.exe plus python3.12.exe and python.exe on a fixture PATH and asserts the exact list ["python3","python3.12.exe","python"]; it fails on the parent sources and passes at the amended head; (2) README/source comment now say the bare python name is resolved when the candidate is run rather than being a PATH scan result; (3) PR body now discloses the changed failure mode of tests/admission-closeout.integration.spec.ts on Windows (it resolves its interpreter from process.env, so it now finds python and runs to its own 90s bound instead of failing fast with "requires Python 3.11+"; it runs only on the Linux lane and fails either way), the two differing pre-change baseline counts (182/14 and 183/13, the difference being the timing-flaky cli.spec child-close assertion), and the remaining gap that resolveLoopXCommand builds its module fallback from bare names only. Re-verified at the amended head: whole plugin suite 188 passed / 8 failed / 196 on native Windows with no newly failing test name, typecheck and peer-range smoke green, dsh-plugin ubuntu-latest lane green and windows-latest re-running. Still not self-merged (host bootstrap/installer behavior, maintainer review required).
 - coordination: agent-x2p8 | 2026-10-17T04:50:42Z | head backfill: PR #6709 now carries commit a786ed7cb (test hardening: the child decodes the CLI event sample with its resolved default codec and the case skips with the resolved codec named where the hazard cannot be shown, instead of asserting only != utf-8); product commits unchanged, still fork-branch only, not self-merged (control-plane runtime behavior, maintainer review required). Independent agent review: APPROVE WITH NOTES; the f6b4280d2 revision and this head reproduce the reviewer numbers; the os.fdopen pins are gate-rule-only protection (reverting both leaves the suite green while the gate reports codex_agent_session.py:173, codex_checkpoint.py:415); the PR and issue now scope the reach to the benchmark/runtime callers.
 - coordination: agent-c8v3 | 2026-10-17T04:56:13Z | PR #6712 rebased onto the current main head (cd148933bb0cb00232cb3cc494f898a171ffe36c) so the branch is no longer BEHIND: 878a21249 -> 586051255d47a41dd00cb6daa060249ba43e5b5e. The change patch is byte-identical across the rebase (git diff <merge-base> HEAD hashed to 3e08ad4086bd05ffdeb16ea4727030694b28ac0e before and after), no reviewer comment existed, and the two upstream commits in that range touch no plugin file. Re-verified at the rebased head: focused regression files show only the 4 disclosed pre-existing Windows-host failures (55 passed / 4 failed of 59), and all required checks are green - Sign-off (DCO), mergify Summary, dependency-review, dsh-plugin (ubuntu-latest), dsh-plugin (windows-latest). PR state: MERGEABLE, reviewDecision REVIEW_REQUIRED, not self-merged (host bootstrap/installer behavior, maintainer review required). This claim is closed at this head unless a maintainer asks for more.
+- coordination: x5p2 | 2026-10-17T13:05:00Z | claim backfill: issue #6710 opened; PR #6716 opened on loopx-project/loopx (base main, head JasonBuildAI:codex/agent-x5p2, commits 9889d6188 + 97756955e, tested revision 97756955e); branch pushed to the fork only, not self-merged (host tree teardown + canary gate verdict, maintainer review required). Files: loopx/extensions/process_runtime.py,loopx/canary/runner.py,loopx/capabilities/issue_fix/acceptance_loop.py,examples/issue-fix-reviewer-recommendation-smoke.py,examples/issue-fix-reviewer-request-smoke.py,tests/extensions/test_process_runtime.py,tests/canary/test_smoke_fixture_cleanup.py,tests/capabilities/test_issue_fix_temporary_workspace.py. T2 duplicate check at PR time: no open issue or PR touches the read-only fixture teardown; the nearest open work is #6642/#6652 (WinError 32, a live child pins the directory - different root cause, different files) and PR #6691 (UTF-8, different files). Evidence: real single-check runner verdict returncode 0 / status failed / reason fixture-cleanup WinError 5 before -> status passed / failure_count 0 after; full-public sweep of the 33 git-object-writing checks 20 -> 18 failures and read-only-unlink failures 4 -> 0, no pass -> failure regression; examples/issue-fix-workflow-e2e-smoke.py and examples/issue-fix-reviewer-recommendation-smoke.py exit 1 -> 0; pytest facade tests/test_smoke_suite.py 1 failed -> 2 passed; risk_profile_run of loopx canary premerge 3 failures -> 0; ruff clean; 3 remaining tests/canary failures and 4 WinError 32 smoke failures reproduced on the untouched base revision fdf03ec61.

.gitignore

@@ -1,5 +1,6 @@
 .DS_Store
 .venv/
+<<<<<<< HEAD
 .idea
 node_modules/
 apps/dashboard/public/*.local.json
@@ -24,10 +25,17 @@ apps/desktop/loopx-control-plane/runtime/
 # Local/private operator skills. Generic, reusable contracts belong in docs or
 # product code; account-specific creator/operator skills stay outside git.
 skills/loopx-social-media/
+=======
+__pycache__/
+*.pyc
+.pytest_cache/
+.ruff_cache/
+>>>>>>> 7dcdc9dc7 (Initial public goal harness scaffold)
 
 # Project-local private state. Keep real project paths, task ids, tokens,
 # internal logs, and active goal state outside the public repository.
 .local/
+<<<<<<< HEAD
 .loopx/
 .goal-harness/
 .goal-wrapper.local/
@@ -44,3 +52,7 @@ logs/
 # Frontend delivery artifacts are built and qualified from source.
 /loopx/web/chat/
 /loopx/web/.chat-build-*/
+=======
+.goal-wrapper.local/
+runtime/
+>>>>>>> 7dcdc9dc7 (Initial public goal harness scaffold)

LICENSE

@@ -1,3 +1,4 @@
+<<<<<<< HEAD
 
                                  Apache License
                            Version 2.0, January 2004
@@ -200,3 +201,26 @@
    WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
    See the License for the specific language governing permissions and
    limitations under the License.
+=======
+MIT License
+
+Copyright (c) 2026 Goal Harness contributors
+
+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.
+>>>>>>> 7dcdc9dc7 (Initial public goal harness scaffold)

README.md

@@ -1,3 +1,4 @@
+<<<<<<< HEAD
 <div align="center">
 
 <h1 align="center">LoopX</h1>
@@ -812,3 +813,101 @@ terms; the historical text and notice are preserved in
 explains the version, contribution, patent-grant, and open-core boundaries.
 
 [osai-verify: eb42dd9cf910399988f0]: #
+=======
+# Goal Harness
+
+Goal Harness is a lightweight control plane for long-running agent goals. It is
+designed to sit above local agent apps, CLI sessions, recurring heartbeats, and
+goal-mode runs.
+
+It does not replace an agent or a project-specific workflow. It gives each goal
+four durable things:
+
+- a project-local goal state file,
+- a registry entry that says where the goal lives and which adapter reads it,
+- a shared runtime directory for run logs,
+- a read-only contract check before the next agent tick.
+
+## Why
+
+Long-running agent work fails less from a single weak prompt than from drift:
+lost next actions, stale assumptions, unclear handoffs, mixed project state,
+and unreviewed private data. Goal Harness keeps those boundaries explicit.
+
+## Recommended Layout
+
+Use one local checkout as the shared base:
+
+```bash
+git clone <your-fork-or-repo-url> ~/goal-harness
+python3 -m pip install -e ~/goal-harness
+```
+
+Each project keeps its own private state and thin adapter:
+
+```text
+project/
+  .local/ACTIVE_GOAL_STATE.md        # private, not committed
+  .local/GOAL_HARNESS_REGISTRY.json  # private, can contain local paths
+  scripts/project-pre-tick.py        # optional thin adapter
+
+~/.codex/goal-harness/
+  goals/<goal-id>/runs/index.jsonl   # shared runtime history
+```
+
+The core code is not copied into every project. Project files call the shared
+CLI and keep only project-specific policy, evidence readers, and guards.
+
+## CLI
+
+```bash
+goal-harness --registry .local/GOAL_HARNESS_REGISTRY.json registry
+goal-harness --registry .local/GOAL_HARNESS_REGISTRY.json history
+goal-harness --registry .local/GOAL_HARNESS_REGISTRY.json check --scan-root .
+```
+
+JSON output is available for pre-tick integration:
+
+```bash
+goal-harness --registry .local/GOAL_HARNESS_REGISTRY.json --format json check --scan-root .
+```
+
+The example registry uses `./runtime` on purpose, so demo commands do not read
+your real local goal history.
+
+## Integration Model
+
+1. Keep the shared package at one stable local path, usually `~/goal-harness`.
+2. Add a private registry in each project.
+3. Add or keep a project-specific pre-tick script that calls Goal Harness.
+4. Save adapter run logs into `~/.codex/goal-harness/goals/<goal-id>/runs/`.
+5. A future UI can read the same runtime root instead of scraping projects.
+
+## Public / Private Boundary
+
+Safe to publish:
+
+- registry schema,
+- runtime layout,
+- adapter lifecycle,
+- generic validation commands,
+- sanitized examples.
+
+Keep private:
+
+- real project paths,
+- task ids,
+- production logs,
+- internal document links,
+- credentials,
+- user-specific active goal state,
+- raw experiment metrics.
+
+See [docs/public-private-boundary.md](docs/public-private-boundary.md).
+
+## Current Status
+
+This repository is intentionally small. The first milestone is not a full agent
+platform; it is a reliable shared substrate for local goal state, run history,
+and contract checks across several projects.
+>>>>>>> 7dcdc9dc7 (Initial public goal harness scaffold)

docs/architecture.md

@@ -1,5 +1,6 @@
 # Architecture
 
+<<<<<<< HEAD
 LoopX has six durable control-plane layers, plus an optional probe surface
 whose execution policy requires read-only observation; it is not a peer layer.
 
@@ -20,28 +21,49 @@ The `pre-tick-runnable` adapter status is declared separately and is not inferre
 from `next_probe`. There is no shipped `pre_tick` module or adapter pre-tick
 package, so keep probe registration, execution policy, and adapter status as
 separate contracts.
+=======
+Goal Harness has five layers.
+
+1. **Registry**: lists known goals, their repos, adapters, status, and guards.
+2. **Goal state**: the active state file for one goal.
+3. **Adapter pre-tick**: a read-only project-specific probe.
+4. **Run log**: JSON and Markdown reports saved per goal.
+5. **Run history**: compact indexes consumed by agents, heartbeats, and UI.
+>>>>>>> 7dcdc9dc7 (Initial public goal harness scaffold)
 
 ```text
 project goal state
   + private registry
+<<<<<<< HEAD
   + optional next_probe
+=======
+  + project adapter
+>>>>>>> 7dcdc9dc7 (Initial public goal harness scaffold)
         |
         v
 shared runtime root
         |
         v
+<<<<<<< HEAD
 loopx history/check
         |
         v
 loopx status
         |
         v
 quota-aware agent tick / heartbeat / future UI
+=======
+goal-harness history/check
+        |
+        v
+agent tick / heartbeat / future UI
+>>>>>>> 7dcdc9dc7 (Initial public goal harness scaffold)
 ```
 
 The core repository intentionally avoids domain logic. A data experiment goal,
 a note-maintenance goal, and a harness self-improvement goal should share the
 same runtime and contract, but use different adapters.
+<<<<<<< HEAD
 
 ## Control Plane As Effect Interpreter
 
@@ -435,3 +457,5 @@ dashboard frontend should follow
 [dashboard-frontend-selection.md](product/roadmaps/dashboard-frontend-selection.md); the
 single-file HTML renderer remains a fallback for smoke tests and offline
 inspection.
+=======
+>>>>>>> 7dcdc9dc7 (Initial public goal harness scaffold)

docs/integration.md

@@ -1,13 +1,18 @@
 # Integration Guide
 
+<<<<<<< HEAD
 LoopX should be used as a shared local base, not copied into every
+=======
+Goal Harness should be used as a shared local base, not copied into every
+>>>>>>> 7dcdc9dc7 (Initial public goal harness scaffold)
 project.
 
 ## Local Base
 
 Clone or symlink one copy:
 
 ```bash
+<<<<<<< HEAD
 git clone <repo-url> ~/loopx
 ~/loopx/scripts/install-local.sh
 loopx doctor
@@ -49,11 +54,16 @@ loopx-canary heartbeat-prompt \
 # After canary observation looks healthy, promote the checkout to default.
 ~/loopx/scripts/install-local.sh
 loopx doctor
+=======
+git clone <repo-url> ~/goal-harness
+python3 -m pip install -e ~/goal-harness
+>>>>>>> 7dcdc9dc7 (Initial public goal harness scaffold)
 ```
 
 Then projects can call:
 
 ```bash
+<<<<<<< HEAD
 loopx --registry <private-registry> registry
 loopx --registry <private-registry> history
 loopx --registry <private-registry> status
@@ -317,6 +327,11 @@ work state or local evidence, add them to `.gitignore`:
 ```gitignore
 .loopx/
 .loopx/goals/
+=======
+goal-harness --registry <private-registry> registry
+goal-harness --registry <private-registry> history
+goal-harness --registry <private-registry> check --scan-root <project-root>
+>>>>>>> 7dcdc9dc7 (Initial public goal harness scaffold)
 ```
 
 ## Project Adapter
@@ -332,11 +347,16 @@ A project adapter should be thin and project-specific. It may read:
 It should output:
 
 - `classification`,
+<<<<<<< HEAD
 - exactly one `recommended_action` for the local control loop,
+=======
+- exactly one `recommended_action`,
+>>>>>>> 7dcdc9dc7 (Initial public goal harness scaffold)
 - relevant warnings,
 - hard guards,
 - optional run log paths.
 
+<<<<<<< HEAD
 `recommended_action` is local project state, not a public artifact by default:
 it may include private project refs such as todo ids, branch names, local
 aliases, or operator-private routing labels. It must not include AK/SK values,
@@ -417,17 +437,27 @@ checks, transfer, and compare-and-swap behavior. Hard leases remain keyed by
 `(goal_id, todo_id)`, so unrelated todos under the same goal can still run in
 parallel when scopes permit.
 
+=======
+By default it should be read-only. Launching jobs, stopping jobs, syncing docs,
+or editing production state requires explicit user approval.
+
+>>>>>>> 7dcdc9dc7 (Initial public goal harness scaffold)
 ## Shared Runtime
 
 All adapters should save compact run history under:
 
 ```text
+<<<<<<< HEAD
 ~/.loopx/goals/<goal-id>/runs/index.jsonl
+=======
+~/.codex/goal-harness/goals/<goal-id>/runs/index.jsonl
+>>>>>>> 7dcdc9dc7 (Initial public goal harness scaffold)
 ```
 
 This gives the app, CLI, heartbeats, and future UI one place to inspect goal
 history.
 
+<<<<<<< HEAD
 Project-local registries should also sync into the shared global registry:
 
 ```text
@@ -698,15 +728,21 @@ the [status data contract](status-data-contract.md).
 Keep adapter output sanitized before it enters the compact index. The status
 queue is meant for control-plane display, not for raw private evidence.
 
+=======
+>>>>>>> 7dcdc9dc7 (Initial public goal harness scaffold)
 ## Public Repo vs Project Repo
 
 Put generic code here:
 
 - registry and history readers,
 - contract checker,
 - generic schema and docs,
+<<<<<<< HEAD
 - sanitized adapter examples,
 - peer task and ephemeral worker lifecycle examples.
+=======
+- sanitized adapter examples.
+>>>>>>> 7dcdc9dc7 (Initial public goal harness scaffold)
 
 Keep in the project repo:
 
@@ -715,5 +751,9 @@ Keep in the project repo:
 - private registry,
 - domain-specific health checks.
 
+<<<<<<< HEAD
 This split lets many local projects share one stable LoopX base while
+=======
+This split lets many local projects share one stable Goal Harness base while
+>>>>>>> 7dcdc9dc7 (Initial public goal harness scaffold)
 keeping their real evidence and safety policies local.