docs: close independent sync work and retain gated publication tasks
This commit is contained in:
codex
parent
ed93d0b21f
commit
450fad9ee9
2 changed files with 36 additions and 12 deletions
|
|
@ -83,7 +83,7 @@
|
|||
| workplan | CUST-WP-0080 | finished | — | workplans/CUST-WP-0080-netkingdom-security-blueprint-and-gap-closure.md |
|
||||
| workplan | CUST-WP-0081 | finished | — | workplans/CUST-WP-0081-netkingdom-architecture-review-and-reuse.md |
|
||||
| workplan | CUST-WP-0082 | backlog | — | workplans/CUST-WP-0082-netkingdom-security-hardening.md |
|
||||
| workplan | CUST-WP-0083 | active | — | workplans/CUST-WP-0083-fleet-sync-and-scanner-remediation.md |
|
||||
| workplan | CUST-WP-0083 | blocked | — | workplans/CUST-WP-0083-fleet-sync-and-scanner-remediation.md |
|
||||
| workplan | THE-WP-0001 | finished | — | workplans/THE-WP-0001-federation-interface.md |
|
||||
| task | CUST-WP-ADHOC-2026-05-02-T01 | done | — | workplans/ADHOC-2026-05-02.md |
|
||||
| task | CUST-WP-ADHOC-2026-07-02-T01 | done | — | workplans/ADHOC-2026-07-02.md |
|
||||
|
|
@ -581,13 +581,15 @@
|
|||
| task | CUST-WP-0082-T24 | todo | — | workplans/CUST-WP-0082-netkingdom-security-hardening.md |
|
||||
| task | CUST-WP-0082-T25 | todo | — | workplans/CUST-WP-0082-netkingdom-security-hardening.md |
|
||||
| task | CUST-WP-0083-T01 | done | — | workplans/CUST-WP-0083-fleet-sync-and-scanner-remediation.md |
|
||||
| task | CUST-WP-0083-T02 | progress | — | workplans/CUST-WP-0083-fleet-sync-and-scanner-remediation.md |
|
||||
| task | CUST-WP-0083-T03 | progress | — | workplans/CUST-WP-0083-fleet-sync-and-scanner-remediation.md |
|
||||
| task | CUST-WP-0083-T02 | wait | — | workplans/CUST-WP-0083-fleet-sync-and-scanner-remediation.md |
|
||||
| task | CUST-WP-0083-T03 | wait | — | workplans/CUST-WP-0083-fleet-sync-and-scanner-remediation.md |
|
||||
| task | CUST-WP-0083-T04 | wait | — | workplans/CUST-WP-0083-fleet-sync-and-scanner-remediation.md |
|
||||
| task | CUST-WP-0083-T05 | todo | — | workplans/CUST-WP-0083-fleet-sync-and-scanner-remediation.md |
|
||||
| task | CUST-WP-0083-T05 | wait | — | workplans/CUST-WP-0083-fleet-sync-and-scanner-remediation.md |
|
||||
| task | CUST-WP-0083-T06 | done | — | workplans/CUST-WP-0083-fleet-sync-and-scanner-remediation.md |
|
||||
| task | CUST-WP-0083-T07 | done | — | workplans/CUST-WP-0083-fleet-sync-and-scanner-remediation.md |
|
||||
| task | CUST-WP-0083-T08 | progress | — | workplans/CUST-WP-0083-fleet-sync-and-scanner-remediation.md |
|
||||
| task | CUST-WP-0083-T08 | wait | — | workplans/CUST-WP-0083-fleet-sync-and-scanner-remediation.md |
|
||||
| task | CUST-WP-0083-T09 | done | — | workplans/CUST-WP-0083-fleet-sync-and-scanner-remediation.md |
|
||||
| task | CUST-WP-0083-T10 | done | — | workplans/CUST-WP-0083-fleet-sync-and-scanner-remediation.md |
|
||||
| task | THE-WP-0001-T01 | done | — | workplans/THE-WP-0001-federation-interface.md |
|
||||
| task | THE-WP-0001-T02 | done | — | workplans/THE-WP-0001-federation-interface.md |
|
||||
| intake | CUST-IN-0001 | closed | green | intake-legacy-suggestions-migration.md |
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ type: workplan
|
|||
title: "Publish local repository changes and resolve scanner publication failures"
|
||||
domain: infotech
|
||||
repo: the-custodian
|
||||
status: active
|
||||
status: blocked
|
||||
owner: codex
|
||||
created: "2026-11-01"
|
||||
updated: "2026-11-01"
|
||||
|
|
@ -29,17 +29,17 @@ Discovered 210 checkouts. Reviewed primary changes, managed clones, linked workt
|
|||
|
||||
```task
|
||||
id: CUST-WP-0083-T02
|
||||
status: progress
|
||||
status: wait
|
||||
priority: high
|
||||
```
|
||||
|
||||
Seven repositories received source/workplan/session/capture commits, and 16 affected repositories stopped tracking their generated local brief while preserving it on disk. 168 checkout tips have been directly verified equal to remote refs. Intelligence Radar's full original history is now published after bounded normal receiver scans; temporary refs were removed. Custodian smaller-batch commit loop is live as unified-exec `54197`; only that loop owns the index. Per-commit pushes continue separately. Exact result files are linked in `docs/repository-sync-2026-11-01.md`. Generated-only refreshes and rejected originals remain intact pending their documented dispositions.
|
||||
Seven repositories received source/workplan/session/capture commits, and 16 affected repositories stopped tracking their generated local brief while preserving it on disk. 168 checkout tips have been directly verified equal to remote refs. Intelligence Radar's full original history is now published after bounded normal receiver scans; temporary refs were removed. Custodian smaller-batch commit loop is terminal: 232 initial paths plus 3,553 retry paths were committed, and 139 original paths remain scanner-refused. The clean-file checkpoint was remotely verified at b4dfcd794117236852c111419bc47fa167df1f9b; audit/source metadata is published separately. No index writer remains active. Exact result files are linked in `docs/repository-sync-2026-11-01.md`. Generated-only refreshes and rejected originals remain intact pending their documented dispositions.
|
||||
|
||||
## Diagnose failures and prepare narrow class-level correction
|
||||
|
||||
```task
|
||||
id: CUST-WP-0083-T03
|
||||
status: progress
|
||||
status: wait
|
||||
priority: high
|
||||
```
|
||||
|
||||
|
|
@ -51,6 +51,8 @@ Generated-only gates, local/remote scanner deadlines and false positives are ind
|
|||
id: CUST-WP-0083-T04
|
||||
status: wait
|
||||
priority: high
|
||||
needs_human: true
|
||||
intervention_note: "Run bash /tmp/forge-scanner-preflight.sh in the founder terminal and return the selected receipt; exact native correction and rollback will then be prepared for approval."
|
||||
```
|
||||
|
||||
Human-lane checkpoint: the current ops-mason-builder identity cannot inspect the forge or perform native administration. The founder returned current deployment/pod identity using their attended admin context. Read-only artifact/config/guard/headroom inspection is prepared as `/tmp/forge-scanner-preflight.sh` and awaits its result. Prepare the exact guarded rollout, verification, rollback and cost/risk assessment from this evidence before requesting approval. The agent must not borrow the founder admin kubeconfig. No local runtime scanner or receiver policy is changed by the existing candidate. Preserve original revisions, failures and any refinements in supervised receipts; no autopilot or scored approval is inferred.
|
||||
|
|
@ -59,7 +61,7 @@ Human-lane checkpoint: the current ops-mason-builder identity cannot inspect the
|
|||
|
||||
```task
|
||||
id: CUST-WP-0083-T05
|
||||
status: todo
|
||||
status: wait
|
||||
priority: high
|
||||
```
|
||||
|
||||
|
|
@ -89,12 +91,32 @@ Completed 2026-11-01. Approval-engine, informed-decision and state-hub adopted t
|
|||
|
||||
```task
|
||||
id: CUST-WP-0083-T08
|
||||
status: progress
|
||||
status: wait
|
||||
priority: medium
|
||||
```
|
||||
|
||||
The all-ref audit found seven non-current branches with commits absent from remote refs. Four are now published under their existing names without rewriting or merging main: executor-sandbox local-smoke-2026-07, reef-railiance backup-pre-main-reset, rein-aharness assembly-webfetcher-v0.2.0, and Custodian cust-wp-0081-original-unpublished. Normal receiver acceptance and exact remote-tip checks passed. Three histories retain scanner refusals: RApp user-engine's pre-envstrip backup contains captured GPG_KEY fingerprint entries; Apps custody preparation has a JSON SHA256-manifest false positive; coulomb-social's unpublished progress branch hits generic-api-key on documentation prose at docs/usecases/platform-communication.md line 41. The exact introduced blob failed even though commit-diff inspection was clean, showing why diff-only scanning is insufficient. Original historical branches remain intact; do not bypass the receiver or call a raw fingerprint a private key. Propose narrowly scoped, content-bound adjudication for these classes and preserve the complete scanner scope. Receipts: `/tmp/unpublished-branch-inspection-results.json`, `/tmp/extra-branch-push-results.json`, `/tmp/csoc-unpublished-object-inspection.json`. The current mail-address-semantics tip was also rechecked and its push found the remote already up to date.
|
||||
|
||||
## Publish the archive files that pass the existing policy
|
||||
|
||||
```task
|
||||
id: CUST-WP-0083-T09
|
||||
status: done
|
||||
priority: high
|
||||
```
|
||||
|
||||
Completed 2026-11-01. The initial successful batches committed 232 paths and the retry committed 3,553 paths, including the archive audit. All clean-file batches passed normal local hooks and remote introduced-object checks, and the completed archive checkpoint b4dfcd794117236852c111419bc47fa167df1f9b was directly equal to remote main. Exactly 139 original paths remain; every one has value-free rule/line diagnostics. There are no unverified or generated-only leaf refusals in the smaller retry. This closes the eligible-file phase of T02, not the remaining held publication or the full goal.
|
||||
|
||||
## Verify the paired JSON-profile source candidate
|
||||
|
||||
```task
|
||||
id: CUST-WP-0083-T10
|
||||
status: done
|
||||
priority: high
|
||||
```
|
||||
|
||||
Completed 2026-11-01. Paired local/receiver rule changes have identical profile content; 12 selected local pinned-Gitleaks tests passed and the full receiver suite passed in 150.087 seconds with the real pinned scanner. The exact RApp rejected source-pin blob passes the candidate. Source/binary digests, negative-test coverage and rollback intent are retained in docs/changes/2026-11-01-scanner-json-digest/. This extracts completed source proof from T03; it is not native admission, authority, activation or a disposition for unrelated findings.
|
||||
|
||||
## Evidence
|
||||
|
||||
`docs/repository-sync-2026-11-01.md` is the cumulative audit. `/tmp/*-results.json` files are execution receipts that still need a durable sanitized closeout summary. Required `statehub fix-consistency --repo the-custodian` is pending the single active staging loop becoming terminal; do not let consistency/autocommit race its index.
|
||||
`docs/repository-sync-2026-11-01.md` is the cumulative audit. `/tmp/*-results.json` files are execution receipts that still need a durable sanitized closeout summary. The single staging loop is now terminal. Required `statehub fix-consistency --repo the-custodian --no-writeback` will assign missing IDs and reconcile these authoritative file statuses without importing DB status into the files.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue