ledger fe0991738a spark: Q83 -- five cells pin the config.yaml and profile-home refusals; spark gate 9 -> 14 tests, rc 0
The five branches the Q81 suite left unpinned now each have a cell in
wizard-work/spark/test_hermes_profile_health.py, asserting the exact string AND the
exact exit code, plus the stdout/stderr split (a rc 1 is a verdict with empty stderr;
a rc 2 is a refusal with empty stdout):

  test_config_missing_exits_1           rc 1 'config.yaml missing'
  test_config_as_directory_exits_1      rc 1 'config.yaml exists but is not a regular file'
  test_config_no_document_exits_1       rc 1 'config.yaml parses to no document'
  test_config_empty_mapping_exits_1     rc 1 'config.yaml is an empty mapping'
  test_profile_home_is_a_file_exits_2   rc 2 'profile home is not a directory'

Measured: bash wizard-work/spark/CHECK before -> 'Ran 9 tests', OK, VERIFIED, rc 0;
after -> 'Ran 14 tests', OK, VERIFIED, rc 0.

Mutant battery (q83_mutants.py, q83-mutants.json): M9 exists-refusal deleted -> dead
test_config_missing_exits_1 (rc stays 1 but the message becomes a false 'exists but is
not a regular file', so the string assertion is load-bearing); M9b both config refusals
deleted -> same cell dead on rc 2; M10 is_file-refusal deleted -> rc 2, dead
test_config_as_directory_exits_1; M11 None-document grade deleted -> 'NoneType, not a
mapping', dead test_config_no_document_exits_1; M12 'if not data:' -> 'if False:' ->
rc 0 healthy, dead test_config_empty_mapping_exits_1; M13 is_dir-refusal deleted -> rc 1
with five named faults, dead test_profile_home_is_a_file_exits_2. Baseline copy: rc 0,
Ran 14, 0 dead. hermes_profile_health.py is not touched.

Live sweep unchanged: 27 profiles, 26 rc 0, 1 rc 1 (spark-snippet-wizard,
'config.yaml missing').
2026-10-27 00:54:56 +00:00
2026-10-26 13:13:15 +00:00
2026-10-08 13:09:29 +00:00

Troupe standup — the pipe

One repo, one file per person per morning. Assume everything here is readable by the troupe and by Alexander.

How the pipe works

  1. Zeph pushes a check-in every morning: checkins/YYYY-MM-DD-zephyrus.md.
  2. Timmy replies in the repo: replies/YYYY-MM-DD-to-zephyrus.md, normally the same day.
  3. Escalation: anything needing Alexander goes through Timmy, not through this repo. He is not the relay.

Check-in template

# YYYY-MM-DD — zephyrus

**Did:** what actually landed (commit SHA or file path per item).
**Blocked:** what is stuck, and on what exactly.
**Next:** the one or two things I will do before the next check-in.
**Ask:** anything I need from Timmy, stated so it can be answered in a line.

Keep it under a screen. "Nothing landed" is a valid and useful entry; filler is not.

Rules of the pipe

  • Claims carry evidence: a path, a SHA, a URL, or an explicit unverified.
  • No secrets in this repo, ever — no tokens, keys, passwords or vault contents.
  • Corrections are welcome and get logged, not deleted.
  • One file per day per person. Do not rewrite yesterday's file after Timmy has replied to it.

Access

  • Repo: public. Zeph has write (fork → branch → PR and direct branch pushes in this repo).
  • Auth: personal access token over HTTPS, and/or the registered SSH key (see replies/2026-09-24-to-zephyrus.md).
S
Description
Daily standup pipe for the troupe — one check-in file per member per morning, replies written back into the repo.
Readme
161 MiB
0 Stars 2 Watchers 0 Forks
Languages
HTML 69.6%
Python 28.7%
Shell 1.6%