diff options
| author | Craig Jennings <c@cjennings.net> | 2026-07-23 08:25:40 -0500 |
|---|---|---|
| committer | Craig Jennings <c@cjennings.net> | 2026-07-23 08:25:40 -0500 |
| commit | 01356fa036847f9d216dd92a006049105c2d5461 (patch) | |
| tree | 4034b455c1a98a8b67e5ebb5ba8976e707055fc6 /working/interaction-no-markup/proposal-from-org-drill.org | |
| parent | 33949c50b7d2b3ab01af4fe91119cc290fae9f01 (diff) | |
| download | rulesets-01356fa036847f9d216dd92a006049105c2d5461.tar.gz rulesets-01356fa036847f9d216dd92a006049105c2d5461.zip | |
chore: file eight bug findings and stage four shared-asset proposals
Overnight hygiene sweep of this repo. Everything here is a finding or a staged proposal. No rule, workflow, script, or bundle file was modified.
The one that matters: the python and typescript language bundles ship no pre-commit hook, so a project installing either gets no credential scan on commit. Both bundles predate the hook rollout that swept go and bash, and install-lang skips missing components without a word, so it went unnoticed for two months. Live on two projects, one of them work. Filed [#A].
Seven more findings landed. The largest is a non-atomic write in the cross-project inbox tool, which can strand an empty handoff in another project's inbox and block a turn there. The rest are lint noise and two gaps in the Signal channel. An eighth was filed and then retracted the same night, once a retest showed I had compared two different files and read the difference as a bug.
Four proposals from other projects are staged under working/ with verified diffs, each behind a VERIFY task, waiting on a decision.
Diffstat (limited to 'working/interaction-no-markup/proposal-from-org-drill.org')
| -rw-r--r-- | working/interaction-no-markup/proposal-from-org-drill.org | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/working/interaction-no-markup/proposal-from-org-drill.org b/working/interaction-no-markup/proposal-from-org-drill.org new file mode 100644 index 0000000..09f0845 --- /dev/null +++ b/working/interaction-no-markup/proposal-from-org-drill.org @@ -0,0 +1,5 @@ +#+TITLE: Proposal: sharpen interaction.md's 'No Reverse-Video Highlig +#+SOURCE: from org-drill +#+DATE: 2026-07-21 00:06:48 -0500 + +Proposal: sharpen interaction.md's 'No Reverse-Video Highlighting in Chat Output' rule. Craig's feedback in org-drill (2026-05-30, saved as a harness memory there): chat output must have zero markup — no code fences, no bold, no backtick spans, ever ('always always list it out without markup'). The current rule bans bold and inline-code spans but says fenced code blocks 'are acceptable when the user explicitly wants a block to copy'. Craig's directive tightens that: default to plain text always; no fences either. Suggest updating the rule text so every project inherits it instead of it living as one project's memory. Evidence: org-drill memory file no-markup-chat-output.md and the 2026-05-30 session log there. |