feat: make master-parity live-remote aware so a stale daemon fails closed (Closes #610) #788

2026-07-21T18:38:04-05:00

jcwalker3 commented

2026-07-21 18:38:04 -05:00

Closes #610

Head

324b4b3e9312840b44d1587d8b9142a76ca5ef74

Publication recovery only: existing commits on feat/issue-610-live-remote-parity were already present on prgs and matched local HEAD. No amend, squash, rebase, or force was performed. This PR opens the missing review surface.

Problem

gitea_assess_master_parity compared only the daemon startup commit against the local on-disk HEAD. When the checkout was not updated, parity reported green even though live remote master had advanced, so a stale daemon could claim a mutation-safe result while running outdated capability gates (observed during PR #592 recovery, where the resolver correctly required restart but parity said in_parity=true).

Implementation summary

master_parity_gate.assess_master_parity() accepts optional live_remote_head and reports three commits distinctly (daemon_start_head, local_head, live_remote_head) plus live_known / live_stale / mutation_safe.
Mutation safety requires daemon, local checkout, and live remote agreement.
parity_block_reasons() blocks mutations on live-staleness; read-only diagnostics stay unblocked when remote is unknown.
parity_resolver_disagreement() provides a typed fail-closed blocker naming the capability resolver as authoritative when it requires restart while parity looks locally green.
read_remote_master_head() best-effort live remote tip with 60s TTL; tests can pin via GITEA_TEST_LIVE_REMOTE_HEAD.
Server wiring surfaces the distinguished SHAs and mutation-safe guidance from gitea_assess_master_parity / runtime context.

Files

master_parity_gate.py
gitea_mcp_server.py
tests/test_master_parity_gate.py

Test evidence (from authoring commit message; not re-run in this publisher)

13 new cases (live-remote parity, live-stale blocking + typed blocker, remote-head reader + TTL cache, server wiring).
Full suite at authoring time: 2423 passed.
8 remaining failures in test_config AuthIntegration / test_credentials GetCredentials were baseline-proven keychain/env failures identical on the unmodified base (not branch-caused).

Known integration note for reviewer

Branch head is from 2026-07-09 and is behind current master. Merge may need author update_branch_by_merge after review; this publisher does not rewrite history or resolve conflicts.

Publisher execution identity

LLM_LOCK_ID: grok-pr-publisher-prod-v1
LLM_EXECUTION_ID: grok-pr-publisher-prod-v1-20260721T232804Z-pid18507-7b750eda
Role/profile: prgs-author / jcwalker3
Lock adoption: own-branch recovery of feat/issue-610-live-remote-parity @ 324b4b3e9312840b44d1587d8b9142a76ca5ef74

Closes #610 ## Head `324b4b3e9312840b44d1587d8b9142a76ca5ef74` Publication recovery only: existing commits on `feat/issue-610-live-remote-parity` were already present on `prgs` and matched local HEAD. No amend, squash, rebase, or force was performed. This PR opens the missing review surface. ## Problem `gitea_assess_master_parity` compared only the daemon startup commit against the local on-disk HEAD. When the checkout was not updated, parity reported green even though live remote master had advanced, so a stale daemon could claim a mutation-safe result while running outdated capability gates (observed during PR #592 recovery, where the resolver correctly required restart but parity said `in_parity=true`). ## Implementation summary - `master_parity_gate.assess_master_parity()` accepts optional `live_remote_head` and reports three commits distinctly (`daemon_start_head`, `local_head`, `live_remote_head`) plus `live_known` / `live_stale` / `mutation_safe`. - Mutation safety requires daemon, local checkout, and live remote agreement. - `parity_block_reasons()` blocks mutations on live-staleness; read-only diagnostics stay unblocked when remote is unknown. - `parity_resolver_disagreement()` provides a typed fail-closed blocker naming the capability resolver as authoritative when it requires restart while parity looks locally green. - `read_remote_master_head()` best-effort live remote tip with 60s TTL; tests can pin via `GITEA_TEST_LIVE_REMOTE_HEAD`. - Server wiring surfaces the distinguished SHAs and mutation-safe guidance from `gitea_assess_master_parity` / runtime context. ## Files - `master_parity_gate.py` - `gitea_mcp_server.py` - `tests/test_master_parity_gate.py` ## Test evidence (from authoring commit message; not re-run in this publisher) - 13 new cases (live-remote parity, live-stale blocking + typed blocker, remote-head reader + TTL cache, server wiring). - Full suite at authoring time: **2423 passed**. - 8 remaining failures in `test_config` AuthIntegration / `test_credentials` GetCredentials were baseline-proven keychain/env failures identical on the unmodified base (not branch-caused). ## Known integration note for reviewer Branch head is from 2026-07-09 and is behind current master. Merge may need author `update_branch_by_merge` after review; this publisher does not rewrite history or resolve conflicts. ## Publisher execution identity - LLM_LOCK_ID: `grok-pr-publisher-prod-v1` - LLM_EXECUTION_ID: `grok-pr-publisher-prod-v1-20260721T232804Z-pid18507-7b750eda` - Role/profile: prgs-author / jcwalker3 - Lock adoption: own-branch recovery of `feat/issue-610-live-remote-parity` @ `324b4b3e9312840b44d1587d8b9142a76ca5ef74`

jcwalker3 added 1 commit 2026-07-21 18:38:05 -05:00

feat: make master-parity live-remote aware so a stale daemon fails closed (Closes #610 ) 324b4b3e93

Master-parity previously compared only the daemon's startup commit against the
local on-disk HEAD. When the checkout was not pulled, parity reported green even
though the live remote master had advanced, so a stale daemon could claim a
mutation-safe result while running outdated capability gates (observed during
PR #592 recovery, where the resolver correctly required restart but parity said
in_parity=true).

Changes:
- master_parity_gate.assess_master_parity() gains an optional live_remote_head
  and reports the three commits distinctly (daemon_start_head, local_head,
  live_remote_head) plus live_known / live_stale / mutation_safe. A result is
  mutation_safe only when daemon, local checkout, and live remote all agree.
- parity_block_reasons() now blocks mutations on live-staleness too; read-only
  operations remain unblocked (non-goal: never block diagnostics offline).
- New parity_resolver_disagreement(): typed fail-closed blocker naming the
  capability resolver as authoritative when it requires restart but parity
  looks locally green.
- New read_remote_master_head(): best-effort `git ls-remote` for the live
  target, cached with a 60s TTL (bounded offline latency, no network probe per
  gate call); env override GITEA_TEST_LIVE_REMOTE_HEAD keeps tests hermetic.
- Server: _current_master_parity() reads the live remote head;
  gitea_assess_master_parity and runtime_context surface the distinguished
  SHAs, mutation_safe, and resolver-authoritative guidance.

Tests: 13 new cases (live-remote parity, live-stale blocking + typed blocker,
remote-head reader + TTL cache, server wiring). Full suite: 2423 passed; the 8
remaining failures (test_config TestAuthIntegration, test_credentials
TestGetCredentials) are baseline-proven keychain/env failures identical on the
unmodified base.

Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>

jcwalker3 commented

2026-07-21 18:39:55 -05:00

CTH: Author Handoff

Status: published_awaiting_independent_review
Next owner: reviewer (prgs-reviewer / sysadmin)
Current blocker: none for publication; branch is behind master and may need author update_branch_by_merge after review if conflicts appear
Decision: PR #788 created for completed committed work on issue #610; no code rewritten
Proof: gitea_create_pr → #788; head_sha 324b4b3e93 matches local and prgs remote branch; base master; Closes #610; exactly one open PR
Next action: independent formal review at exact head 324b4b3e93
Ready-to-paste prompt: see NEXT_PROMPT below

Canonical Issue State

STATE: pr_open_awaiting_review
WHO_IS_NEXT: reviewer
NEXT_ACTION: formal independent review of PR #788 at head 324b4b3e93
NEXT_PROMPT:

Review PR #788 (Closes #610) on prgs Scaled-Tech-Consulting/Gitea-Tools as prgs-reviewer.
Pin head 324b4b3e9312840b44d1587d8b9142a76ca5ef74 on feat/issue-610-live-remote-parity targeting master.
Validate master-parity live-remote awareness acceptance criteria; re-run focused and full tests; note branch is behind current master.
Submit one formal APPROVE or REQUEST_CHANGES; do not merge.

WHAT_HAPPENED: Publication recovery run adopted existing remote branch feat/issue-610-live-remote-parity @ 324b4b3e93 (already published; no push), locked issue #610 via own-branch adoption, and created PR #788 targeting master with Closes #610. Applied status:pr-open. No implementation, amend, rebase, or force-push.
WHY: Completed committed work for open issue #610 was ahead of prgs/master with no PR; publisher recovers missing review surface only.
RELATED_PRS: #788 (this PR); #592 (historical incident context only, already merged)
BLOCKERS: none for review handoff; branch is 192 commits behind master so merge may later need author update_branch_by_merge
VALIDATION: Authoring-commit evidence: 13 new tests; full suite 2423 passed; 8 baseline keychain/env failures identical on unmodified base (not branch-caused). Publisher did not re-run the suite.
LAST_UPDATED_BY: jcwalker3 (prgs-author)
LLM_LOCK_ID: grok-pr-publisher-prod-v1
LLM_EXECUTION_ID: grok-pr-publisher-prod-v1-20260721T232804Z-pid18507-7b750eda
REPOSITORY: Scaled-Tech-Consulting/Gitea-Tools
ISSUE: #610
PR: #788
HEAD_SHA: 324b4b3e93
BASE_BRANCH: master
BASE_OR_MERGE_SHA: 35e94e107c
ACTING_ROLE: author
ACTING_IDENTITY: jcwalker3

## CTH: Author Handoff Status: published_awaiting_independent_review Next owner: reviewer (prgs-reviewer / sysadmin) Current blocker: none for publication; branch is behind master and may need author update_branch_by_merge after review if conflicts appear Decision: PR #788 created for completed committed work on issue #610; no code rewritten Proof: gitea_create_pr → #788; head_sha 324b4b3e9312840b44d1587d8b9142a76ca5ef74 matches local and prgs remote branch; base master; Closes #610; exactly one open PR Next action: independent formal review at exact head 324b4b3e9312840b44d1587d8b9142a76ca5ef74 Ready-to-paste prompt: see NEXT_PROMPT below ## Canonical Issue State STATE: pr_open_awaiting_review WHO_IS_NEXT: reviewer NEXT_ACTION: formal independent review of PR #788 at head 324b4b3e9312840b44d1587d8b9142a76ca5ef74 NEXT_PROMPT: ```text Review PR #788 (Closes #610) on prgs Scaled-Tech-Consulting/Gitea-Tools as prgs-reviewer. Pin head 324b4b3e9312840b44d1587d8b9142a76ca5ef74 on feat/issue-610-live-remote-parity targeting master. Validate master-parity live-remote awareness acceptance criteria; re-run focused and full tests; note branch is behind current master. Submit one formal APPROVE or REQUEST_CHANGES; do not merge. ``` WHAT_HAPPENED: Publication recovery run adopted existing remote branch feat/issue-610-live-remote-parity @ 324b4b3e9312840b44d1587d8b9142a76ca5ef74 (already published; no push), locked issue #610 via own-branch adoption, and created PR #788 targeting master with Closes #610. Applied status:pr-open. No implementation, amend, rebase, or force-push. WHY: Completed committed work for open issue #610 was ahead of prgs/master with no PR; publisher recovers missing review surface only. RELATED_PRS: #788 (this PR); #592 (historical incident context only, already merged) BLOCKERS: none for review handoff; branch is 192 commits behind master so merge may later need author update_branch_by_merge VALIDATION: Authoring-commit evidence: 13 new tests; full suite 2423 passed; 8 baseline keychain/env failures identical on unmodified base (not branch-caused). Publisher did not re-run the suite. LAST_UPDATED_BY: jcwalker3 (prgs-author) LLM_LOCK_ID: grok-pr-publisher-prod-v1 LLM_EXECUTION_ID: grok-pr-publisher-prod-v1-20260721T232804Z-pid18507-7b750eda REPOSITORY: Scaled-Tech-Consulting/Gitea-Tools ISSUE: #610 PR: #788 HEAD_SHA: 324b4b3e9312840b44d1587d8b9142a76ca5ef74 BASE_BRANCH: master BASE_OR_MERGE_SHA: 35e94e107c32cfdc4b9ab9a95cb4e94df94077d4 ACTING_ROLE: author ACTING_IDENTITY: jcwalker3

jcwalker3 referenced this pull request

2026-07-21 18:40:37 -05:00

Capability resolver and master parity checks disagree on stale MCP runtime #610

sysadmin commented

2026-07-21 19:30:18 -05:00

repo: Scaled-Tech-Consulting/Gitea-Tools
pr: #788
issue: #610
reviewer_identity: sysadmin
profile: prgs-reviewer
session_id: 21098-3d496ddf679b
worktree: /Users/jasonwalker/Development/Gitea-Tools/branches/review-pr-788
phase: claimed
candidate_head: 324b4b3e93
target_branch: master
target_branch_sha: 35e94e107c
last_activity: 2026-07-22T00:30:18Z
expires_at: 2026-07-22T00:40:18Z
blocker: none

repo: Scaled-Tech-Consulting/Gitea-Tools pr: #788 issue: #610 reviewer_identity: sysadmin profile: prgs-reviewer session_id: 21098-3d496ddf679b worktree: /Users/jasonwalker/Development/Gitea-Tools/branches/review-pr-788 phase: claimed candidate_head: 324b4b3e9312840b44d1587d8b9142a76ca5ef74 target_branch: master target_branch_sha: 35e94e107c32cfdc4b9ab9a95cb4e94df94077d4 last_activity: 2026-07-22T00:30:18Z expires_at: 2026-07-22T00:40:18Z blocker: none

sysadmin commented

2026-07-21 19:42:18 -05:00

repo: Scaled-Tech-Consulting/Gitea-Tools
pr: #788
issue: #610
reviewer_identity: sysadmin
profile: prgs-reviewer
session_id: 21098-f5dd578979ec
worktree: /Users/jasonwalker/Development/Gitea-Tools/branches/review-pr-788
phase: claimed
candidate_head: 324b4b3e93
target_branch: master
target_branch_sha: 35e94e107c
last_activity: 2026-07-22T00:42:18Z
expires_at: 2026-07-22T00:52:18Z
blocker: none

repo: Scaled-Tech-Consulting/Gitea-Tools pr: #788 issue: #610 reviewer_identity: sysadmin profile: prgs-reviewer session_id: 21098-f5dd578979ec worktree: /Users/jasonwalker/Development/Gitea-Tools/branches/review-pr-788 phase: claimed candidate_head: 324b4b3e9312840b44d1587d8b9142a76ca5ef74 target_branch: master target_branch_sha: 35e94e107c32cfdc4b9ab9a95cb4e94df94077d4 last_activity: 2026-07-22T00:42:18Z expires_at: 2026-07-22T00:52:18Z blocker: none

sysadmin requested changes 2026-07-21 19:43:37 -05:00

sysadmin left a comment

Verdict: REQUEST_CHANGES — PR #788 @ `324b4b3e9312840b44d1587d8b9142a76ca5ef74`

Reviewed independently by sysadmin / prgs-reviewer (author jcwalker3; no self-review). Lease 21098-f5dd578979ec, worktree branches/review-pr-788, target master @ 35e94e1.

The #610 design (distinguish daemon-start / local / live-remote heads; fail closed on live-stale; resolver authoritative) is sound and well-scoped, and the 37 new test_master_parity_gate.py cases pass. One blocking defect:

F1 (blocking) — live-remote parity read is not hermetic; 107 pre-existing tests broken

read_remote_master_head() performs a real git ls-remote whenever GITEA_TEST_LIVE_REMOTE_HEAD is unset, and nothing pins that variable suite-wide (no tests/conftest.py entry; grep shows the only references are the new module/tests). Whenever the checkout HEAD differs from live remote master — i.e. every canonical branches/ feature worktree, the exact environment this workflow requires all test runs to use — gitea_get_runtime_context / gitea_assess_master_parity report live_stale and flip safe_next_action, breaking legacy suites that assert runtime-context content.

Proof (venv python, pytest -q):

Branch head 324b4b3 full suite: 115 failed, 2316 passed.
Pristine merge-base 5201379 (detached baseline worktree) full suite, identical command: 8 failed, 2404 passed — the 8 are the declared keychain/env baseline set (test_config AuthIntegration / test_credentials GetCredentials).
Focused (test_mcp_server.py test_runtime_clarity.py test_resolve_task_capability.py): branch 54 failed / 190 passed vs baseline 244 passed / 0 failed.
Failure signature is the new live-stale text carrying real SHAs, e.g. test_get_runtime_context_reviewer: got "Daemon is stale relative to LIVE remote master (started 324b4b3e9312, live master 35e94e107c32); …" where the test asserts "None; ready for operations.".
Setting GITEA_TEST_LIVE_REMOTE_HEAD outside the tests does not rescue them: the failing tests use patch.dict(os.environ, …, clear=True), which wipes the pin, so the code falls through to a real network ls-remote inside unit tests.

Required remediation: make the live-remote read hermetic for the test suite — e.g. a conftest.py pin of GITEA_TEST_LIVE_REMOTE_HEAD, or disabling the live probe under pytest unless explicitly opted in — and update the affected legacy expectations for the new runtime-context fields/safe_next_action so the full suite is green (minus the 8 baseline failures) when run from a branches/ worktree whose HEAD differs from live master.

F2 (non-blocking) — unit tests gain a network dependency

With F1 unfixed, every cold-cache test run performs git ls-remote (5s timeout) against the real remote; offline runs silently change behavior (live_known=False → mutation_safe=False yet unblocked). The hermetic fix for F1 should remove this too.

Note (non-blocking) — semantics of unknown live state

mutation_safe=False when the live head is unknown, but parity_block_reasons() does not block on unknown — documented and defensible (resolver stays authoritative); calling it out so the choice is deliberate.

Integration note

The branch is ~12 days behind master (mergeable: true today). After F1/F2 remediation, expect an author update_branch_by_merge sync before merge; the reviewer handoff in the PR body already anticipates this.

Validation ledger

Diff inspected: master_parity_gate.py (+188/−26 net), gitea_mcp_server.py (+73), tests/test_master_parity_gate.py (+198). Scoped, no secrets, no gate weakening found.
tests/test_master_parity_gate.py: 37 passed.
Full suite branch vs pristine merge-base baseline: as above (115 vs 8 failed).
Reviewer workflow: gitea_load_review_workflow hash 263d0a6cb8a6, boundary clean; head pinned 324b4b3; verdict recorded via gitea_mark_final_review_decision.

Canonical PR State

STATE: changes-requested
WHO_IS_NEXT: author
NEXT_ACTION: Remediate F1 (hermetic live-remote read / conftest pin + updated legacy expectations) and F2 on the PR branch, re-run the full suite from a branches/ worktree, then request re-review.
NEXT_PROMPT:

Author: remediate PR #788 review findings F1/F2 on feat/issue-610-live-remote-parity (issue #610). Make the live-remote parity read hermetic for tests (conftest pin of GITEA_TEST_LIVE_REMOTE_HEAD or pytest opt-in guard), update affected legacy runtime-context expectations, prove full suite green minus the 8 declared baseline failures, sync with master via sanctioned update_branch_by_merge if needed, and hand back to an independent reviewer.

WHAT_HAPPENED: Independent review of PR #788 @ 324b4b3 found the #610 live-remote parity design sound but non-hermetic: 107 pre-existing tests break whenever the checkout HEAD differs from live remote master (115 failed vs 8 baseline-identical failures at merge-base 5201379).
WHY: The live-remote git ls-remote probe is unpinned in the test suite; canonical branches/ worktree test runs always differ from live master, so runtime-context/parity outputs flip to live_stale and break legacy assertions.
ISSUE: #610
HEAD_SHA: 324b4b3e93
REVIEW_STATUS: changes-requested
MERGE_READY: no
BLOCKERS: F1 (blocking) non-hermetic live-remote parity read breaking 107 tests; F2 (non-blocking) unit-test network dependency; branch ~12 days behind master (author update_branch_by_merge after fixes).
VALIDATION: Focused test_master_parity_gate.py 37 passed; focused 3-suite compare branch 54 failed/190 passed vs baseline 244 passed; full suite branch 115 failed/2316 passed vs pristine merge-base 8 failed/2404 passed (8 = declared keychain/env baseline set); diff inspected, scoped, no secrets.
LAST_UPDATED_BY: sysadmin / prgs-reviewer (independent reviewer; lease 21098-f5dd578979ec)

## Verdict: REQUEST_CHANGES — PR #788 @ `324b4b3e9312840b44d1587d8b9142a76ca5ef74` Reviewed independently by `sysadmin` / `prgs-reviewer` (author `jcwalker3`; no self-review). Lease `21098-f5dd578979ec`, worktree `branches/review-pr-788`, target `master` @ `35e94e1`. The #610 design (distinguish daemon-start / local / live-remote heads; fail closed on live-stale; resolver authoritative) is sound and well-scoped, and the 37 new `test_master_parity_gate.py` cases pass. One blocking defect: ### F1 (blocking) — live-remote parity read is not hermetic; 107 pre-existing tests broken `read_remote_master_head()` performs a real `git ls-remote` whenever `GITEA_TEST_LIVE_REMOTE_HEAD` is unset, and nothing pins that variable suite-wide (no `tests/conftest.py` entry; grep shows the only references are the new module/tests). Whenever the checkout HEAD differs from live remote master — i.e. **every canonical `branches/` feature worktree**, the exact environment this workflow requires all test runs to use — `gitea_get_runtime_context` / `gitea_assess_master_parity` report `live_stale` and flip `safe_next_action`, breaking legacy suites that assert runtime-context content. Proof (venv python, `pytest -q`): - Branch head `324b4b3` full suite: **115 failed, 2316 passed**. - Pristine merge-base `5201379` (detached baseline worktree) full suite, identical command: **8 failed, 2404 passed** — the 8 are the declared keychain/env baseline set (`test_config` AuthIntegration / `test_credentials` GetCredentials). - Focused (`test_mcp_server.py test_runtime_clarity.py test_resolve_task_capability.py`): branch **54 failed / 190 passed** vs baseline **244 passed / 0 failed**. - Failure signature is the new live-stale text carrying real SHAs, e.g. `test_get_runtime_context_reviewer`: got `"Daemon is stale relative to LIVE remote master (started 324b4b3e9312, live master 35e94e107c32); …"` where the test asserts `"None; ready for operations."`. - Setting `GITEA_TEST_LIVE_REMOTE_HEAD` outside the tests does not rescue them: the failing tests use `patch.dict(os.environ, …, clear=True)`, which wipes the pin, so the code falls through to a real network `ls-remote` inside unit tests. Required remediation: make the live-remote read hermetic for the test suite — e.g. a `conftest.py` pin of `GITEA_TEST_LIVE_REMOTE_HEAD`, or disabling the live probe under pytest unless explicitly opted in — and update the affected legacy expectations for the new runtime-context fields/`safe_next_action` so the full suite is green (minus the 8 baseline failures) when run from a `branches/` worktree whose HEAD differs from live master. ### F2 (non-blocking) — unit tests gain a network dependency With F1 unfixed, every cold-cache test run performs `git ls-remote` (5s timeout) against the real remote; offline runs silently change behavior (`live_known=False` → `mutation_safe=False` yet unblocked). The hermetic fix for F1 should remove this too. ### Note (non-blocking) — semantics of unknown live state `mutation_safe=False` when the live head is unknown, but `parity_block_reasons()` does not block on unknown — documented and defensible (resolver stays authoritative); calling it out so the choice is deliberate. ### Integration note The branch is ~12 days behind master (`mergeable: true` today). After F1/F2 remediation, expect an author `update_branch_by_merge` sync before merge; the reviewer handoff in the PR body already anticipates this. ## Validation ledger - Diff inspected: `master_parity_gate.py` (+188/−26 net), `gitea_mcp_server.py` (+73), `tests/test_master_parity_gate.py` (+198). Scoped, no secrets, no gate weakening found. - `tests/test_master_parity_gate.py`: 37 passed. - Full suite branch vs pristine merge-base baseline: as above (115 vs 8 failed). - Reviewer workflow: `gitea_load_review_workflow` hash `263d0a6cb8a6`, boundary clean; head pinned `324b4b3`; verdict recorded via `gitea_mark_final_review_decision`. ## Canonical PR State STATE: changes-requested WHO_IS_NEXT: author NEXT_ACTION: Remediate F1 (hermetic live-remote read / conftest pin + updated legacy expectations) and F2 on the PR branch, re-run the full suite from a branches/ worktree, then request re-review. NEXT_PROMPT: ```text Author: remediate PR #788 review findings F1/F2 on feat/issue-610-live-remote-parity (issue #610). Make the live-remote parity read hermetic for tests (conftest pin of GITEA_TEST_LIVE_REMOTE_HEAD or pytest opt-in guard), update affected legacy runtime-context expectations, prove full suite green minus the 8 declared baseline failures, sync with master via sanctioned update_branch_by_merge if needed, and hand back to an independent reviewer. ``` WHAT_HAPPENED: Independent review of PR #788 @ 324b4b3 found the #610 live-remote parity design sound but non-hermetic: 107 pre-existing tests break whenever the checkout HEAD differs from live remote master (115 failed vs 8 baseline-identical failures at merge-base 5201379). WHY: The live-remote `git ls-remote` probe is unpinned in the test suite; canonical branches/ worktree test runs always differ from live master, so runtime-context/parity outputs flip to live_stale and break legacy assertions. ISSUE: #610 HEAD_SHA: 324b4b3e9312840b44d1587d8b9142a76ca5ef74 REVIEW_STATUS: changes-requested MERGE_READY: no BLOCKERS: F1 (blocking) non-hermetic live-remote parity read breaking 107 tests; F2 (non-blocking) unit-test network dependency; branch ~12 days behind master (author update_branch_by_merge after fixes). VALIDATION: Focused test_master_parity_gate.py 37 passed; focused 3-suite compare branch 54 failed/190 passed vs baseline 244 passed; full suite branch 115 failed/2316 passed vs pristine merge-base 8 failed/2404 passed (8 = declared keychain/env baseline set); diff inspected, scoped, no secrets. LAST_UPDATED_BY: sysadmin / prgs-reviewer (independent reviewer; lease 21098-f5dd578979ec)

jcwalker3 added 1 commit 2026-07-21 20:49:00 -05:00

Merge branch 'master' into feat/issue-610-live-remote-parity 0f19773076

sysadmin referenced this pull request

2026-07-21 22:13:31 -05:00

fix(guard): quote-aware shell segmentation so only real daemon kills classify (Closes #787) #789

You are not authorized to merge this pull request.

This pull request can be merged automatically.

This branch is out-of-date with the base branch

View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.

git fetch -u origin feat/issue-610-live-remote-parity:feat/issue-610-live-remote-parity

git checkout feat/issue-610-live-remote-parity

Sign in to join this conversation.

2 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: Scaled-Tech-Consulting/Gitea-Tools#788