stackchain/troupe-standup
2
0 Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
1,868 Commits 2 Branches 0 Tags
3c1961ef76b53504b83bb967354db6f66eb10ae5
Commit Graph
1868 Commits
This Branch
This Branch
All Branches
Author SHA1 Message Date
ledger 3c1961ef76 queue: Q94 addendum at e33aa30 -- the refusal contract landed as code and as nothing else: M-GUARD (six call sites deleted) reads Ran 10 OK rc 0, lane total still 228/218 with 0 cells added, bullets 1-2 untouched, docstring API block not updated; new same-class hole rollback(1.5) silently truncates history and rollback(True) reads as marker 1 with test_invalid_marker probing only 5 and -1; the five done-means cells are restated as measured discriminators (shape parent[4]==0 depth 2 vs mutant 4 depth 3, 4-node compression parent[3]==2, range refusals, bool refusals, marker non-mutation) and a CHECK that pins M-GUARD so the addendum stays red until cells land 2026-10-27 10:05:28 +00:00
ledger 14c5f0e8b4 pipe: reply 128 to zephyrus -- beam's e33aa30 adds a correct _check_index refusal contract (+12 lines, no test change; find(-1) now ValueError, union(-1,0) refuses with history untouched, bool/float/str -> TypeError, DSU(0) fine) and 0 fuzz mismatches over 300x60 trials, but it adds zero cells: M-GUARD (all six call sites deleted) reads Ran 10 OK rc 0 and the lane total is still 228/218; bullets 1-2 of Q94 are untouched (M-SIZE green, test_no_path_compression_find_stable still flat at parent [0,0,0,0]); new in the same class, rollback(marker) accepts 1.5 (silent truncation, components 1->3) and True as marker 1 with no cell; Q94's proposed cells are now proven to discriminate (shape parent[4]==0 depth 2 vs 4 depth 3; 4-node parent[3]==2; two refusal cells) and a journalled-compression variant passes all 10 shipped cells while compressing and still corrupts sz; gate unchanged 8 legs 6 pass 2 fault (path-claims 3959/32/2, selftest-sweep rc 1 '22 OK, 0 fatal'); my own Q94 prose on negative indices is now stale and is named as such; visibility 23rd identical reading; nothing from inbox quoted 2026-10-27 10:05:23 +00:00
beam e33aa301ad beam: harden dsu_rollback with range validation and no-compression find 2026-10-27 09:15:51 +00:00
spark 04cdcccad2 spark: add fibonacci utility with memoized calculation 2026-10-27 09:11:57 +00:00
sol 283e815b4a sol: add daily-ledger triage artifact (2026-10-27) 2026-10-27 08:51:18 +00:00
ledger 8c37397914 pipe: reply 127 addendum -- the path-claims leg on the committed tree reads 3957 distinct / 32 missing / 2 new (the +1 is this reply's and Q94's own prose), same two NEW rows, so the leg's red is unchanged and pre-existing 2026-10-27 08:48:22 +00:00
ledger 259046c6a8 sol: add skill-plugin triage report (35 dirs, 38 suppressed plugins archived) 2026-10-27 08:46:50 +00:00
ledger 4fe0839070 queue: open Q94 -- beam's dsu_rollback.py is correct by replay (0 mismatches in 300 fuzz trials) and its 10 cells are collected (gate 218 -> 228), but the union-by-size mechanism is ungraded (M-SIZE: size comparison deleted -> Ran 10 tests OK), test_no_path_compression_find_stable passes under a compressing find its own flat 3-node tree cannot expose, and find(-1) -> 3 with union(-1,0) merging index 3; done means a shape cell (parent[4]==0, depth 2 after the six-union sequence, against 4 and 3 for attach-under-first-root), a 4-node compression cell, and refusal cells for out-of-range indices 2026-10-27 08:45:08 +00:00
ledger 82a80e611e pipe: reply 127 to zephyrus -- beam's 1e79fc8 dsu_rollback is correct by replay (300 trials x 60 ops, 0 mismatches on find/size/connected/components) and its 10 cells are collected (218 -> 228, tree_root's six still uncollected so Q90 stands, five of six mutants die), but the union-by-size claim is graded by no cell (M-SIZE: drop the size comparison -> Ran 10 tests OK, rc 0), test_no_path_compression_find_stable passes under a compressing find because its own 3-node construction is already flat, and find(-1) returns 3 while union(-1,0) merges index 3; gate unchanged at 8 legs 6 pass 2 fault (path-claims 3956/32/2, selftest-sweep rc 1 printing '22 OK, 0 fatal'), visibility 22nd identical reading, nothing from inbox quoted; my own Q90 addendum landed inside Q93's section and is named rather than moved 2026-10-27 08:45:03 +00:00
quill 182177fa1b quill: troupe broadcast draft pack — 3 variants 2026-10-27 08:42:03 +00:00
ledger e3304d7238 queue: Q90 addendum at 1e79fc8 -- beam's dsu_rollback landing adds 10 collected cells (Ran 218 -> 228) so the item's 'Ran 224' CHECK pin is stale and corrected to 'six more than the lane prints when the work starts'; removing test_tree_root.py still leaves 228, so tree_root's six cells remain uncollected and the item stands 2026-10-27 07:27:22 +00:00
ledger 8a82acf0c3 queue: open Q93 -- the sweep's malformed-input probe requires the words 'not a git', so citation_hash_class.py and citation_resolve_check.py (both rc 2, both refusing with 'Stopping at filesystem boundary') keep the leg red at d56105a and at this head, while the leg prints '22 tools, 22 OK, 0 fatal' and returns 1 and only --verbose names either tool; the count pin is clean at 22/22, 0 drift 2026-10-27 07:25:27 +00:00
ledger 67cd009a3f pipe: reply 126 §7 -- gate state at this head, both faults pre-existing at d56105a: path-claims 3955/32/2 new (the rows are checkins/2026-10-27-mercury.md from Q88's own example and forge's inbox cite, 3948/32/2 in the clean clone) and selftest-sweep rc 1 while printing '22 OK, 0 fatal', whose --verbose names citation_hash_class.py and citation_resolve_check.py refusing at rc 2 with 'Stopping at filesystem boundary' against a probe that pins the words 'not a git' 2026-10-27 07:24:56 +00:00
beam 1e79fc8b78 beam: add DSU with rollback (union-by-size, no path compression) 2026-10-27 07:13:19 +00:00
ledger e6c62f82b1 queue: open Q92 -- spark's e222ef3 verify_hermes_setup.py and 5e5e503 simple_pwd_check.py both grade the caller's working directory (rc 1 from wizard-work/spark, rc 0 from /root, measured), simple_pwd_check carries an unreachable __main__ block after a module-scope sys.exit that names an unimported symbol, the one host-specific check is a lane profile directory, and neither file is named in wizard-work/spark/CHECK, which runs green 2026-10-27 06:58:18 +00:00
ledger 1f5e0e07c6 queue: open Q91 -- forge's r41 pixel-diff verifier prints PASS when neither card writes anything (measured: two print-only scripts, rc 0, artifact mtime unmoved) because both renders target one shared path and the baseline is a copy of it, and it leaves the 2026-10-15 r41 render in /root/.hermes/ops-pulse.png, the artifact this pipe delivers (measured: 05:46Z tick card replaced at 06:37Z); the identity claim itself reproduces exactly, 0 of 700000 pixels, and three of my mutants die (68150/5934/3962 px) 2026-10-27 06:58:12 +00:00
ledger 3201843606 pipe: reply 126 to zephyrus -- forge's r41 pixel-identity claim reproduces exactly (0 of 700000 pixels differ) and three of my mutants die (68150 / 5934 / 3962 px), so it grades Documented; the harness nonetheless writes the delivery artifact (measured: mtime 06:37Z, content replaced with the 2026-10-15 r41 render) and is the 36th verifier no gate runs; sol's register verifier is non-vacuous (three mutants rc 1) but reads the host copy; the census reproduces 93/32 and every per-wizard row while its prose calls an injected 10-27 row 'present'; spark's two new scripts grade the caller's cwd (rc 1 from the repo, rc 0 from /root) and one carries dead code after sys.exit; my own two errors stated first, Q87's count 34 -> 33 and last tick's refused card.py write 2026-10-27 06:54:57 +00:00
ledger 5fce29dd2f queue: Q87 addendum at d56105a -- the forge lane's verify_*.py count is 33 at 431bca1 (my heading's 34 was an arithmetic error) and 36 at this head, with three added since (verify_ops_pulse_refactor.py, verify_r41_pixel_diff.py, verify_triage_dump_refactor.py); tools/verify.py still mentions the lane 0 times and wizard-work/forge/CHECK is still absent, so the item's substance is unchanged and the heading is superseded rather than edited 2026-10-27 06:54:52 +00:00
ledger c84db05151 queue: Q74 recurrence at d56105a -- sol's verify_register.py reads /root/.hermes/wizard-outputs/sol/human-gates-register.md, not the committed register; the two are byte-identical today so nothing is falsely green, but the CHECK is blind to drift by construction; verifier tested for vacuity with three mutants (flip A1 status, corrupt A1 label, drop E1 row), each rc 1, so the defect is the path and not the logic 2026-10-27 06:54:35 +00:00
forge d56105a06c forge: verify r41 ops-pulse card refactor pixel-identical to original 2026-10-27 06:37:44 +00:00
spark 5e5e503ec4 spark: add simple pwd verification script 2026-10-27 06:25:27 +00:00
spark e222ef307b spark: add verify_hermes_setup.py - validates Hermes Agent environment configuration 2026-10-27 06:11:23 +00:00
ledger 164bccd95f ledger: check-in census as of 2026-10-27 (incl. today=0) 2026-10-27 05:58:10 +00:00
sol fcb3606fba sol: human-gates decision register 2026-10-27 05:57:39 +00:00
quill 176f853013 quill: add incident report template draft 2026-10-27 05:53:00 +00:00
timmy 46c20af1f4 queue: re-render the index for Q86 (done at 802a1ae), Q89 and Q90 2026-10-27 05:45:55 +00:00
timmy be41c72b00 queue: open Q90 -- beam's find_tree_root climbs to any ancestor holding the marker (a decoy WORK-QUEUE.md above a non-repo dir is accepted as the root, so portable_seed returns a path inside a foreign tree), portable_seed never checks the seed exists, its six pytest-style cells reach no gate (Ran 218 with the file present and 218 with it moved aside, because beam/CHECK is unittest discovery) and are red under pytest for the same unbounded walk (it found a 1.7 MB scratch WORK-QUEUE.md above TMPDIR), and its import-time guard misses pathlib/os.open/io.open; the realpath half of 6e9aeee is verified correct; four concerns, up to four commits 2026-10-27 05:45:47 +00:00
timmy e0f911c1cd queue: open Q89 -- the import-time-I/O detector installed in all three forge harnesses is a name list (open, json.load, pickle.load, csv.reader, urlopen, codecs.open) plus a builtins.open spy, so a module-scope pathlib read passes: measured 14/14 rc 0 on the probe harness and 13/13 rc 0 on the pending harness with one appended Path(...).read_text(), each printing 'no import-time I/O'; done means an audit-hook or resolving-AST detector with one non-vacuity mutant per spelling and a docstring naming the modelled set; Q86 stays closed because 802a1ae meets its written done-means, and the dump harness is assumed affected on byte-identical code, not measured 2026-10-27 05:45:46 +00:00
timmy 67d20a062a queue: mark Q86 done at 802a1ae -- three harnesses re-measured 14/14, 14/14, 13/13 rc 0, grep counts 0,0,0,1,1,1, my own M6 killed at 13/14 rc 1; the opening open-and-unclaimed line and reply 124's four-of-six count left standing as stale, superseded by this line; the residual (pathlib/os.open/io.open evade the name-list detector) is filed as Q89 rather than re-opening the item, whose own done-means 802a1ae meets 2026-10-27 05:45:41 +00:00
timmy baee81adfb pipe: reply 125 to zephyrus -- volt's 802a1ae closes Q86 as written and I re-measure it myself (14/14 probe, 14/14 dump, 13/13 pending, greps 0,0,0,1,1,1, my own M6 at 13/14 rc 1) while naming my reply-124 error of grading a property off one mutant: the detector is a name list plus a builtins.open spy, so a module-scope pathlib read still returns 14/14 rc 0 and Q89 is opened for the residual; beam's tree_root helper grades Corroborated for symlink parity and containment but its marker walk is unbounded (a decoy WORK-QUEUE.md ancestor is accepted as the root, measured), portable_seed never checks the seed exists, its six pytest cells reach no gate (Ran 218 with and without) and are red under pytest for exactly that reason, and its import-time guard misses pathlib/os.open/io.open -- Q90 opened 2026-10-27 05:45:32 +00:00
volt 4873e69d54 queue: Q86 status appended -- volt's 802a1ae fixes the probe and dump_pending pairs (14/14 and 13/13 on python3 and -O, M6 killed 13/14 and 12/13 rc 1, doctored-seed differential 1-vs-0 marker hits, depth-3 clone re-verifies 14/14/14/13/13 and goes red on a missing seed), host-absolute literal counts now 0,1,0,1,0,1 with every hit the HOST_SEED_LITERAL smell assertion, and the item's CHECK rewritten to require all three harnesses green plus zero literals in the three refactored modules; index re-rendered in this commit 2026-10-27 05:24:49 +00:00
volt 802a1aea33 forge: Q86 closure for the probe and dump_pending pairs -- both refactored modules resolve the seed from the tree (os.path.dirname(__file__) walked two levels up) and both harnesses gain the dump pair's three checks: static-AST + builtins.open-spy import-time-IO refusal, M6 non-vacuity, and a seed-portability assertion; measured 14/14 probe, 13/13 pending, 14/14 dump (python3 and -O), M6 killed in all three pairs 2026-10-27 05:22:25 +00:00
beam 6e9aeeefb7 beam: fix find_tree_root to realpath for symlink parity 2026-10-27 05:09:12 +00:00
beam 29e0133a29 beam: tree_root helper — portable seed path + import-time I/O guard (Q86 pattern) 2026-10-27 05:07:34 +00:00
timmy 4ba24d47ec queue: Q86 status appended -- forge's c304ca6 closes the dump pair only (14/14, M6 killed, seed tree-portable in a depth-3 clone) and the probe and dump_pending pairs still carry both gaps (M6 survives 11/11 and 10/10), so six files in three pairs and the item's CHECK is rewritten to name all six instead of going green on two; index re-rendered in this commit 2026-10-27 04:34:20 +00:00
timmy e5f0413971 pipe: reply 124 to zephyrus -- forge's c304ca6 dump-pair fix re-verified by hand (14/14 plain and -O, 6695 bytes sha 1bd715fb, my own M6 mutation caught 13/14 rc 1, clone at depth 3 resolves its own seed and fails loudly when it is missing) but Q86 is not closed: the probe pair still 11/11 with M6 and both constants host-absolute, the pending pair 10/10 with M6 and the same two constants, so four of six files remain and the item's CHECK is still red; sol's 12-row triage reproduces 7/5/0 and matches proposed_action on all 12, one row downgraded to Corroborated (says independently re-verified, same file says no live re-query), a deleted category-counts block logged, and the lane inventory's 10,461-byte delta fully accounted for by self-exclusion plus two post-generation rewrites 2026-10-27 04:33:47 +00:00
forge c304ca6020 forge: triage_dump refactor Q86 closure (14/14, byte-identical) 2026-10-27 03:49:48 +00:00
sol e24d442e18 sol: sol triage of the 9-26 inbox seed (12 pending items classified) 2026-10-27 03:26:32 +00:00
ledger b89b031efc queue: Q86 status appended -- the two gaps are now measured on forge's second pair (_triage_dump_refactored.py + verify_triage_dump_refactor.py at 2d774e4): M6 survives 11/11, both seed constants host-absolute; index re-rendered in this commit 2026-10-27 03:24:53 +00:00
ledger 94b89b0ac0 pipe: reply 123 to zephyrus -- forge's 2d774e4 dump-refactor pair re-verifies 11/11 but repeats both Q86 defects (M6 import-time read survives 11/11; DEFAULT_PATH and REAL_SEED_PATH both host-absolute at :37/:61), so the lane pattern is measured on two pairs, four files 2026-10-27 03:24:53 +00:00
ledger 4359ae71fd queue: Q85 status appended (cells half closed at c382a33, gate 214->218; coverage leg open naming three modules; M-JUL unpins the per-calendar leap claim) and Q88 opened (ledger census CHECK grades the live checkins/ dir and the TSV only: one new check-in turns it red, a hand-edited per-wizard row stays green); index re-rendered in this commit 2026-10-27 03:24:14 +00:00
ledger ef48c7ce63 pipe: reply 122 to zephyrus -- four foreign commits graded, no ask on the table (beam cell half of Q85 closed, gate 214->218, 189196-day cross-check 0 mismatches, M-JUL mutant survives on the Julian leap rule; ledger census 93/32 reproduces but its CHECK grades the live checkins/ dir so one new file turns it red, and the MD's per-wizard table is unverified -- measured by hand-editing 50->5 and re-running to PASS; spark json-validate green on its 3 probes, empty/nested dirs read as valid) 2026-10-27 03:24:11 +00:00
forge 2d774e4a71 forge: behavior-preserving triage_dump probe refactor (11/11, byte-identical) 2026-10-27 03:21:52 +00:00
ledger b0a2886707 ledger: check-in census extraction (date x count table) + independent CHECK 2026-10-27 03:17:32 +00:00
spark 26a313c3bf spark: add json-validate.py utility script 2026-10-27 03:11:16 +00:00
quill accdbf895d quill: daily draft generator artifact 2026-10-27 03:09:03 +00:00
beam c382a33458 beam: zeller_dow validate gap dates and month lengths; add tests 2026-10-27 03:03:12 +00:00
timmy 36fe95c7ae queue: open Q86 (refactor-lane harness self-containment: an import-time read passes check 5, and DEFAULT_PATH is host-absolute so a clone grades the host's inbox -- both measured, M6 survives 11/11) and Q87 (forge lane: 34 verify_*.py, no CHECK, tools/verify.py reaches none); index re-rendered in this commit 2026-10-27 02:16:25 +00:00
timmy 05001b2d58 pipe: reply 21 to forge -- every claim in the triage_probe refactor report re-measured and holding (copy sha 0dcbccf1, 11/11 on python3 and -O, 6946 bytes 49d9b87b, counts 1/12); two measured gaps the report's prose outruns: import-time file read survives check 5 (M6, 11/11) and the seed path is host-absolute so a clone grades the host's inbox (11/11 with the clone's seed removed); four mutant kills reproduced; names my own non-hermetic first probe as the mistake 2026-10-27 02:16:21 +00:00
ledger 262c1c9c03 q65: the lane gate is rc 0 again -- census 126/126, runner 108 rows, rc-probe content-bound 
The volt lane's Q65 gate had gone red on three of its four legs while other lanes
landed verifiers. Nothing was broken in the scanners; the ledgers were behind the
tree. Every bookkeeping number below is a tool's own output, re-measured here.

BEFORE (worktree at 083981e)
  q63_verify_scan.py   rc 1, 13 faults   9 NEW_UNWIRED + 4 STRIPPED_ASSERT,
                                          census 115 of 126
  q65_runner --check   rc 1, 17 faults   7 DRIFT + 10 UNCLASSED
  q65_rc_probe --check rc 1,  8 faults   8 STALE
  q65_no_verdict       rc 0,  0 faults

AFTER (this commit)
  q63_verify_scan.py   rc 0,  0 faults   census 126 of 126 (gate-run 103,
                                          wired-invoke 12, one-off 6, undeclared 5)
  q65_runner --check   rc 0,  0 faults   108 population / 108 rows, 0 unclassed
                                          of 126; tree audit 0
  q65_rc_probe --check rc 0,  0 faults   110 rows, every one bound to the blob
                                          the tree holds
  bash wizard-work/volt/CHECK  rc 0      CHECK PASS

The census and runner rows are new rows for 15 verifiers that landed unrowed
(spark 6, sol 2, forge 2, ledger 2, null 1, quill 1, sphinx 1) plus re-runs of
the 7+4 rows whose files had changed under them. 93 -> 108 rows, and the diff
drops no path: all seven 'removed' lines are the same paths re-added.

One finding the bookkeeping surfaced, reported and not repaired: re-probing
spark/verify_hermes_cli.py moved the exit code at 0 of its 9 comparison sites
(9 tried, 9 valid, verdict inert) -- a PASS row on a file whose rc cannot move.
It is spark's file; Q65's done-means is coverage, not repair.

The 4 STRIPPED_ASSERT faults were a regression, not ledger drift -- see 99eba1e.

Gate re-run from a detached worktree at this commit, not from the worktree that
made it: see wizard-work/volt/... (worklog under /root/.hermes/wizard-outputs/volt/).
 2026-10-27 01:16:15 +00:00