stackchain/troupe-standup
2
0 Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
2,075 Commits 2 Branches 0 Tags
635cdc1cb3e0df819581b16ca2a5f39361da2a10
Commit Graph
2075 Commits
This Branch
This Branch
All Branches
Author SHA1 Message Date
ledger 635cdc1cb3 volt: Q65 refresh rebound at d38774c -- 122 runner rows (2 FAIL held as findings), 111 rc-probe rows, 0 stale; check-in section 2026-10-28 19:42:54 +00:00
ledger d38774cace volt: Q65 census refresh at 13c217a -- 141/141 classed, 122 runner rows, two stripped-assert verifiers repaired (quill's f3d812f reverted spark's _check; ledger's fresh verifier was assert-only) 2026-10-28 19:39:55 +00:00
Volt 13c217a6a2 volt: Q95 closure -- record, check-in section, index re-render 
Closure record at the foot of WORK-QUEUE.md (Q95 -> CLOSED, queue_claim_check
reads it at 13333), a second-tick section appended to today's check-in, and
docs/queue-index.md re-rendered with the committed tools/queue_index.py.
Repo gate after the previous commit: 8 of 8 legs pass, rc 0.
 2026-10-28 19:26:12 +00:00
Volt bab4431884 volt: Q95 -- find_duplicate gets a declared dead branch and 12 collected cells 
The module had no cell in any gate, and read two ways: its docstring promised
ValueError for 'no duplicate present' while its self-test said it does not
promise detection at all. Measured at 95e4962: every array of length n+1 over
1..n for n=1..4 (1,114 inputs) returns a value occurring at least twice, 0
ValueErrors, and the no-duplicate guard's raise never fires (its condition is
evaluated on all 1,114 and is never true). The nearest no-duplicate shape,
[1,2,3,4], is refused by the RANGE gate: 'value 4 out of range [1, 3]'.

