Skip to content

human todo

Jerry Holland edited this page Nov 15, 2026 · 55 revisions

Human TODO

Required human actions have public issues and step-by-step procedures here, with planning on the private project board. The issue is the record of ownership, status, decisions, and evidence. These instructions do not activate parked work or close a follow-up when implementation merges. Agent preparation can continue while the human action is pending.

Issue Procedure When needed
#14 OneDrive path probe qualified Done: owner confirmed active sync during the 2026-09-15 probe window (confirmed 2026-09-16); remaining #14 work needs no human
#18 Bounded native read-engine decision accepted Done: ADR-0027 accepted; the bounded optional read increment shipped through #83
#19 Continue the adopted branch-and-land pilot Closed 2026-11-06 as done: compact landings with carried provenance are this repository's routine. The missing dimensions (a real conflict, concurrency, a recovery in anger, POSIX workspaces) are Gate B condition 9 design evidence for N3's ADR (#312)
#22 Record the identified Windows benchmark baseline Done 2026-09-09: lab-windows-a recorded and qualified; the procedure stays for the next re-record
#68 Windows-only release latency qualification Done: Windows-only scope delivered in PR #82; current releases qualify the matching lab-windows-a machine only. Functional Windows/POSIX qualification remains required
#27 Causal-rebase usability judged Done: the owner's walkthrough matched every prediction (2026-09-17); ADR-0032 accepted
#41 Supply and review Gate B user evidence Done: maintainer accepted the standing evidence record; all nine Gate B conditions remain unproven
#42 Establish representative host evidence Closed 2026-11-06 as superseded: ADR-0043 stopped the performance program for Git-backed repositories, and N1's corpora (corpora.yml) now produce real-repository evidence on hosted Linux and Windows runners
#124 Complete the v0.17.0 release Done 2026-09-23: released at cf371ea after #122 (gate 3 run 35775710024, 15/15; gate 10 passed on lab-windows-a); release
#115 Scope the board's auto-add workflow to this repository Done 2026-11-06: the owner scoped the workflow. Verified the same day: an updated Ashebrook issue stayed off project 7
#139 Set up npm publishing for @holland-vip/causet Step 5 done 2026-10-13: trusted publisher configured and tokens disallowed on all three packages; NPM_PUBLISH stays true (owner, 2026-10-14). Still required: a tag run whose npm publish succeeds with provenance, blocked by npm/cli#9969; until then, publish each stable version by hand with scripts/publish-npm.ps1 (procedure, "Until step 6"; #448, 2026-11-13); since #440 (2026-11-12), NPM_PUBLISH is false while it is blocked (done 2026-11-13, #442), and step 6 turns CI publishing back on
#441 Let the release workflow create release tags Done 2026-11-13: the owner removed "release tags are created by maintainers" (GitHub refused GitHub Actions as its bypass actor); "release tags are immutable" stays, verified on #441
#442 Turn off npm publishing from CI while npm/cli#9969 is open Done 2026-11-13: NPM_PUBLISH is false, verified on #442; npm stays a hand publish until #139 step 6
#217 Complete the v0.21.0 release Closed 2026-10-18 as superseded: v0.21.0 shipped 2026-10-09; trusted publishing is tracked on #139, and the release workflow runs the install check on a hosted Windows runner, so no machine of the owner's is needed (#289)
#240 Complete the v0.22.1 release Done 2026-10-14: released at 7e5f899; the owner published the npm packages by hand (npm/cli#9969 refused the tag run's publish); release. Install by script and by npm reports causet 0.22.1
#245 Complete the v0.23.0 release Done 2026-10-14: released at 6aae8da; the owner published the npm packages by hand (npm/cli#9969 refused the tag run's publish); release. Install by script and by npm reports causet 0.23.0 with cst only, and an upgrade from 0.22.1 removes vlab
#253 Complete the v0.24.0 release Done 2026-10-15: released at 19626b0; the owner published the npm packages by hand (npm/cli#9969 refused the tag run's publish); release. Install by script and by npm reports causet 0.24.0
#267 Complete the v0.25.0 release Done 2026-10-16: released at 53b671b; the owner published the npm packages by hand (npm/cli#9969 refused the tag run's publish); release. Install by script and by npm reports causet 0.25.0
#274 Complete the v0.25.1 release Done 2026-10-17: released at 658c200; the owner published the npm packages by hand (npm/cli#9969 refused the tag run's publish); release. Install by script and by npm reports causet 0.25.1
#168 Rename the repository and the project board to causet Done 2026-09-29: repository is jwh3times/causet, project 7 is "causet"; links updated in PR #169 (de6e11e) and the wiki
#337 Report Git's commit-graph hang upstream No deadline: a Git bug the generated-history corpus found (PR #333); causet already works around it
#453 Report Git's %B overread upstream No deadline: a Git bug the native cst log differential tests found (PR #452); causet prints nothing there and documents it
#49 Published-object retention decision completed Done: ADR accepted 2026-09-09; implementation merged in PR #75. Backfill guide

Each procedure identifies the owner role, prerequisites, numbered execution steps, verification, failure handling, and completion evidence. Replace example host labels with the stable label assigned to the actual machine. A latency skip or deterministic-only pass does not qualify host latency.

After the human action is performed, attach suitable evidence or the decision to the issue, remove human-action-required when that dependency is satisfied, and update the board. Retain the procedure and issue link for future reference. The live human-action issue filter is the current list; this page provides the execution instructions.

Sensitive vulnerability details and restricted procedures belong in a draft repository security advisory, with access-appropriate private board tracking, until public disclosure is authorized. Do not put credentials or private repository contents in public issue comments or wiki pages.

See the agent follow-up settings and benchmark host guide.

Clone this wiki locally