feat(things): add status and doctor runtime truth #740

Merged
pdurlej merged 1 commit from codex/things-wave-3-status-doctor into main 2026-06-07 16:59:15 +02:00
Collaborator

Summary

  • add status-json for fast local runtime truth about the Things bridge
  • add doctor-json with an optional tiny read-only live Things Cloud probe
  • record latest read/proposal/preview/apply/result runtime state so Piotr and Iskra have one status surface
  • document status/doctor usage in the bridge docs, OpenClaw skill, and VPS1000 wrapper help

BMADX wave

Wave 3 - Status / Doctor / Runtime Truth.

Verification

  • pytest -q tests/test_iskra_things_sync_contract.py
  • python3 -m py_compile scripts/iskra-things-sync/iskra_things_sync.py
  • bash -n scripts/iskra-things-sync/iskra-things-vps1000
  • git diff --check

What Iskra can do now

  • answer whether the Things bridge is healthy with iskra-things status-json
  • run iskra-things doctor-json for a read-only live SDK probe
  • distinguish live Things read health from Signal delivery and Obsidian cache state

Still cannot do

  • no new mutation path; writes remain behind digest-bound approvals
  • no Wloczykij promotion flow yet
  • no honest partial-search metadata or human title validator yet; that is Wave 4
## Summary - add `status-json` for fast local runtime truth about the Things bridge - add `doctor-json` with an optional tiny read-only live Things Cloud probe - record latest read/proposal/preview/apply/result runtime state so Piotr and Iskra have one status surface - document status/doctor usage in the bridge docs, OpenClaw skill, and VPS1000 wrapper help ## BMADX wave Wave 3 - Status / Doctor / Runtime Truth. ## Verification - `pytest -q tests/test_iskra_things_sync_contract.py` - `python3 -m py_compile scripts/iskra-things-sync/iskra_things_sync.py` - `bash -n scripts/iskra-things-sync/iskra-things-vps1000` - `git diff --check` ## What Iskra can do now - answer whether the Things bridge is healthy with `iskra-things status-json` - run `iskra-things doctor-json` for a read-only live SDK probe - distinguish live Things read health from Signal delivery and Obsidian cache state ## Still cannot do - no new mutation path; writes remain behind digest-bound approvals - no Wloczykij promotion flow yet - no honest partial-search metadata or human title validator yet; that is Wave 4
feat(things): add status and doctor runtime truth
All checks were successful
base-is-main / guard (pull_request) Successful in 1s
canary-required / collect-diff (pull_request) Successful in 4s
python-ci / Python 3.12 (pull_request) Successful in 43s
patchwarden-pr-sanity / sanity (pull_request) Successful in 4m18s
patchwarden-client-dry-run / collect-diff (pull_request) Successful in 3s
patchwarden-pr-sanity / collect-diff (pull_request) Successful in 3s
python-ci / Python 3.11 (pull_request) Successful in 43s
python-ci / Python 3.13 (pull_request) Successful in 42s
canary-required / canary (pull_request) Successful in 13s
patchwarden-client-dry-run / dry-run (pull_request) Successful in 17s
5521f85acf
First-time contributor

Patchwarden PR sanity

  • Status: advisory_findings
  • PR: 740
  • Commit: 5521f85acf05ab3e021cf067b109c1830558d533
  • Security-sensitive label: missing
  • Authority: advisory model review plus deterministic blockers only
  • 3+3 canary: still alive; this does not replace it

Deterministic findings

No deterministic findings.

Model reviewers

global-glm / glm-5.1:cloud

  • Status: ok

  • Verdict: ABSTAIN

  • medium reviewer output unparseable

    • Evidence: no valid JSON object found in response
    • Next: investigate provider response; possibly increase max_tokens or retry