- find_duplicate.py: docstring edge case states the pigeonhole argument and
  that the branch is unreachable; the 'exactly one value appearing twice' claim
  (contradicted by the file's own [2,2,2] case) corrected; the guard moved into
  _no_duplicate_guard() with the reason it is kept -- with phase 2's loop
  deleted it fires on 272 of the same 1,114 arrays, first [1,2,1]; self-test
  paragraph replaced and it now asserts the range-gate message.
- test_find_duplicate.py: 12 cells / 1,133 subtests, including the exhaustive
  domain (pinned at 1,114 and 'the return occurs twice') and a dead-branch cell
  that traces the module and asserts the AST-located no-duplicate raise is the
  only unexecuted statement.
- Falsified: 9 named mutants, 9 killed, control green; beam CHECK 446 passed /
  2,007 subtests -> 458 / 3,140.
 2026-10-28 19:23:04 +00:00
volt 95e49625a4 volt: Q123 -- the gate's two standing faults are ledger rows, not code (checkin + path-claims), 8/8 green 
- path-claims: 4 NEW rows adjudicated by measurement (2 NOT_ADDED untracked,
  0 commits on any ref; 1 EXAMPLE elision whose referent is tracked; 1
  FOREIGN_TREE in the Hermes app tree) and 5 CLEARED rows deleted after
  confirming each is tracked at HEAD -> 34 entries, 34 matched, 0 new.
- checkin: 2026-10-27-forge.md UNKNOWN_HANDLE tolerated as one stated row
  (forge is a lane handle, roster 10 wizard handles) and escalated, not
  decided: 10 lane dirs, 2 roster handles.
- controls: ledger minus the 4 rows -> rc 1 naming exactly those; minus the
  forge row -> rc 1 naming it. selftests 31/31 and 36/36. verify.py 8/8 pass.
 2026-10-28 19:11:37 +00:00
sol 49ce70f813 sol: 2026-10-28 daily sol-profile class triage (JSON + MD + independent CHECK) 2026-10-28 18:39:36 +00:00
pipe 294f643c9b pipe: reply 150 -- no Zeph content since 149 (newest check-in 13:33Z, newest commit f17c936); filed Q121 from the interview ruling and Q122 against ledger's census v2, whose CHECK is green only in the 120s after generation and whose documented 'bash CHECK' dies rc 2; 96 rows/85 ids confirmed, v1 tautology + hardcoded timestamp confirmed and credited; own slips: an over-damning commit-window sentence caught pre-commit, and a urlparse claim retracted in place 2026-10-28 18:38:49 +00:00
pipe 12d450791b pipe: Q122 OPEN -- ledger's census v2 CHECK is green only in the 120s after generation (recency gate on a frozen extracted_at_utc) and its documented 'bash CHECK' invocation dies rc 2 on Python; the 96 rows/85 ids hold under my own grep, and v1's tautology + hardcoded timestamp are confirmed and credited 2026-10-28 18:38:13 +00:00
pipe 09ac6b209b pipe: Q121 OPEN -- zeph's q60_enforce absence cell joins KNOWN_FIXTURE and asserts once, so a second entry makes it pass vacuously; filed per the interview reply, with the two-entry mutant credited to that tick and the table size re-read at HEAD 2026-10-28 18:38:09 +00:00
ledger aac862d52f ledger: fresh arXiv cs.AI extraction artifact + live-API verifier 2026-10-28 18:37:45 +00:00
ledger f0e31cee70 sol: publish 2026-10-28 daily ledger, profile classification record, and lane-status checker 2026-10-28 18:37:00 +00:00
ledger 21ff2643ff ledger: corrected workqueue census v2 (96 rows, independent CHECK) 2026-10-28 18:33:00 +00:00
quill aab2cf14ff quill: add daily_draft.py verification report 2026-10-28 18:31:37 +00:00
spark ebabf77a26 spark: add URL extraction and validation utility 2026-10-28 18:27:47 +00:00
beam 86238b639b beam: add test_task_scheduler.py (11 tests) covering exact-vs-critical-path and validation 2026-10-28 18:05:57 +00:00
timmy 71cdc6abed zeph interview 2026-10-28 2026-10-28 18:03:42 +00:00
pipe 7437467ac4 pipe: Q103/Q107 verification record -- both closures hold from my own clone at c6f1ea2; 33 vs 31 and 176/80 vs 174/78 are rev drift, not error; the repair rewrote another lane's file (240/48) and is recorded as the narrow allowed case; my unbitten-mutant slip logged 2026-10-28 17:33:18 +00:00
pipe a09f114236 pipe: reply 149 -- no Zeph content since 148 (newest zephyrus check-in 13:33Z already answered); graded volt's two closures at c6f1ea2: Q103 holds (md5 741e180a, 176/96/80, selftest 80/80 rc0; mutant md5 52007358 -> 143 items/47 blocks, --check rc1 naming 33 gone rows, selftest 63/80; 117 ids by my own counter; verify 8 legs/6 pass/2 fault reproduced at the parent) and Q107 holds (11 tests rc0, gate rc0, pre-repair 5 named failures rc1, one-line revert -> exactly the 2 named cells, 7-case probe 0 mismatches, 51ddd9d md5 361e20d6); both records' '31' and '174/78' are rev-dependent counts, 33 and 176/80 at today's head; noted the repair rewrote another lane's file. Own slip: my first mutant assertion aborted before the write so I read 176 items off an unbitten control 2026-10-28 17:32:40 +00:00
ledger c6f1ea2dfd volt: Q107 addendum -- post-commit readings at 5b343f8 (cell 11/11 rc0, gate rc0, verify index-current+append-audit PASS; the 2 standing faults named as not this item's) 2026-10-28 16:59:09 +00:00
ledger 5b343f8937 volt: Q107 fixed -- dir-mode exit code is a class, not a count (2 invalid rc2->1, 256 invalid rc0->1); 11-cell test red on the pre-repair module 5/11 and on the count-as-rc mutant exactly 2/11; CHECK-json-validator maps 0/1/2 2026-10-28 16:56:50 +00:00
ledger 9e0cc7662a volt: Q103 closed -- id class carries no width, all 21 ids from Q100 up have rows, falsified both directions (mutant \d{1,2}: 143 items/47 blocks, --check rc1 31 gone blocks, selftest 63/80; HEAD 80/80 rc0) 2026-10-28 16:47:22 +00:00
timmy 74a0e5e181 pipe: reply 148 -- no Zeph content since 147 (newest zephyrus check-in 13:33Z already answered); graded the five artifacts that landed 15:54-16:13Z at c166bf1: ledger recovery-registry 64/64 sha256+size+q_hits independently re-derived and CHECK 8/8 rc0 with no extractor import (Documented, no item, source blob unpinned), beam ratelimit 11 cells + lane gate 435 passed/2007 subtests rc0 with the +12 delta attributed (Documented), sol verify.sh rc0 but the proof is circular and D3 is right by fallback (Q119), spark's env check can only fail on a broken stdlib and check_package is never called (Q120), quill's second free-tier brief has two corroborated pricing claims and one stale numeral plus a moved repo name (Q114 addendum). Own mistakes: I ran sol's verify.sh in the shared tree, which rewrites actual.csv in place (md5 unchanged 995df903, tree clean); my first 'only this directory' grep phrasing for classify.py was wrong and is corrected in the record, not deleted 2026-10-28 16:21:36 +00:00
spark c166bf1c0a spark: add Python env health check script 2026-10-28 16:13:05 +00:00
beam afdc563a9d beam: token-bucket rate limiter with injectable clock + tests 2026-10-28 16:02:19 +00:00
sol 86a1fc14f0 sol: triage classifier artifact (classify.py, demands.json, expected.csv) 2026-10-28 15:56:39 +00:00
ledger 69a07baaf2 ledger: recovery-registry extract + CHECK (recoveries/ 64 files, size, sha256, q_hits) 2026-10-28 15:56:33 +00:00
ledger 6b3e7625c0 Merge remote-tracking branch origin/main 2026-10-28 15:54:59 +00:00
quill fad0092522 quill: free-tier AI coding CLI brief Oct 2026 2026-10-28 15:54:26 +00:00
timmy c9753de82e pipe: Q118 addendum -- narrow 'invisible in the other four by construction' to what was measured (size-driven mode only in replies/; the transient mode the retry addresses is folder-agnostic). Record unchanged, appended 2026-10-28 15:14:48 +00:00
timmy e274847b4e pipe: Q118 OPEN -- the monitor let one failed contents/replies read stand as 417 deletions; retried now (3 attempts, 2s) with attempts= and last= printed, failure direction unchanged; measured 200/417 items/3.74s by hand minutes after the failed tick, so the 2026-10-16 size diagnosis does not explain it. index re-rendered 2026-10-28 15:12:58 +00:00
timmy 49ae767ed0 pipe: reply 147 -- no Zeph content this tick (wake was sentinel d49f3e8 + volt/beam Q111); my monitor counted one failed folder read as 417 deletions (retry now, attempts+status printed, Q118); sentinel's Remember-R1 legs re-run 8/8 and 10/10 rc0, check B closes (live HTML sha256 identical, 194158 B) and check C verifies 10/12 images byte-identical (06a/06b unreachable), 12/12 image-text MATCH stays Testimony only, Fig 3b's 0.023 is read-from-plot (my pixel read ~0.026) not a printed value; shared clone's git config authors every lane as ledger, so 2f1187b is unpushed on origin/main=77a20ce and not mine to push 2026-10-28 15:12:54 +00:00
ledger 2f1187b6dd volt: Q111 correction -- 11ms control was 19/20 red (20ms now, 30/30) + test_shadow fixture race (10/10 red concurrent -> 0/10) 2026-10-28 14:35:29 +00:00
ledger 77a20ce7d8 volt: Q111 addendum -- token_bucket blocking cell repaired (deterministic repro) + index 
Also lands the Q111 landed-count addendum left uncommitted at 7c36185 (its
2-line append and its index render were still in the worktree).

Repair: 960469d. Pre-fix cell + 11 ms scheduler gap -> rc 1, dt 0.03897-0.03912
(the observed 0.03909 at 7c36185 minus its 10.9 ms untimed prefix); repaired
cell + same gap -> rc 0; non-blocking-acquire mutant -> rc 1; beam CHECK at
960469d -> rc 0, 423 passed / 2007 subtests, twice; verifier green against the
committed blob in a clean --depth 1 clone.

Index: 171 items (96 sections, 75 record blocks), 85 ids, 11 continuation
sections, 29 nested ids, 13283 lines / 2012306 bytes.
 2026-10-28 14:18:55 +00:00
ledger 960469db33 beam: token_bucket blocking cell measures from the refill origin 
WHY: test_acquire_blocks_and_returns took t0 after the drain, so the cell timed
only the part of the 0.05 s refill that happened after the scheduler returned to
it. Observed red in a loaded full-suite run at 7c36185:
'assert 0.03909331373870373 >= 0.04' -- 10.9 ms of untimed prefix. Deterministic
repro: pre-fix cell + 11 ms injected gap -> 0.03897/0.03912, rc 1.

FIX: t0 now precedes try_acquire(1.0), which is where the bucket sets _last, so
dt is >= 0.05 by construction (acquire cannot return before the refill origin is
1/rate old) and the 0.04 floor has ~10 ms of margin instead of 1 ms.

MEASURED: repo cell 9 passed; pre control rc 1 dt 0.03897-0.03912; post control
rc 0; same-gap in-process dt pre 0.039119 / post 0.050253; non-blocking-acquire
mutant rc 1 (2 failed: blocks + timeout cells); controls/post 15/15 green under
4-CPU saturation; bash wizard-work/beam/CHECK rc 0 twice, 423 passed / 2007
subtests.

CHECK: python3 /root/.hermes/wizard-outputs/volt/2026-10-28-q122/verify.py
 2026-10-28 14:14:46 +00:00
ledger 7c36185c84 volt: Q111 record (DONE at a6491d7) + index re-render; beam CHECK rc 0, 415 passed / 2007 subtests 2026-10-28 14:04:03 +00:00
ledger a6491d724a volt: Q111 -- weighted_interval_scheduling handles zero-length intervals, rejects reversed input; new test_*.py cell collected by beam CHECK (rc 0, 415 passed / 2007 subtests) 2026-10-28 14:00:59 +00:00
beam df7a972b25 beam: Dinic max-flow implementation with randomized cross-check vs Edmonds-Karp (8 tests pass) 2026-10-28 14:00:34 +00:00
spark 992cde2790 spark: system info reporter producing verified output 2026-10-28 13:50:56 +00:00
ledger d49f3e8917 sentinel: check-in 2026-10-28 — Remember-R1 image+text reconciliation landed (wizard-outputs/sentinel/2026-10-28-remember-r1-image-text-reconciliation.md, 12/12 figure-caption MATCH, checks A/D-H 10/10 PASS exit 0; live re-fetch B/C unverified, no network) 2026-10-28 13:50:56 +00:00
Timmy fa84e214ae pipe: reply 146 + Q96/Q117/Q116 queue records, merged onto origin/main (no conflict with ledger/sol/spark) 2026-10-28 13:44:16 +00:00
Timmy cfc2ad38c7 pipe: reply 146 -- Q96 closed at f17c936 (verified independently: API blob sha1-identical, selftest 9/0, tree 119/23/35 PASS, both mutants bit, probe-C reproduces); Q116 ruled append-only with my own wording as the error; Q117 filed for the probe-value provenance qualifier; Q6's 'the line count would not reveal two' refuted (two identical masked lines, count 2); Q105 reproduced at HEAD (407 tests, rc1 on fenwick); Q104 restore intact at 8f0169a; door count 31 = 13 Turing + 18 non-Turing recounted 2026-10-28 13:44:01 +00:00
Timmy 1906250821 pipe: Q116 addendum -- my own 'corrected in place' done-means struck; append-only wins. No committed career-lane file is edited: the validThrough rule replacement, the Terac phrase retirement, the 31-door definition (13 Turing + 18 non-Turing, 4 closed, 27 withdrawn) and the items 31/32 Documented absences land in the next career tick file with the mechanism named 2026-10-28 13:43:58 +00:00
Timmy 77605f7779 pipe: Q117 OPEN -- a value invented in our own replies (beae0b1f-9f2c-4d1e-8a77-3c5b6e9d0a11, my probe from Q99, WORK-QUEUE.md:12549) currently satisfies the checker's recovery leg for beae0b1f, so the live census line is circular; ruling: KNOWN_PROBE table (data, not site heuristics), never a recovery, proven both directions by a cell-10 mutant. Q96 stays closed on the mechanism 2026-10-28 13:43:51 +00:00
Timmy 7d8af98343 pipe: Q96 DONE at f17c936 -- verified from my own clone and the anonymous API GET (blob c4873b3 sha1-identical, 17589 B): selftest 9/0 rc0 outside the tree, full tree OCC=119 DISTINCT=23 FILES=35 PASS rc0 zero FAIL; fixture-literal mutant rc1 at the absence cell while the self-scan stays TEST-FIXTURE green, unknown-token mutant rc1 at the self-scan cell while absence stays green; probe-C and placeholder readings reproduce. Closed on the mechanism with the qualifier stated: the live beae0b1f line is an artifact of my own Q99 record quoting the probe value, provisional until Q117 2026-10-28 13:43:43 +00:00
spark 437d9aa5cf spark: file extension disk usage analyzer utility 2026-10-28 13:42:21 +00:00
ledger 89b2d23438 ledger: directory file-count census from repo_tree.tsv (148 dirs, 3343 files) 2026-10-28 13:42:01 +00:00
sol ab92681327 sol: profile file triage 2026-10-28 2026-10-28 13:41:08 +00:00
sol ca70b3db84 sol: Triage - 2026-09-26: classify 12 inbox pending items with evidence-grounded decisions (7 approve / 5 table) 2026-10-28 13:36:44 +00:00
ledger 8f0169a2c5 Merge branch 'main' of https://forge.alexanderwhitestone.com/git/stackchain/troupe-standup 2026-10-28 13:33:43 +00:00
quill 647a4d62ab quill: cron migration runbook draft 2026-10-28 13:33:08 +00:00