Files
jason.woltje 6bad02612a lead: commit dewey's untracked evidence (721 files: queue-124-review queue-143 queue-149 queue-165-review queue-170 queue-175 queue-177 queue-184 queue-191)
Unclaimed files left in the canonical checkout. Inventory: canonical-cleanup-inventory.md (commit-as-evidence groups). detect-secrets scan clean on 2026-11-02: hits are sha256 pins, git object ids, test sentinels already in tracked tests and unit-file lines.
2026-11-02 15:05:14 -06:00

123 lines
9.2 KiB
Plaintext
Raw Permalink Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
control-spec-review: exit 0; ℹ tests 12 ℹ pass 12 ℹ fail 0
control-tools: exit 0; ℹ tests 20 ℹ pass 20 ℹ fail 0
control-spec-review-contracts: exit 0; ℹ tests 3 ℹ pass 3 ℹ fail 0
b1-any-path-notifies: exit 1; ℹ tests 12 ℹ pass 11 ℹ fail 1
failed: ✖ failing tests:
failed: ✖ no notice for a docs save, an agent record commit, a git commit outside the Console, or a refused save
b2-pm-only: exit 1; ℹ tests 12 ℹ pass 6 ℹ fail 6
failed: ✖ a BLOCK is refused from anyone but a pm or cto, to anyone but the chief of staff, and outside a reply to its own notice
failed: ✖ a BLOCK reaches the chief of staff, the chief relays it to the assistant in the user's thread, and the commit stands
failed: ✖ a human spec save sends one notice to each pm and cto, naming the commit, and each commit sends its own
failed: ✖ a notice to a role no run holds waits for a claim, and launches nobody and tells nobody
failed: ✖ failing tests:
failed: ✖ no notice for a docs save, an agent record commit, a git commit outside the Console, or a refused save
failed: ✖ with no thread a BLOCK still reaches the chief of staff, and the relay to the assistant is refused
b3-chief-also: exit 1; ℹ tests 12 ℹ pass 7 ℹ fail 5
failed: ✖ a BLOCK reaches the chief of staff, the chief relays it to the assistant in the user's thread, and the commit stands
failed: ✖ a human spec save sends one notice to each pm and cto, naming the commit, and each commit sends its own
failed: ✖ a notice to a role no run holds waits for a claim, and launches nobody and tells nobody
failed: ✖ failing tests:
failed: ✖ no notice for a docs save, an agent record commit, a git commit outside the Console, or a refused save
failed: ✖ with no thread a BLOCK still reaches the chief of staff, and the relay to the assistant is refused
b4-notice-failure-swallowed: exit 1; ℹ tests 12 ℹ pass 11 ℹ fail 1
failed: ✖ a notice that cannot be stored answers outcome-unknown, and the commit stands
failed: ✖ failing tests:
b5-notice-not-routed: exit 1; ℹ tests 12 ℹ pass 11 ℹ fail 1
failed: ✖ a human spec save sends one notice to each pm and cto, naming the commit, and each commit sends its own
failed: ✖ failing tests:
b6-body-omits-reply-id: exit 1; ℹ tests 12 ℹ pass 11 ℹ fail 1
failed: ✖ a human spec save sends one notice to each pm and cto, naming the commit, and each commit sends its own
failed: ✖ failing tests:
b7-body-omits-base: exit 1; ℹ tests 12 ℹ pass 11 ℹ fail 1
failed: ✖ a human spec save sends one notice to each pm and cto, naming the commit, and each commit sends its own
failed: ✖ failing tests:
c1-no-block-check: exit 1; ℹ tests 12 ℹ pass 10 ℹ fail 2
failed: ✖ a BLOCK is refused from anyone but a pm or cto, to anyone but the chief of staff, and outside a reply to its own notice
failed: ✖ a role cannot forge a spec notice: its text opens neither a BLOCK nor the assistant's thread
failed: ✖ failing tests:
c2-any-role-may-block: exit 1; ℹ tests 12 ℹ pass 11 ℹ fail 1
failed: ✖ a BLOCK is refused from anyone but a pm or cto, to anyone but the chief of staff, and outside a reply to its own notice
failed: ✖ failing tests:
c3-any-recipient: exit 1; ℹ tests 12 ℹ pass 11 ℹ fail 1
failed: ✖ a BLOCK is refused from anyone but a pm or cto, to anyone but the chief of staff, and outside a reply to its own notice
failed: ✖ failing tests:
c4-no-reply-required: exit 1; ℹ tests 12 ℹ pass 10 ℹ fail 2
failed: ✖ a BLOCK is refused from anyone but a pm or cto, to anyone but the chief of staff, and outside a reply to its own notice
failed: ✖ a role cannot forge a spec notice: its text opens neither a BLOCK nor the assistant's thread
failed: ✖ failing tests:
c5-other-roles-notice: exit 1; ℹ tests 12 ℹ pass 11 ℹ fail 1
failed: ✖ a BLOCK is refused from anyone but a pm or cto, to anyone but the chief of staff, and outside a reply to its own notice
failed: ✖ failing tests:
c6-forged-notice-accepted: exit 1; ℹ tests 12 ℹ pass 11 ℹ fail 1
failed: ✖ a role cannot forge a spec notice: its text opens neither a BLOCK nor the assistant's thread
failed: ✖ failing tests:
c7-any-bus-notice: exit 1; ℹ tests 12 ℹ pass 11 ℹ fail 1
failed: ✖ a BLOCK is refused from anyone but a pm or cto, to anyone but the chief of staff, and outside a reply to its own notice
failed: ✖ failing tests:
c8-block-class-not-offered: exit 1; ℹ tests 12 ℹ pass 6 ℹ fail 6
failed: ✖ a BLOCK is refused from anyone but a pm or cto, to anyone but the chief of staff, and outside a reply to its own notice
failed: ✖ a BLOCK reaches the chief of staff, the chief relays it to the assistant in the user's thread, and the commit stands
failed: ✖ a more recently opened thread in another project does not take the relay
failed: ✖ a role cannot forge a spec notice: its text opens neither a BLOCK nor the assistant's thread
failed: ✖ failing tests:
failed: ✖ within the notice's project the relay lands in the user's most recently opened thread
failed: ✖ with no thread a BLOCK still reaches the chief of staff, and the relay to the assistant is refused
t1-no-notice-chain: exit 1; ℹ tests 12 ℹ pass 9 ℹ fail 3
failed: ✖ a BLOCK reaches the chief of staff, the chief relays it to the assistant in the user's thread, and the commit stands
failed: ✖ a more recently opened thread in another project does not take the relay
failed: ✖ failing tests:
failed: ✖ within the notice's project the relay lands in the user's most recently opened thread
t2-forged-notice-opens-thread: exit 1; ℹ tests 12 ℹ pass 11 ℹ fail 1
failed: ✖ a role cannot forge a spec notice: its text opens neither a BLOCK nor the assistant's thread
failed: ✖ failing tests:
t3-any-bus-notice-opens-thread: exit 0; ℹ tests 12 ℹ pass 12 ℹ fail 0
t4-oldest-thread: exit 1; ℹ tests 12 ℹ pass 11 ℹ fail 1
failed: ✖ failing tests:
failed: ✖ within the notice's project the relay lands in the user's most recently opened thread
t5-ignores-opens: exit 1; ℹ tests 12 ℹ pass 11 ℹ fail 1
failed: ✖ failing tests:
failed: ✖ within the notice's project the relay lands in the user's most recently opened thread
t6-any-owner: exit 1; ℹ tests 12 ℹ pass 8 ℹ fail 4
failed: ✖ a BLOCK reaches the chief of staff, the chief relays it to the assistant in the user's thread, and the commit stands
failed: ✖ a more recently opened thread in another project does not take the relay
failed: ✖ failing tests:
failed: ✖ within the notice's project the relay lands in the user's most recently opened thread
failed: ✖ with no thread a BLOCK still reaches the chief of staff, and the relay to the assistant is refused
t7-any-project: exit 1; ℹ tests 12 ℹ pass 11 ℹ fail 1
failed: ✖ a more recently opened thread in another project does not take the relay
failed: ✖ failing tests:
h1-tool-lacks-block: exit 1; ℹ tests 20 ℹ pass 19 ℹ fail 1
failed: ✖ failing tests:
failed: ✖ send_message offers the BLOCK class, beside the classes it already had
r1-pm-no-read_spec: exit 1; ℹ tests 3 ℹ pass 2 ℹ fail 1
failed: ✖ failing tests:
failed: ✖ the pm and the cto check a saved spec against settled decisions and work in flight, and answer with a BLOCK or an accept
r2-cto-no-block-class: exit 1; ℹ tests 3 ℹ pass 2 ℹ fail 1
failed: ✖ failing tests:
failed: ✖ the pm and the cto check a saved spec against settled decisions and work in flight, and answer with a BLOCK or an accept
r3-pm-revert-claim: exit 1; ℹ tests 3 ℹ pass 2 ℹ fail 1
failed: ✖ failing tests:
failed: ✖ the pm and the cto check a saved spec against settled decisions and work in flight, and answer with a BLOCK or an accept
r4-cto-no-accept: exit 1; ℹ tests 3 ℹ pass 2 ℹ fail 1
failed: ✖ failing tests:
failed: ✖ the pm and the cto check a saved spec against settled decisions and work in flight, and answer with a BLOCK or an accept
r5-assistant-quotes: exit 1; ℹ tests 3 ℹ pass 2 ℹ fail 1
failed: ✖ failing tests:
failed: ✖ the assistant summarizes a spec review in its own words and doesn't repeat the chief of staff's text
r6-assistant-no-summary: exit 1; ℹ tests 3 ℹ pass 2 ℹ fail 1
failed: ✖ failing tests:
failed: ✖ the assistant summarizes a spec review in its own words and doesn't repeat the chief of staff's text
r7-pm-no-assistant-path: exit 1; ℹ tests 3 ℹ pass 2 ℹ fail 1
failed: ✖ failing tests:
failed: ✖ the pm and the cto check a saved spec against settled decisions and work in flight, and answer with a BLOCK or an accept
r8-chief-no-reply-link: exit 1; ℹ tests 3 ℹ pass 2 ℹ fail 1
failed: ✖ failing tests:
failed: ✖ the chief of staff relays a BLOCK or an accept to the assistant as a reply to the message that carried it
r9-chief-no-refusal-reason: exit 1; ℹ tests 3 ℹ pass 2 ℹ fail 1
failed: ✖ failing tests:
failed: ✖ the chief of staff relays a BLOCK or an accept to the assistant as a reply to the message that carried it
r10-chief-no-block-note: exit 1; ℹ tests 3 ℹ pass 2 ℹ fail 1
failed: ✖ failing tests:
failed: ✖ the chief of staff relays a BLOCK or an accept to the assistant as a reply to the message that carried it
done