global-deepseek / deepseek-v4-pro:cloud

  • Status: ok

  • Verdict: OK

  • medium Potential state directory mismatch between write and read paths

    • Evidence: scripts/iskra-things-sync/iskra_things_sync.py: try_write_runtime_statewrites tostate_dir() / name(viaruntime_state_path), while read_runtime_statereads fromconfigured_state_dir() / name. If state_dir()andconfigured_sta`
    • Next: Confirm that state_dir() and configured_state_dir() are identical (both default to /state and respect ISKRA_THINGS_STATE_DIR). If they are, remove the duplicate function to avoid confusion; if not, align them to use the same directory.

redteam / kimi-k2.6:cloud

  • Status: ok

  • Verdict: NOT_OK

  • high doctor-json live probe crashes on unexpected SDK exceptions

    • Evidence: scripts/iskra-things-sync/iskra_things_sync.py status_payload() wraps the live probe (collect_snapshot) in except SystemExit as exc only; any network, auth, or runtime exception from the Things SDK will propagate uncaught, causing doctor-
    • Next: Change the handler to except Exception as exc: so doctor-json always emits JSON and returns exit code 2 when the live probe fails for any reason.

Policy notes

  • GLM 5.1 + DeepSeek V4 Pro are the operator-required model mix for this bot.
  • Optional red-team model is enabled only when PLATFORMCTL_PR_SANITY_REDTEAM_MODEL is configured.
  • Auto-merge is not enabled here.
<!-- patchwarden-pr-sanity:pdurlej/platform:PR-740 --> # Patchwarden PR sanity - Status: `advisory_findings` - PR: `740` - Commit: `5521f85acf05ab3e021cf067b109c1830558d533` - Security-sensitive label: `missing` - Authority: advisory model review plus deterministic blockers only - 3+3 canary: still alive; this does not replace it ## Deterministic findings No deterministic findings. ## Model reviewers ### `global-glm` / `glm-5.1:cloud` - Status: `ok` - Verdict: `ABSTAIN` - **`medium`** reviewer output unparseable - Evidence: `no valid JSON object found in response` - Next: investigate provider response; possibly increase max_tokens or retry ### `global-deepseek` / `deepseek-v4-pro:cloud` - Status: `ok` - Verdict: `OK` - **`medium`** Potential state directory mismatch between write and read paths - Evidence: `scripts/iskra-things-sync/iskra_things_sync.py: `try_write_runtime_state` writes to `state_dir() / name` (via `runtime_state_path`), while `read_runtime_state` reads from `configured_state_dir() / name`. If `state_dir()` and `configured_sta` - Next: Confirm that `state_dir()` and `configured_state_dir()` are identical (both default to `/state` and respect `ISKRA_THINGS_STATE_DIR`). If they are, remove the duplicate function to avoid confusion; if not, align them to use the same directory. ### `redteam` / `kimi-k2.6:cloud` - Status: `ok` - Verdict: `NOT_OK` - **`high`** doctor-json live probe crashes on unexpected SDK exceptions - Evidence: `scripts/iskra-things-sync/iskra_things_sync.py status_payload() wraps the live probe (collect_snapshot) in `except SystemExit as exc` only; any network, auth, or runtime exception from the Things SDK will propagate uncaught, causing doctor-` - Next: Change the handler to `except Exception as exc:` so doctor-json always emits JSON and returns exit code 2 when the live probe fails for any reason. ## Policy notes - GLM 5.1 + DeepSeek V4 Pro are the operator-required model mix for this bot. - Optional red-team model is enabled only when `PLATFORMCTL_PR_SANITY_REDTEAM_MODEL` is configured. - Auto-merge is not enabled here.
pdurlej deleted branch codex/things-wave-3-status-doctor 2026-06-07 16:59:15 +02:00
Sign in to join this conversation.
No reviewers
No labels
W6d-automerge-calibration
agent/claude-code
agent/codex
agent/hermes
agent/iskra
agent/ollama
agent/patchwarden
automerge-candidate
class/security-sensitive
cutover-gate
dependency/blocked
dependency/blocks-others
dependency/cross-repo
dependency/needs-confirmation
domain:agents
domain:ci
domain:docs
domain:forgejo
domain:infra
domain:memory
domain:runtime
domain:signal
domain:ux
flow/architecture
flow/blocked
flow/deployed
flow/done
flow/implementation
flow/intake
flow/maintained
flow/observed
flow/ready
flow/refining
flow/retired
flow/review
iterating
judge/codex-candidate
judge/hermes-candidate
judge/low-confidence
judge/needs-refinement
judge/operator-needed
judge/p0
judge/p1
judge/p2
judge/p3
judge/park
judge/patchwarden-candidate
judge/stale-priority
kind/adr
kind/bug
kind/chore
kind/feature
kind/infra
kind/ops
kind/refactor
kind/research
large-impact
merge/auto
merge/manual
merge/manual-dependency-conflict
merge/manual-failing-tests
merge/manual-merge-conflict
merge/manual-missing-review
merge/manual-operator-preference
merge/manual-red-zone
merge/manual-security-sensitive
merge/manual-unclear-scope
merge/manual-unknown
meta
mode:operator-only
mode:patchwarden-iskra-approved
mode:safe-auto
needs-operator-decision
needs-triage
not-ready
observed/erroring
observed/needs-followup
observed/pending
observed/retire-candidate
observed/unused
observed/used
operator-emotional
owner-attention
phase/02
phase/03
priority:p0
priority:p1
priority:p2
priority:p3
proposed
ready-for-agent
ready-for-operator
recovery
review:claude-reviewed
review:codex-reviewed
review:dziadek-reviewed
review:needs-human
risk/exposure
risk/process
risk/product
risk/runtime
safety:external-write
safety:no-prod-mutation
safety:prod-impact
safety:secret-touch
size/large
size/medium
size/small
size/tiny
size/unknown
source/adr
source/agent-generated
source/manual
source/operator-chat
source/voice-note
status:blocked
status:codex-ready
status:merged:pending-evidence
status:needs-evidence
status:operator-needed
status:parked
tier/full
tier/lite
tier/stacked
tier:0-platform-substrate
tier:1-iskra-value-layer
tier:2-tools-products-modules
type:bug
type:chore
type:docs
type:feat
type:policy
type:research
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
pdurlej/platform!740
No description provided.