Skip to content

WIP {!} logan/obsidian (spiritual successor to the late #563) - #926

Closed
github-actions[bot] wants to merge 3001 commits into
mainfrom
logan/obsidian
Closed

github-actions[bot] wants to merge 3001 commits into
mainfrom
logan/obsidian

Conversation

@github-actions

@github-actions github-actions Bot commented Aug 4, 2026

Copy link
Copy Markdown
Contributor

Auto-generated PR

Agent: logan
Lifecycle: staged
Label: none

Diff stat

 .agent/AGENT.md                                    |     7 +
 .agent/stub.txt                                    |     1 +
 .claude.json (2).backup                            |   925 +
 .claude.json (3).backup                            |   573 +
 .claude.json.backup (2).1781662524583              |   933 +
 .claude.json.backup (2).1781662589691              |   933 +
 .claude.json.backup (2).1781662653764              |   933 +
 .claude.json.backup (2).1781662729639              |   933 +
 .claude.json.backup (2).1781670949591              |     3 +
 .claude.json.backup.1776645410704                  |   628 +
 .claude.json.backup.1776645490433                  |   628 +
 .claude.json.backup.1776645970206                  |   629 +
 .claude.json.backup.1776654503884                  |   629 +
 .claude.json.backup.1776654631477                  |   629 +
 .claude.json.backup.1781662524583                  |   933 +
 .claude.json.backup.1781662589691                  |   933 +
 .claude.json.backup.1781662653764                  |   933 +
 .claude.json.backup.1781662729639                  |   933 +
 .claude.json.backup.1781670949591                  |     3 +
 .codex-global-state.json                           |     1 +
 .codex-global-state.json.bak                       |     1 +
 .crewai/5WIZARDS-DRAFT.md                          |   565 -
 .crewai/manifest.json                              |    31 -
 .../.cursor-managed-skills-manifest.json           |    15 -
 .cursor/skills-cursor/babysit/SKILL.md             |    15 -
 .cursor/skills-cursor/create-hook/SKILL.md         |   239 -
 .cursor/skills-cursor/create-rule/SKILL.md         |   166 -
 .cursor/skills-cursor/create-skill/SKILL.md        |   514 -
 .cursor/skills-cursor/create-subagent/SKILL.md     |   228 -
 .cursor/skills-cursor/migrate-to-skills/SKILL.md   |   135 -
 .cursor/skills-cursor/shell/SKILL.md               |    24 -
 .cursor/skills-cursor/statusline/SKILL.md          |   194 -
 .cursor/skills-cursor/update-cli-config/SKILL.md   |   104 -
 .../skills-cursor/update-cursor-settings/SKILL.md  |   124 -
 .gitignore                                         |    35 +-
 .obsidian/file-recovery.json                       |     4 +
 .../registry.ollama.ai/library/devstral/latest     |     1 +
 .../registry.ollama.ai/library/gemma4/latest       |     1 +
 .../registry.ollama.ai/library/gpt-oss/latest      |     1 +
 .../registry.ollama.ai/library/llama3.2-vision/90b |     1 +
 .../registry.ollama.ai/library/magistral/latest    |     1 +
 .../library/mistral-large/latest                   |     1 +
 .../registry.ollama.ai/library/mistral-nemo/latest |     1 +
 .../library/mistral-small/latest                   |     1 +
 .../library/mistral/7b-instruct-q4_K_M             |     1 +
 .../registry.ollama.ai/library/mistral/latest      |     1 +
 .../registry.ollama.ai/library/mixtral/latest      |     1 +
 .../registry.ollama.ai/library/nemotron/latest     |     1 +
 .../registry.ollama.ai/library/qwen/latest         |     1 +
 .op/1password-hygiene-policy.json                  |    73 -
 .op/OP.md                                          |    18 +-
 .op/SETUP.md                                       |   233 -
 .op/openrouter.env.template                        |    11 -
 .op/secrets.template.md                            |   177 -
 .personality_migration                             |     1 +
 .pycache/PYCACHE.md                                |    31 +
 .pycache/stub.txt                                  |     1 +
 .pytest/PYTEST.md                                  |    31 +
 .pytest/stub.txt                                   |     1 +
 .smart-env/embedding_models/embedding_models.ajson |     2 +
 .smart-env/event_logs/event_logs.ajson             |    34 +
 .space/waypoints.json                              |     1 +
 .vscode-shared/VSCODE-SHARED.md                    |     7 +-
 ...World_ A Native American Perspective of Evil.md |    66 +
 ...e Boise State_UNLV game see tickets canceled.md |    80 +
 ...fuel storage \342\200\242 Idaho Capital Sun.md" |    62 +
 ... renaissance \342\200\242 Idaho Capital Sun.md" |    48 +
 2026-03-24-mcp-coordination-update.md              |    49 +
 2026-03-24-mcp-pr-prep.md                          |    44 +
 2026-04-03 (3).md                                  |    31 +
 ...rance could raise members' health care costs.md |    67 +
 ...eaders look at expansion & improvement plans.md |    68 +
 ...laims; insurer calls allegations sensational.md |   106 +
 ...ring Regence deal ahead of June 15 deadline.md" |    48 +
 ...te employees \342\200\242 Idaho Capital Sun.md" |    61 +
 ...Regence split leaves patients out of network.md |    38 +
 ...ion_ Freelancers discuss the keys to success.md |    68 +
 ...ands Out in a Blockbuster Supreme Court Term.md |    34 +
 ...ts Raise New Questions for States and Tribes.md |    60 +
 ...sagree. Let\342\200\231s Just Do It Better..md" |    56 +
 ... Boise State launches search for new provost.md |    24 +
 ...ds campaign for US Senate seat held by Risch.md |    47 +
 ...n Faulkner_ The legacy of an Idaho rock star.md |    28 +
 ...s. Soon, 52 affordable homes will rise there.md |    38 +
 ...rump\342\200\231s Administration Priorities.md" |    38 +
 ...red schedule to ease bus, traffic challenges.md |    34 +
 ...200\231s misspelling reveals a deeper truth.md" |    32 +
 ... grow_ 45-acre mushroom farm listed for sale.md |    54 +
 ...ute creates STEM pipeline for high schoolers.md |    18 +
 ...case means thousands could get bond hearings.md |    66 +
 ... Warns About Its Perils, Praises Its Promise.md |    44 +
 ...-30 - Want to Be Persuasive_ Be Persuadable..md |    46 +
 ... access tips \342\200\242 Idaho Capital Sun.md" |    29 +
 ...nts at Nampa construction site, DHS confirms.md |    42 +
 ...nce February \342\200\242 Idaho Capital Sun.md" |    66 +
 ... Medicaid work rules \342\200\242 Stateline.md" |    34 +
 ...s are reshaping Belize\342\200\231s forests.md" |   211 +
 ...r adults and workers \342\200\242 Stateline.md" |    28 +
 ...31 - Record first-year class enrolls at ICOM.md |    22 +
 ...ers to gather in Boise for annual conference.md |    28 +
 ... identified as Payette Lake drowning victim.md" |    86 +
 ...even sent to hospital for heat issues Friday.md |    56 +
 ...Bears Ears Monument Cuts Spark Tribe Outrage.md |    80 +
 2026-08-02 - Building permit fees could rise.md    |    40 +
 ... An Idaho law saved it tens of millions more.md |   142 +
 ...2\200\224 and claim the $1,000 contribution.md" |    62 +
 ...lth insurers \342\200\242 Idaho Capital Sun.md" |    50 +
 ...ly had any idea it would be that successful'.md |   198 +
 ... of eastern Idaho, as wildfire smoke lingers.md |    44 +
 ...s Lake Channel Fire reaches full containment.md |    38 +
 ...aste\302\240 \342\200\242 Idaho Capital Sun.md" |    82 +
 ...3 - New schools are set to open across Idaho.md |   120 +
 ...he worst\342\200\231 \342\200\242 Stateline.md" |    66 +
 ...me Spokane residents can return after fires.md" |    43 +
 AGENT-BOOTSTRAP-EXPLORER-COMPANION-2026-04-13.md   |    81 +
 AGENTS (75).md                                     |     1 +
 JOURNAL-PAGE-1 (2).md                              |    78 +
 JOURNAL-PAGE-2 (2).md                              |   111 +
 JOURNAL-PAGE-3 (2).md                              |    90 +
 JOURNAL-PAGE-4 (2).md                              |    91 +
 JOURNAL-PAGE-5 (2).md                              |    82 +
 JOURNAL-PAGE-6 (2).md                              |    80 +
 JOURNAL-PAGE-7 (2).md                              |   101 +
 JOURNAL-PAGE-8 (2).md                              |    73 +
 LOGIC-PUZZLE-REGISTRATION (2).md                   |   413 +
 LOGIC-PUZZLE-RESEARCH (2).md                       |   701 +
 LOGIC-PUZZLE-ROSTER (2).md                         |   605 +
 .crewai/MANIFEST.md => MANIFEST.md                 |     0
 MEMORY (2).md                                      |    35 +
 MEMORY (3).md                                      |    35 +
 MEMORY (4).md                                      |    38 +
 Map.webp                                           |     3 +
 .crewai/TRAINING.md => TRAINING.md                 |     0
 __about__.cpython-314 (2).pyc                      |   Bin 0 -> 214 bytes
 __about__.cpython-314.pyc                          |   Bin 0 -> 214 bytes
 __check_syntax__.cpython-313.pyc                   |   Bin 0 -> 2638 bytes
 __check_syntax__.cpython-314.pyc                   |   Bin 0 -> 3062 bytes
 .crewai/crews/__init__.py => __init__ (2).py       |     0
 .crewai/tools/__init__.py => __init__ (3).py       |     0
 __init__.cpython-313 (2).pyc                       |   Bin 0 -> 154 bytes
 __init__.cpython-313 (3).pyc                       |   Bin 0 -> 160 bytes
 __init__.cpython-313 (4).pyc                       |   Bin 0 -> 160 bytes
 __init__.cpython-313.pyc                           |   Bin 0 -> 272 bytes
 __init__.cpython-314 (10).pyc                      |   Bin 0 -> 195 bytes
 __init__.cpython-314 (11).pyc                      |   Bin 0 -> 195 bytes
 __init__.cpython-314 (12).pyc                      |   Bin 0 -> 202 bytes
 __init__.cpython-314 (13).pyc                      |   Bin 0 -> 202 bytes
 __init__.cpython-314 (14).pyc                      |   Bin 0 -> 195 bytes
 __init__.cpython-314 (15).pyc                      |   Bin 0 -> 192 bytes
 __init__.cpython-314 (16).pyc                      |   Bin 0 -> 192 bytes
 __init__.cpython-314 (17).pyc                      |   Bin 0 -> 201 bytes
 __init__.cpython-314 (18).pyc                      |   Bin 0 -> 208 bytes
 __init__.cpython-314 (19).pyc                      |   Bin 0 -> 208 bytes
 __init__.cpython-314 (2).pyc                       |   Bin 0 -> 190 bytes
 __init__.cpython-314 (20).pyc                      |   Bin 0 -> 201 bytes
 __init__.cpython-314 (21).pyc                      |   Bin 0 -> 194 bytes
 __init__.cpython-314 (22).pyc                      |   Bin 0 -> 208 bytes
 __init__.cpython-314 (23).pyc                      |   Bin 0 -> 208 bytes
 __init__.cpython-314 (24).pyc                      |   Bin 0 -> 201 bytes
 __init__.cpython-314 (25).pyc                      |   Bin 0 -> 201 bytes
 __init__.cpython-314 (26).pyc                      |   Bin 0 -> 194 bytes
 __init__.cpython-314 (27).pyc                      |   Bin 0 -> 186 bytes
 __init__.cpython-314 (28).pyc                      |   Bin 0 -> 186 bytes
 __init__.cpython-314 (29).pyc                      |   Bin 0 -> 193 bytes
 __init__.cpython-314 (3).pyc                       |   Bin 0 -> 202 bytes
 __init__.cpython-314 (30).pyc                      |   Bin 0 -> 193 bytes
 __init__.cpython-314 (31).pyc                      |   Bin 0 -> 1439 bytes
 __init__.cpython-314 (32).pyc                      |   Bin 0 -> 1439 bytes
 __init__.cpython-314 (33).pyc                      |   Bin 0 -> 190 bytes
 __init__.cpython-314 (34).pyc                      |   Bin 0 -> 190 bytes
 __init__.cpython-314 (35).pyc                      |   Bin 0 -> 532 bytes
 __init__.cpython-314 (36).pyc                      |   Bin 0 -> 428 bytes
 __init__.cpython-314 (37).pyc                      |   Bin 0 -> 428 bytes
 __init__.cpython-314 (38).pyc                      |   Bin 0 -> 1476 bytes
 __init__.cpython-314 (39).pyc                      |   Bin 0 -> 551 bytes
 __init__.cpython-314 (4).pyc                       |   Bin 0 -> 202 bytes
 __init__.cpython-314 (40).pyc                      |   Bin 0 -> 5922 bytes
 __init__.cpython-314 (41).pyc                      |   Bin 0 -> 5922 bytes
 __init__.cpython-314 (42).pyc                      |   Bin 0 -> 551 bytes
 __init__.cpython-314 (43).pyc                      |   Bin 0 -> 485 bytes
 __init__.cpython-314 (44).pyc                      |   Bin 0 -> 191 bytes
 __init__.cpython-314 (45).pyc                      |   Bin 0 -> 191 bytes
 __init__.cpython-314 (46).pyc                      |   Bin 0 -> 201 bytes
 __init__.cpython-314 (47).pyc                      |   Bin 0 -> 208 bytes
 __init__.cpython-314 (48).pyc                      |   Bin 0 -> 208 bytes
 __init__.cpython-314 (49).pyc                      |   Bin 0 -> 201 bytes
 __init__.cpython-314 (5).pyc                       |   Bin 0 -> 195 bytes
 __init__.cpython-314 (50).pyc                      |   Bin 0 -> 2506 bytes
 __init__.cpython-314 (51).pyc                      |   Bin 0 -> 2506 bytes
 __init__.cpython-314 (52).pyc                      |   Bin 0 -> 2897 bytes
 __init__.cpython-314 (53).pyc                      |   Bin 0 -> 2897 bytes
 __init__.cpython-314 (54).pyc                      |   Bin 0 -> 5564 bytes
 __init__.cpython-314 (55).pyc                      |   Bin 0 -> 3040 bytes
 __init__.cpython-314 (56).pyc                      |   Bin 0 -> 3040 bytes
 __init__.cpython-314 (57).pyc                      |   Bin 0 -> 5564 bytes
 __init__.cpython-314 (58).pyc                      |   Bin 0 -> 55409 bytes
 __init__.cpython-314 (59).pyc                      |   Bin 0 -> 55409 bytes
 __init__.cpython-314 (6).pyc                       |   Bin 0 -> 195 bytes
 __init__.cpython-314 (60).pyc                      |   Bin 0 -> 753 bytes
 __init__.cpython-314 (61).pyc                      |   Bin 0 -> 1076 bytes
 __init__.cpython-314 (62).pyc                      |   Bin 0 -> 1076 bytes
 __init__.cpython-314 (63).pyc                      |   Bin 0 -> 753 bytes
 __init__.cpython-314 (64).pyc                      |   Bin 0 -> 859 bytes
 __init__.cpython-314 (65).pyc                      |   Bin 0 -> 859 bytes
 __init__.cpython-314 (66).pyc                      |   Bin 0 -> 1476 bytes
 __init__.cpython-314 (67).pyc                      |   Bin 0 -> 205 bytes
 __init__.cpython-314 (68).pyc                      |   Bin 0 -> 205 bytes
 __init__.cpython-314 (69).pyc                      |   Bin 0 -> 199 bytes
 __init__.cpython-314 (7).pyc                       |   Bin 0 -> 299 bytes
 __init__.cpython-314 (70).pyc                      |   Bin 0 -> 199 bytes
 __init__.cpython-314 (71).pyc                      |   Bin 0 -> 202 bytes
 __init__.cpython-314 (72).pyc                      |   Bin 0 -> 202 bytes
 __init__.cpython-314 (73).pyc                      |   Bin 0 -> 335 bytes
 __init__.cpython-314 (74).pyc                      |   Bin 0 -> 335 bytes
 __init__.cpython-314 (75).pyc                      |   Bin 0 -> 532 bytes
 __init__.cpython-314 (76).pyc                      |   Bin 0 -> 485 bytes
 __init__.cpython-314 (8).pyc                       |   Bin 0 -> 299 bytes
 __init__.cpython-314 (9).pyc                       |   Bin 0 -> 195 bytes
 __init__.cpython-314.pyc                           |   Bin 0 -> 190 bytes
 .crewai/__init__.py => __init__.py                 |     0
 __main__.cpython-314 (2).pyc                       |   Bin 0 -> 369 bytes
 __main__.cpython-314 (3).pyc                       |   Bin 0 -> 665 bytes
 __main__.cpython-314 (4).pyc                       |   Bin 0 -> 665 bytes
 __main__.cpython-314.pyc                           |   Bin 0 -> 369 bytes
 __pycache__-__init__.cpython-313.pyc               |   Bin 0 -> 152 bytes
 __pycache__-app.cpython-313.pyc                    |   Bin 0 -> 5874 bytes
 ...che__-resolve_openrouter_secret.cpython-313.pyc |   Bin 0 -> 5604 bytes
 __pycache__-twitter-extract.cpython-313.pyc        |   Bin 0 -> 13984 bytes
 __pycache__/importlib.cpython-312.pyc              |   Bin 0 -> 595 bytes
 __pycache__/importlib.cpython-313.pyc              |   Bin 0 -> 553 bytes
 __pycache__/tarfile.cpython-313.pyc                |   Bin 0 -> 1125 bytes
 _base.cpython-314 (2).pyc                          |   Bin 0 -> 1887 bytes
 _base.cpython-314 (3).pyc                          |   Bin 0 -> 2215 bytes
 _base.cpython-314 (4).pyc                          |   Bin 0 -> 2215 bytes
 _base.cpython-314.pyc                              |   Bin 0 -> 1887 bytes
 _callers.cpython-314 (2).pyc                       |   Bin 0 -> 7814 bytes
 _callers.cpython-314.pyc                           |   Bin 0 -> 7814 bytes
 _elffile.cpython-314 (2).pyc                       |   Bin 0 -> 5614 bytes
 _elffile.cpython-314.pyc                           |   Bin 0 -> 5614 bytes
 _hooks.cpython-314 (2).pyc                         |   Bin 0 -> 32378 bytes
 _hooks.cpython-314.pyc                             |   Bin 0 -> 32378 bytes
 _impl.cpython-314 (2).pyc                          |   Bin 0 -> 21696 bytes
 _impl.cpython-314.pyc                              |   Bin 0 -> 21696 bytes
 _in_process.cpython-314 (2).pyc                    |   Bin 0 -> 15914 bytes
 _in_process.cpython-314.pyc                        |   Bin 0 -> 15914 bytes
 _mainjsweep.cpython-314.pyc                        |   Bin 0 -> 7479 bytes
 _manager.cpython-314 (2).pyc                       |   Bin 0 -> 31039 bytes
 _manager.cpython-314.pyc                           |   Bin 0 -> 31039 bytes
 _manylinux.cpython-314 (2).pyc                     |   Bin 0 -> 12051 bytes
 _manylinux.cpython-314.pyc                         |   Bin 0 -> 12051 bytes
 _meta.cpython-314 (2).pyc                          |   Bin 0 -> 4047 bytes
 _meta.cpython-314.pyc                              |   Bin 0 -> 4047 bytes
 _musllinux.cpython-314 (2).pyc                     |   Bin 0 -> 5146 bytes
 _musllinux.cpython-314.pyc                         |   Bin 0 -> 5146 bytes
 _parser.cpython-314 (2).pyc                        |   Bin 0 -> 19774 bytes
 _parser.cpython-314.pyc                            |   Bin 0 -> 19774 bytes
 _phone-link-sweep.log                              |     5 +
 _phone-link-watcher (2).log                        |     2 +
 _phone-link-watcher.log                            |   995 +
 _pr128jsweep.cpython-314.pyc                       |   Bin 0 -> 9979 bytes
 _result.cpython-314 (2).pyc                        |   Bin 0 -> 5144 bytes
 _result.cpython-314.pyc                            |   Bin 0 -> 5144 bytes
 _spdx.cpython-314 (2).pyc                          |   Bin 0 -> 54711 bytes
 _spdx.cpython-314.pyc                              |   Bin 0 -> 54711 bytes
 _structures.cpython-314 (2).pyc                    |   Bin 0 -> 1986 bytes
 _structures.cpython-314.pyc                        |   Bin 0 -> 1986 bytes
 _tokenizer.cpython-314 (2).pyc                     |   Bin 0 -> 9932 bytes
 _tokenizer.cpython-314.pyc                         |   Bin 0 -> 9932 bytes
 _tracing.cpython-314 (2).pyc                       |   Bin 0 -> 5567 bytes
 _tracing.cpython-314.pyc                           |   Bin 0 -> 5567 bytes
 _typing.cpython-314 (2).pyc                        |   Bin 0 -> 3485 bytes
 _typing.cpython-314.pyc                            |   Bin 0 -> 3485 bytes
 _utils.cpython-314 (2).pyc                         |   Bin 0 -> 1815 bytes
 _utils.cpython-314.pyc                             |   Bin 0 -> 1815 bytes
 _version.cpython-314 (2).pyc                       |   Bin 0 -> 1057 bytes
 _version.cpython-314 (3).pyc                       |   Bin 0 -> 267 bytes
 _version.cpython-314 (4).pyc                       |   Bin 0 -> 267 bytes
 _version.cpython-314.pyc                           |   Bin 0 -> 1057 bytes
 _warnings.cpython-314 (2).pyc                      |   Bin 0 -> 1331 bytes
 _warnings.cpython-314.pyc                          |   Bin 0 -> 1331 bytes
 agent-auto-pr.yml                                  |   225 +
 agent-review-gate.yml                              |   117 +
 agg.cpython-314 (2).pyc                            |   Bin 0 -> 3704 bytes
 agg.cpython-314.pyc                                |   Bin 0 -> 3704 bytes
 ai-code-tracking.db                                |     3 +
 ansi.cpython-314 (2).pyc                           |   Bin 0 -> 4155 bytes
 ansi.cpython-314.pyc                               |   Bin 0 -> 4155 bytes
 ansi_test.cpython-314 (2).pyc                      |   Bin 0 -> 5576 bytes
 ansi_test.cpython-314.pyc                          |   Bin 0 -> 5576 bytes
 ansitowin32.cpython-314 (2).pyc                    |   Bin 0 -> 17095 bytes
 ansitowin32.cpython-314.pyc                        |   Bin 0 -> 17095 bytes
 ansitowin32_test.cpython-314 (2).pyc               |   Bin 0 -> 18317 bytes
 ansitowin32_test.cpython-314.pyc                   |   Bin 0 -> 18317 bytes
 app.cpython-313.pyc                                |   Bin 0 -> 5874 bytes
 app.cpython-314 (2).pyc                            |   Bin 0 -> 1318 bytes
 app.cpython-314 (3).pyc                            |   Bin 0 -> 7999 bytes
 app.cpython-314 (4).pyc                            |   Bin 0 -> 7999 bytes
 app.cpython-314.pyc                                |   Bin 0 -> 1318 bytes
 appearance.json                                    |     4 +
 apply_patch.bat                                    |     2 +
 applypatch.bat                                     |     2 +
 ...ve-__pycache__-__check_syntax__.cpython-313.pyc |   Bin 0 -> 2638 bytes
 ...e-__pycache__-doctrinal_flatten.cpython-313.pyc |   Bin 0 -> 14963 bytes
 archive-__pycache__-main.cpython-313.pyc           |   Bin 0 -> 884 bytes
 archive-__pycache__-run_checks.cpython-313.pyc     |   Bin 0 -> 3433 bytes
 archive-__pycache__-sort_audit (2).cpython-313.pyc |   Bin 0 -> 19233 bytes
 archive-__pycache__-sort_audit.cpython-313.pyc     |   Bin 0 -> 19229 bytes
 ...t__src_scratch-folder__cd1728fd.cpython-313.pyc |   Bin 0 -> 19259 bytes
 ...t__src_scratch-folder__ef10c025.cpython-313.pyc |   Bin 0 -> 19259 bytes
 ...ipts-__pycache__-health_monitor.cpython-313.pyc |   Bin 0 -> 7168 bytes
 ...-__pycache__-openrouter_runtime.cpython-313.pyc |   Bin 0 -> 8151 bytes
 ...he__-render_flatten_attribution.cpython-313.pyc |   Bin 0 -> 6080 bytes
 ...cache__-start_claude_openrouter.cpython-313.pyc |   Bin 0 -> 625 bytes
 ...ycache__-start_codex_openrouter.cpython-313.pyc |   Bin 0 -> 623 bytes
 ...-__pycache__-validate_bootstrap.cpython-313.pyc |   Bin 0 -> 9089 bytes
 ...__pycache__-validate_openrouter.cpython-313.pyc |   Bin 0 -> 8343 bytes
 ...s-__pycache__-validate_services.cpython-313.pyc |   Bin 0 -> 6941 bytes
 ...ts-__pycache__-vault-pheromones.cpython-313.pyc |   Bin 0 -> 35040 bytes
 ...daho_vault-__pycache__-__init__.cpython-313.pyc |   Bin 0 -> 234 bytes
 ...-__pycache__-bootstrap_contract.cpython-313.pyc |   Bin 0 -> 11245 bytes
 ...ault-__pycache__-civic_scaffold.cpython-313.pyc |   Bin 0 -> 20374 bytes
 ...rc-idaho_vault-__pycache__-crew.cpython-313.pyc |   Bin 0 -> 2382 bytes
 ...rc-idaho_vault-__pycache__-main.cpython-313.pyc |   Bin 0 -> 13046 bytes
 ...daho_vault-__pycache__-mock_llm.cpython-313.pyc |   Bin 0 -> 3154 bytes
 ...lt-__pycache__-operator_context.cpython-313.pyc |   Bin 0 -> 14221 bytes
 ...idaho_vault-__pycache__-runtime.cpython-313.pyc |   Bin 0 -> 2573 bytes
 ...aho_vault-__pycache__-sparkseed.cpython-313.pyc |   Bin 0 -> 11663 bytes
 ...ve_wizards-__pycache__-__init__.cpython-313.pyc |   Bin 0 -> 4780 bytes
 ...-five_wizards-__pycache__-enums.cpython-313.pyc |   Bin 0 -> 10750 bytes
 ...wizards-__pycache__-lane_runner.cpython-313.pyc |   Bin 0 -> 20714 bytes
 ...five_wizards-__pycache__-models.cpython-313.pyc |   Bin 0 -> 22338 bytes
 ...e_wizards-__pycache__-pipelines.cpython-313.pyc |   Bin 0 -> 17071 bytes
 ...e_wizards-__pycache__-renderers.cpython-313.pyc |   Bin 0 -> 26207 bytes
 ...ive_wizards-__pycache__-service.cpython-313.pyc |   Bin 0 -> 5518 bytes
 ...ive_wizards-__pycache__-staging.cpython-313.pyc |   Bin 0 -> 14250 bytes
 ...ds-__pycache__-threshold_runner.cpython-313.pyc |   Bin 0 -> 16691 bytes
 ..._wizards-__pycache__-validators.cpython-313.pyc |   Bin 0 -> 9290 bytes
 ...e_wizards-__pycache__-what_lane.cpython-313.pyc |   Bin 0 -> 2560 bytes
 ...e_wizards-__pycache__-when_lane.cpython-313.pyc |   Bin 0 -> 2561 bytes
 ..._wizards-__pycache__-where_lane.cpython-313.pyc |   Bin 0 -> 2592 bytes
 ...ve_wizards-__pycache__-who_lane.cpython-313.pyc |   Bin 0 -> 2540 bytes
 ...ve_wizards-__pycache__-why_lane.cpython-313.pyc |   Bin 0 -> 2536 bytes
 ...ve_wizards-__pycache__-workflow.cpython-313.pyc |   Bin 0 -> 10343 bytes
 ...che__-test_backfill_daily_notes.cpython-313.pyc |   Bin 0 -> 7643 bytes
 ...__pycache__-test_civic_scaffold.cpython-313.pyc |   Bin 0 -> 10598 bytes
 ...__pycache__-test_daily_rollover.cpython-313.pyc |   Bin 0 -> 13666 bytes
 ...ycache__-test_doctrinal_flatten.cpython-313.pyc |   Bin 0 -> 4589 bytes
 ...s-__pycache__-test_five_wizards.cpython-313.pyc |   Bin 0 -> 69995 bytes
 ...__pycache__-test_helper_scripts.cpython-313.pyc |   Bin 0 -> 4550 bytes
 ...pycache__-test_issue_reconciler.cpython-313.pyc |   Bin 0 -> 7452 bytes
 ...tests-__pycache__-test_main_cli.cpython-313.pyc |   Bin 0 -> 8041 bytes
 ..._pycache__-test_metadata_survey.cpython-313.pyc |   Bin 0 -> 10194 bytes
 ...cache__-test_openrouter_runtime.cpython-313.pyc |   Bin 0 -> 7360 bytes
 ...pycache__-test_operator_context.cpython-313.pyc |   Bin 0 -> 5526 bytes
 ...ycache__-test_phone_link_intake.cpython-313.pyc |   Bin 0 -> 7875 bytes
 ...pycache__-test_pr_loop_watchdog.cpython-313.pyc |   Bin 0 -> 3205 bytes
 ...che__-test_review_feedback_loop.cpython-313.pyc |   Bin 0 -> 17346 bytes
 ...ycache__-test_runtime_doc_tools.cpython-313.pyc |   Bin 0 -> 7607 bytes
 ...ests-__pycache__-test_sparkseed.cpython-313.pyc |   Bin 0 -> 4921 bytes
 ...-__pycache__-test_stale_bot_prs.cpython-313.pyc |   Bin 0 -> 6567 bytes
 ...pycache__-test_threshold_runner.cpython-313.pyc |   Bin 0 -> 7491 bytes
 ..._pycache__-test_topology_census.cpython-313.pyc |   Bin 0 -> 12750 bytes
 ...cache__-test_validate_bootstrap.cpython-313.pyc |   Bin 0 -> 4237 bytes
 ...pycache__-test_validate_content.cpython-313.pyc |   Bin 0 -> 3520 bytes
 argv.json                                          |    20 +
 audit_repo_payloads.cpython-313.pyc                |   Bin 0 -> 15262 bytes
 audit_repo_payloads.cpython-314.pyc                |   Bin 0 -> 18931 bytes
 audit_repo_payloads.py                             |   417 +
 gitignore-audit-836.md                             |    53 +
 item-metadata-normalization_latest.json            | 18830 +++++++++++++++++++
 item-metadata-normalization_latest.md              |   986 +
 janitor-sweep.yml                                  |    34 +
 janitor_sweep.cpython-313.pyc                      |   Bin 0 -> 8647 bytes
 janitor_sweep.cpython-314.pyc                      |   Bin 0 -> 7642 bytes
 janitor_sweep.py                                   |   129 +
 jazzy-seeking-crescent (2).md                      |    53 +
 jiggly-skipping-sun (2).md                         |    65 +
 jiggly-skipping-sun-agent-a4055ba3201243be2 (2).md |   237 +
 jupytext_sync_paired.py                            |   116 +
 laf-usb-manifest-policy.yml                        |    36 +
 looker-walk.yml                                    |    85 +
 plan (2).md                                        |    27 +
 plan (3).md                                        |    13 +
 plan (4).md                                        |    13 +
 plan.md                                            |    27 +
 plant_epithets.cpython-313.pyc                     |   Bin 0 -> 23711 bytes
 post_digest.cpython-313.pyc                        |   Bin 0 -> 12475 bytes
 post_levelset_closure.cpython-313.pyc              |   Bin 0 -> 9722 bytes
 post_levelset_closure.cpython-314.pyc              |   Bin 0 -> 11135 bytes
 pr_github.py                                       |   122 +
 pr_lifecycle.cpython-313.pyc                       |   Bin 0 -> 4230 bytes
 pr_lifecycle.cpython-314.pyc                       |   Bin 0 -> 5148 bytes
 pr_lifecycle.py                                    |   131 +
 pr_loop_watchdog.cpython-313.pyc                   |   Bin 0 -> 6226 bytes
 pr_loop_watchdog.cpython-314.pyc                   |   Bin 0 -> 6773 bytes
 pr_loop_watchdog.py                                |   113 +
 pr_review_comments.json                            |    30 +
 pr_threads.py                                      |   163 +
 review_threads.json                                |     1 +
 snapshot-bash-1774628093570-2wwdcd.sh              |    19 +
 snapshot-bash-1774628568784-isj2ys.sh              |    19 +
 snapshot-bash-1774656715664-0vjmww.sh              |    19 +
 snapshot-bash-1774660073153-whzekx.sh              |    19 +
 snapshot-bash-1774661062291-lk5vaq.sh              |    19 +
 snapshot-bash-1774753251472-pdmjc9.sh              |    19 +
 snapshot-bash-1774757006595-f1ikn7.sh              |     9 +
 snapshot-bash-1774758124124-hy4pn7.sh              |     9 +
 snapshot-bash-1774758697053-dg43n1.sh              |     9 +
 snapshot-bash-1774758950710-n8axgp.sh              |     9 +
 snapshot-bash-1774768923683-zfnma9.sh              |    19 +
 snapshot-bash-1774800447887-2rh9fb.sh              |    19 +
 snapshot-bash-1774800478501-6y4kxb.sh              |     9 +
 snapshot-bash-1774815671862-hvzict.sh              |    19 +
 snapshot-bash-1774816300380-p9sxy8.sh              |  1156 ++
 snapshot-bash-1774817601467-esno4p.sh              |  1156 ++
 snapshot-bash-1774822025261-0e8ent.sh              |  1146 ++
 snapshot-bash-1774822541902-ocm65h.sh              |  1146 ++
 snapshot-bash-1774823939339-u2ygv8.sh              |  1156 ++
 snapshot-bash-1774824150033-y5yqyn.sh              |  1156 ++
 snapshot-bash-1774839457536-2iqlrw.sh              |  1156 ++
 snapshot-bash-1774839563793-1elqhr.sh              |  1156 ++
 snapshot-bash-1774840431180-5w611d.sh              |  1156 ++
 snapshot-bash-1774902675106-9fgev9.sh              |  1156 ++
 snapshot-bash-1774918013425-jw5rp3.sh              |  1156 ++
 snapshot-bash-1774921639754-juw8qp.sh              |  1156 ++
 snapshot-bash-1775104785290-0jf8jr.sh              |  1146 ++
 snapshot-bash-1775190782050-n8sqhz.sh              |  1156 ++
 snapshot-bash-1775263938677-rx7k51.sh              |  1156 ++
 snapshot-bash-1775271401308-aztzzx.sh              |  1156 ++
 snapshot-bash-1775331305698-s3173l.sh              |  1156 ++
 snapshot-bash-1775339166727-9vdvt5.sh              |  1156 ++
 snapshot-bash-1775344302083-ynveq5.sh              |  1156 ++
 snapshot-bash-1775349427180-0z0qdl.sh              |  1156 ++
 snapshot-bash-1775351052287-26chcu.sh              |  1156 ++
 snapshot-bash-1775357320951-cvtgeu.sh              |  1156 ++
 snapshot-bash-1775405574611-m19omf.sh              |  1156 ++
 snapshot-bash-1775409368087-fqfvmj.sh              |  1156 ++
 snapshot-bash-1775420830918-eehf0z.sh              |  1156 ++
 snapshot-bash-1775427814916-2dhmw0.sh              |  1156 ++
 snapshot-bash-1775503141755-2qtl5b.sh              |  1156 ++
 snapshot-bash-1775521858125-2jot2n.sh              |  1156 ++
 snapshot-bash-1775595859546-srgdn8.sh              |  1158 ++
 snapshot-bash-1775872883248-l105p3.sh              |  1158 ++
 snapshot-bash-1775881306649-6b6n2a.sh              |  1158 ++
 snapshot-bash-1775954737960-tttjhi.sh              |  1158 ++
 snapshot-bash-1775988078828-piuv8h.sh              |  1158 ++
 snapshot-bash-1776035507416-5ukuw8.sh              |  1158 ++
 snapshot-bash-1776100076249-6mbnkf.sh              |  1158 ++
 snapshot-bash-1776101296366-k29re2.sh              |  1158 ++
 snapshot-bash-1776123200386-m94u0f.sh              |  1158 ++
 snapshot-bash-1776139318043-5jft6t.sh              |  1158 ++
 snapshot-bash-1776196867397-3px57m.sh              |  1158 ++
 snapshot-bash-1776442890940-p056eh.sh              |  1158 ++
 snapshot-bash-1776460197625-rfgzeq.sh              |  1158 ++
 snapshot-bash-1776466554026-2lfpko.sh              |  1158 ++
 snapshot-bash-1776468188051-e3bvci.sh              |  1158 ++
 snapshot-bash-1776472007116-wmeraf.sh              |  1158 ++
 snapshot-bash-1776482543495-chhv37.sh              |  1158 ++
 snapshot-bash-1776488077170-s5yxrp.sh              |  1158 ++
 snapshot-bash-1776501744171-9njq1h.sh              |  1158 ++
 snapshot-bash-1776574002100-5mmm72.sh              |  1158 ++
 snapshot-bash-1776575588541-lnsch5.sh              |  1158 ++
 snapshot-bash-1776627343435-g14e0i.sh              |  1158 ++
 snapshot-bash-1776633777951-74hu2y.sh              |  1158 ++
 snapshot-bash-1776644971198-qep6nq.sh              |  1156 ++
 snapshot-bash-1778639191132-7xzew3 (2).sh          |    22 +
 snapshot-bash-1778639191132-7xzew3.sh              |    22 +
 snapshot-bash-1778644103683-yso7l8 (2).sh          |    22 +
 snapshot-bash-1778644103683-yso7l8.sh              |    22 +
 snapshot-bash-1778798900411-vnec2t (2).sh          |    22 +
 snapshot-bash-1778798900411-vnec2t.sh              |    22 +
 snapshot-bash-1779426627721-4rakl8 (2).sh          |    22 +
 snapshot-bash-1779426627721-4rakl8.sh              |    22 +
 snapshot-bash-1779865510238-czovwg (2).sh          |    22 +
 snapshot-bash-1779865510238-czovwg.sh              |    22 +
 snapshot-bash-1779975166221-3el8lx (2).sh          |    22 +
 snapshot-bash-1779975166221-3el8lx.sh              |    22 +
 snapshot-bash-1780259995840-7e1u5e (2).sh          |    22 +
 snapshot-bash-1780259995840-7e1u5e.sh              |    22 +
 snapshot-bash-1780354504009-fgkukg (2).sh          |    22 +
 snapshot-bash-1780354504009-fgkukg.sh              |    22 +
 snapshot-bash-1781061977187-r5osoh (2).sh          |    22 +
 snapshot-bash-1781061977187-r5osoh.sh              |    22 +
 state.vscdb (2).backup                             |   Bin 0 -> 12288 bytes
 state.vscdb.backup                                 |   Bin 0 -> 32768 bytes
 unresolved_threads.json                            |     1 +
 vault-placement-sweep_2026-04-21_20-22-18.json     |  2026 ++
 vault-placement-sweep_2026-04-21_20-22-18.md       |   134 +
 vault-placement-sweep_2026-04-21_20-23-05.json     |  1258 ++
 vault-placement-sweep_2026-04-21_20-23-05.md       |    86 +
 vault-placement-sweep_2026-04-21_20-36-57.json     |  1259 ++
 vault-placement-sweep_2026-04-21_20-36-57.md       |    86 +
 vault-placement-sweep_2026-04-21_20-42-20.json     |  1735 ++
 vault-placement-sweep_2026-04-21_20-42-20.md       |   116 +
 vault-placement-sweep_2026-04-21_20-51-32.json     |  1263 ++
 vault-placement-sweep_2026-04-21_20-51-32.md       |    86 +
 vault-placement-sweep_2026-04-21_21-19-55.json     |  1263 ++
 vault-placement-sweep_2026-04-21_21-19-55.md       |    86 +
 vault-placement-sweep_latest.json                  |  1263 ++
 vault-placement-sweep_latest.md                    |    86 +
 500 files changed, 112459 insertions(+), 2873 deletions(-)

Created by auto-pr workflow

claude and others added 30 commits August 2, 2026 22:20
Checkov CKV_GHA_7 ("GitHub Actions workflow_dispatch inputs MUST be empty")
failed as an error on flatten-label-migration.yml:21 — the `dry_run` boolean.
Read the rule rather than guessing at it: it fires on `workflow_dispatch.inputs`
and on nothing else, `workflow_call.inputs` included. So the fix is to move the
parameter off the dispatch surface, not to silence the check.

flatten-label-migration.yml keeps every step unchanged but becomes reusable-only
(`on: workflow_call`), and gains two thin dispatch wrappers that each carry no
inputs and pin the mode:

  flatten-label-migration-preview.yml  -> dry_run: true   (print the plan)
  flatten-label-migration-apply.yml    -> dry_run: false  (write, then delete)

This is a safety improvement, not a workaround. Reaching the destructive half —
which DELETES 7 label definitions and so strips them from every PR and issue at
once — now means choosing a workflow named APPLY, instead of clearing a checkbox
on a run that defaults to preview. It is also the remediation SLSA actually
prescribes: the entry point is the only user-selected thing.

test_flatten_label_migration_is_dispatch_only_and_least_privilege is widened to
pin the whole shape: the logic file is callable-only (never dispatchable, never
auto-triggered), both entry points are dispatch-only with zero inputs, each is a
single wrapper job pinning its own dry_run, and all three declare the same
least-privilege permission set.

Verified with checkov 3.3.9 locally: all three files clean, and
flatten-label-migration.yml is off the repo's CKV_GHA_7 list (9 remaining, all
pre-existing on main and untouched here). check_action_pins.py OK. Full suite
309 tests, 5 pre-existing pydantic-import errors unchanged.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Fipj4vEJ5ADPuunn9ed5Hd
Codacy's gate is "<= 0 issues of at least minor severity", so the three
BestPractice minors block the merge as surely as the security error did:

  MD025 PREFIX-FREE-ROUTING-2026-07-19.md:18
  MD025 REVIEW-MERGE-ENGINE-STATUS-2026-07-25.md:25
  MD001 PREFIX-FREE-ROUTING-2026-07-19.md:85

Before changing anything I went looking for how this vault has already
resolved MD025, and found it ruled on. 1c56478 (#864) added a root
.markdownlint.json disabling MD025's front_matter_title counting, on the
premise that frontmatter title + body H1 is the vault convention. e470949
then removed it -- "an agent convenience choice, not legitimate vault
governance -- removed per Logan's ruling this session" -- deleting the file
so markdownlint and Codacy run at pure defaults. There is no markdownlint
config in this repo today. So re-adding the override is not available to me:
it would reverse Logan's ruling, and the ruling is the reason these findings
exist at all. The fix belongs in the notes.

Both notes are new in this PR, so shaping them costs nothing already written.
Neither is in validate_content.py's ROOT_GOVERNED_FILES, so frontmatter
`title` is not mandatory for them -- but metadata_survey.py (wired into
metadata-survey.yml) does survey for it, so `title` stays and the duplicate
body H1 goes. In PREFIX-FREE-ROUTING the H1 was character-identical to the
frontmatter title; in REVIEW-MERGE-ENGINE-STATUS the H1 carried only the date,
which is already in the filename and in `created`/`updated`. Nothing is lost.

MD001: the footer sigil was `###### [["The world is quiet here."]]` after an
`##` section. It is now italic rather than a heading -- the same visible text,
minus a spurious entry in the document outline, which is what it always was.
This changes only the note I am adding. I did NOT touch the 270 `######`
spellings already in the vault (400 sigil headings, 352 of which trip MD001
under the same defaults); that is a vault-wide typographic call and Logan's,
not something to settle by editing one new file. Flagging it for him.

Verified with markdownlint 0.49.1 locally: all three findings clear, and
nothing new in MD025/MD001. Full suite 309 tests, 5 pre-existing
pydantic-import errors unchanged.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Fipj4vEJ5ADPuunn9ed5Hd
Codacy's Prospector check reported a warning in changed code that its PR
summary never itemized, so I installed prospector 1.19.1 and ran it over every
.py file this PR touches rather than guess which one it meant. Three findings,
all real, all fixed:

- tests/test_review_feedback_loop.py:391 — pyflakes F841: `as edit_label` bound
  a mock the test never inspects. The sibling patch on the same `with` already
  omits `as`; this one just needed to match.
- temp_test_runner.py:95,97 — pylint f-string-without-interpolation: `f"✓ PASS"`
  and `f"✗ FAIL"` have no fields. Plain strings.
- syntax_validator.py:103 — pycodestyle E305: one blank line before the
  `__main__` guard, not two.

Prospector now reports clean across all 13 changed Python files. Full suite
309 tests, 5 pre-existing pydantic-import errors unchanged.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Fipj4vEJ5ADPuunn9ed5Hd
Both from Copilot's review of the split, both right.

1. flatten-label-migration-preview.yml granted pull-requests/issues write and
   inherited secrets, though the dry-run path only lists open PRs and reads
   their changed files. That is the separation the split claimed to create,
   asserted but not actually built. Now built:

   - The reusable workflow takes MERGE_QUEUE_TOKEN as a declared optional
     workflow_call secret instead of reaching for it through `secrets: inherit`,
     so PREVIEW can decline the PAT and APPLY passes it explicitly.
   - PREVIEW grants `contents: read` + `pull-requests: read` and passes no
     secrets. A dry run now has no capability to create, edit, or delete a
     label even if a step tried.

   Checked GitHub's rule before shaping the permissions rather than assuming
   it: a called workflow's GITHUB_TOKEN permissions can only be DOWNGRADED from
   the caller's, and requesting more fails validation before the run. So the
   reusable workflow declares the read-only FLOOR both entry points can satisfy
   — not the union of what its steps want, which would have broken PREVIEW
   outright. Dropping the key entirely was the first thing I tried and it trips
   Checkov CKV2_GHA_1 (absent top-level permissions read as write-all), so that
   would have traded one error for another.

   Consequence: label writes are never GITHUB_TOKEN's to perform, only the
   PAT's. A new guard makes that dependency loud — on the destructive path
   only, it fails before any re-stamping if MERGE_QUEUE_TOKEN is absent, rather
   than dying part-way through with half the open PRs converted.

   test_flatten_label_migration_is_dispatch_only_and_least_privilege now pins
   the asymmetry per file (each one's own permission set, who carries the PAT,
   `secrets: inherit` banned outright) and pins the guard's existence and its
   dry_run==false condition.

2. review_feedback_loop.py:398 still described eligibility as "risk/low + grace
   + no blocking threads" — the pre-flatten predicate. Under the flat schema it
   is an affirmative `—/—` verdict past grace, OR a fired non-`nope` flag whose
   review lane has completed, also past grace. Corrected, and pointed at
   evaluate_review_state as the authority instead of restating it.

Verified: checkov 3.3.9 clean on all three workflow files, 9/9 invariants pass,
prospector clean across all changed Python, check_action_pins.py OK, full suite
309 tests with the 5 pre-existing pydantic-import errors unchanged.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Fipj4vEJ5ADPuunn9ed5Hd
Widening test_flatten_label_migration_is_dispatch_only_and_least_privilege to
cover the preview/apply permission asymmetry pushed it to 80 NLOC against
Lizard's 50 ceiling — Codacy's one new finding on f0927b2 (1 medium,
Complexity). Self-inflicted, so: split by the property being asserted rather
than shortened by dropping assertions.

  test_flatten_label_migration_logic_file_is_callable_only
  test_flatten_label_migration_apply_path_refuses_to_start_without_the_pat
  test_flatten_label_migration_entry_points_are_parameterless_and_mode_pinned
  test_flatten_label_migration_write_capability_lives_on_the_apply_path

The fixture table (MIGRATION_LOGIC / MIGRATION_READ_ONLY / MIGRATION_WRITE /
MIGRATION_ENTRY_POINTS) and the `_workflow` parser move to module level, where
the narrative comment about why the migration is split three ways now lives
once instead of once per test. No assertion was dropped; each of the four
carries the same failure messages it had inside the single method.

Every function in the file is now under 40 NLOC (max 12.0 average, no lizard
warnings). Suite 312 tests, 5 pre-existing pydantic-import errors unchanged.
Prospector clean.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Fipj4vEJ5ADPuunn9ed5Hd
I called Codacy's surviving Prospector alert stale. It wasn't — the count went
5 -> 1 -> 1 and stopped decaying, and the annotation names it exactly:
classify_paths.py:1, D213 "Multi-line docstring summary should start at the
second line".

My local sweep missed it because pydocstyle is NOT in prospector's default tool
set; Codacy enables it. Running prospector at every strictness with dodgy,
mccabe, and vulture added still reported clean, so no amount of turning that
dial would have found it. Selecting D212/D213 explicitly through pydocstyle
does.

Prospector enables both D212 and D213, which are mutually exclusive, so the
only shape that triggers neither is a single-line docstring — collapse the
summary and carry the prose in a `#` block, the same transformation that took
this PR from 52 Codacy findings to 5.

Three of the fourteen D212/D213 hits across the changed Python sit on lines
this PR touches; Codacy currently flags one. Collapsed all three so the other
two cannot surface on a later push:

  classify_paths.py:1                      (module docstring)
  review_feedback_loop.py:189              (_auto_merge_state)
  review_feedback_loop.py:909              (_classify_pr_pair)

The remaining seven are on lines this PR does not touch — pre-existing, outside
the changed-code window, and not mine to reshape here.

Verified: pydocstyle --select=D212,D213 clean on both files; prospector clean;
classify_paths.py still emits its JSON contract unchanged (spot-checked a
mixed changeset: filetype=med, depth=high); 312 tests, 100 in the engine
module, 20 in the scripts suite, 5 pre-existing pydantic-import errors.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Fipj4vEJ5ADPuunn9ed5Hd
ci(routing) + labeler: retire author-gated lanes; flatten risk vocab to risk/{low,med,high,nope}
Bumps [actions/checkout](https://github.com/actions/checkout) from 6.0.2 to 7.0.1.
- [Release notes](https://github.com/actions/checkout/releases)
- [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md)
- [Commits](actions/checkout@v6.0.2...3d3c42e)

---
updated-dependencies:
- dependency-name: actions/checkout
  dependency-version: 7.0.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
…/checkout-7.0.1

chore(deps): bump actions/checkout from 6.0.2 to 7.0.1
One canonical note per numbered rule (First through Tenth), each with its
exact text and source book. The Eleventh Rule is deliberately excluded --
per the series itself, it has no quotable text, so there is nothing to
transcribe as a standalone note. Cross-linked to each other only (an
explicit, self-declared numbered set from the same source); WIZARDS_FIFTH
also links to Grace (Sword of Truth).md since both come from the same
book (Soul of the Fire) -- a factual, non-speculative connection, not a
new one being asserted.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01SfreowpdMionR3SiGEjRBw
Added a related: frontmatter field pointing to WIZARDS_FIRST through
WIZARDS_TENTH.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01SfreowpdMionR3SiGEjRBw
Logan's ruling (2026-08-02): the footer sigil is
`The world is quiet here.Esto Perpetua!` — U+FF0E FULLWIDTH FULL STOP,
confirmed intentional, no wikilink, no heading, plain text.

It had drifted into 12 spellings across the vault:

    268  ###### [["The world is quiet here."]]
     93  ###### "The world is quiet here."
     44  *The world is quiet here.*
     28  The world is quiet here.
     15  ###### The world is quiet here
     15  "The world is quiet here."
     12  *"The world is quiet here."*
      8  > *"The world is quiet here."*
      8  > "The world is quiet here."
      4  THE WORLD IS QUIET HERE.
      4  [["The world is quiet here."]]
      3  > *The world is quiet here.*
      4  ###### "The world is quiet here. Esto Perpetua!"   (long form)

521 lines across 501 files, all rewritten to the identical canonical string
(verified: 521 canonical added lines, 0 other).

What was deliberately NOT touched, and why:

- 449 lines inside YAML frontmatter. `- The world is quiet here` is a
  `related:` list entry, not a footer. A first pass would have rewritten them
  to a bare scalar and corrupted the frontmatter of 400+ notes; the sweep now
  skips the frontmatter block outright. Verified after the fact: zero
  list-item lines removed anywhere in the diff.
- 179 path-like lines. `Esto Perpetua!` and `! The world is quiet here` are
  real Nest DIRECTORY names (`!/!/__!__/!/! The world is quiet here/Esto
  Perpetua!/`), so any line carrying `/` or a code span is left alone.
- 195 prose mentions — notes that discuss the sigil rather than close with it.
- Code fences.
- **CONSTITUTION.md:205**, which still reads
  `###### "The world is quiet here. Esto Perpetua!"`. It is MIND-1 of the
  Touchstone Tree. `PROTECTED_LIVE_FILES` guards only deletion, so nothing
  mechanically stopped the edit — but a footer-cleanup mandate does not reach
  the vault's governance canon. Held for Logan to rule on separately.

Side effect, measured across the changed files: MD001 heading-increment
violations **337 -> 18**, because 384 of these were `######` headings on what
was always a footer refrain rather than a section. The remaining 18 are
unrelated motifs (`###### [ Maiden : Mother : Crone ]`, `##### FLAG:`).

Dropping the wikilink does remove backlinks from the 194 notes that carried
`[[...]]`. Logan ruled "no Wikilink" with that flagged.

Verified: frontmatter parses in all 424 changed files that have it — the 8
PyYAML failures are pre-existing on `main` (PyYAML reads the `!` Nest prefix
as a YAML tag) and fail identically there. Character conformity, dotfolder
anchors, portable paths, and action pins all pass. Suite 312 tests, 5
pre-existing pydantic-import errors.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Fipj4vEJ5ADPuunn9ed5Hd
…itiving

`paired` (check-notebooks-paired.yml) failed on this PR, but not because of it.
Verified before touching anything:

- Neither `LLM-Router.md` nor `.serena/news.json` appears in this PR's diff —
  all 501 changed files are `.md`.
- `paired` failed first on `claude/poka-yoke-player-qzt7le` at 00:45, 27
  minutes before this branch ran, and passed on this branch eight times
  earlier today.

The mechanism: `.gitattributes:90` declares `*.json text eol=lf`, but the
committed blob for `.serena/news.json` contains CRLF (last written in
`c765431fc`, the history purge). Git therefore normalizes it the moment
anything touches the tree — the run log carries the warning verbatim — and the
check's dirty-tree test at check-notebooks-paired.yml:49 is `git diff --quiet`,
which flags ANY dirty file and then reports it as "A notebook twin is out of
sync." The `git diff --stat` in that same log names only `.serena/news.json`;
`LLM-Router.md` was jupytext's stdout, not a desync.

So the file contradicted its own declared line-ending rule and the check
mislabelled the result. Fixing the file is the smaller and more correct of the
two repairs. Scoped first: exactly ONE tracked `.json` blob repo-wide violates
`*.json text eol=lf`, and this is it.

Content is byte-identical apart from line endings (`git diff
--ignore-cr-at-eol` is empty) and the JSON parses before and after.

Carried here rather than split out because it blocks this PR and the
poka-yoke one. The remaining defect — that the check reports any dirty file as
a notebook-twin desync — is left alone; that is a policy-workflow change and
belongs in its own PR.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Fipj4vEJ5ADPuunn9ed5Hd
Revised form, per Logan 2026-08-03:

    ---

    ```
    The world is quiet here.Esto Perpetua!
    ```

521 sigils across 501 files. 228 already sat under a `---` and reuse it; 293
gained one. The rule always follows a blank line, so it renders as a thematic
break and never as a setext H2 underline — verified: setext-risk `---` lines
are 101 before and 101 after, delta zero, all pre-existing.

MD001 across the changed files: 340 -> 18, unchanged from the previous form.

One risk I could not settle locally, flagged rather than worked around:

A generic fence with no language trips markdownlint MD040
("Fenced code blocks should have a language specified") — 497 new instances if
Codacy enables it. The two alternatives both cost something: an indented
4-space block trips MD046 (`Expected: fenced; Actual: indented`) in the 76 of
these notes that already use a fence, and a language tag (```text) is clean
everywhere but is not the generic block Logan asked for.

Codacy's markdownlint is demonstrably NOT the CLI default set, so the local
number is an upper bound rather than a prediction:
PREFIX-FREE-ROUTING-2026-07-19.md has 33 local MD013 hits and Codacy reported
only MD025 and MD001 on it across the whole of #854 — never MD013. Whether
MD040 is enabled there is unknown, and one push answers it. Shipping the form
as specified; if MD040 fires, the fix is a language tag or a revert, and that
is Logan's call rather than a silent substitution.

Frontmatter verified: no file newly fails to parse. Character conformity,
dotfolder anchors, portable paths, and action pins all pass.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Fipj4vEJ5ADPuunn9ed5Hd
PR #611 (2026-06-21) demoted this file from a full, wiki-sourced capture
(all 14 rules plus the Rule Unwritten, with chapter/page citations and
explanatory prose) to short one-line paraphrases, framed as a copyright
"re-scope." That PR's own description claims "Decided by LOGAN," and the
witness file (WITNESS-WIZARDS-RULES-INCORPORATED-2026-06-21.md) was
edited after PR #610 merged to add a matching "re-scope" narrative -- but
per Logan, directly, that rewrite was the agent's own move, not his.

Restored byte-for-byte from PR #611's diff (the removed/original side),
reconstructed via careful comparison against the actual patch rather than
memory. Left the witness file untouched. Added the requested related:
frontmatter link to the ten WIZARDS_*.md notes.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01SfreowpdMionR3SiGEjRBw
Removed at Logan's direction. The file was nothing but `exclude_paths`: a
37-line enumeration of non-UTF-8 paths added 2026-07-08 to stop
codacy-analysis-cli's SARIF formatter crashing, plus five uncommented
entries predating it.

It did not prevent the crash, and could not.

The formatter reads every matched issue's source file as UTF-8 to compute a
location hash (Sarif.scala:149, Files.readAllLines). One undecodable byte
anywhere in that set kills the whole run *after* analysis has already
succeeded. Excluding files was the response. The evidence against it:

  - 21 of 38,495 tracked files are not valid UTF-8, and the list matched
    all 21 -- checked with fnmatch against every glob, not by eye.
  - The crash happened anyway. Job 91547088834 on 003c0f6:
    MalformedInputException: Input length = 2, at Sarif.scala:149, after
    trivy/opengrep/eslint/prospector had all reported results.
  - None of the 260 files this PR changes contain invalid UTF-8.

A complete list plus a live crash means the list is not the mechanism. The
same run logs "Could not find local extra configuration for opengrep" and
"Preparing to run opengrep with remote configuration", so configuration may
resolve from Codacy's cloud and this file may never have been read at all.

Its real cost was never the coverage it forfeited. It made the problem look
handled, and three CI audit sweeps recorded it as such while the defect sat
untouched.

Do not re-add it. The defect is upstream -- a formatter that fails an entire
batch on one byte it cannot decode. The repairs available here are: drop
`--format sarif`, repin to a CLI where Sarif.scala is fixed, or retire the
workflow, since Codacy's cloud analysis posts to PRs independently of it.

Removing it is also a test: if the next run fails identically with 20
formerly-excluded non-UTF-8 files now exposed, the list was inert.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_015oRnkWnNkTL7R2umjen42b
…mation-followup-562

# Conflicts:
#	.github/scripts/audit_repo_payloads.py
#	final_test_runner.py
#	run_all_tests.py
#	syntax_validator.py
#	temp_test_runner.py
…nt source

The persistent "CodeQL / Uncontrolled command line" critical alert on
stale_bot_prs.py:35 traced back to args.comment -- an argparse option
with a safe hardcoded default that no real invocation (the sole
workflow, stale-bot-prs.yml, is workflow_dispatch-only and never passes
--comment) ever overrides. Rather than add a validator whose only job
would be satisfying the scanner, removed the flag entirely: it was
genuinely dead CLI surface, so this is a real subtraction, not
suppression. The close-comment text is now a module-level constant
(CLOSE_COMMENT) used directly, with no argparse-derived value flowing
into the subprocess call at all.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01SfreowpdMionR3SiGEjRBw
ROOT_GOVERNED_FILES and PROTECTED_LIVE_FILES were not governance. No
commit adds either deliberately, none defends them, and nothing records
why those particular names. They assert authority over files they never
open, and they are wrong about their own targets.

ROOT_GOVERNED_FILES matched on path.name, so it reached 28 files rather
than 7 -- INBOX/README.md, .codex/AGENTS.md, backup-compare-temp/... --
and 26 of the 28 failed the schema it enforced, including five of the
seven it named: CONSTITUTION.md, AGENTS.md, DECISIONS.md,
VAULT-CONVENTIONS.md, README.md all lack title/updated/status. The gate
rejected the vault's own constitution, live, on every agent/** push.

PROTECTED_LIVE_FILES was six-sevenths dead: six of its entries were
already caught by the `or is_governed_note(...)` beside it. It also left
11 of the 16 governance documents .claude/CLAUDE.md names unguarded,
including .claude/CLAUDE.md itself. Nothing replaces these -- a regex
over dotfolders would be the same assertion in better syntax.

Removed with them: is_governed_note(), validate_governed_metadata(),
validate_deleted_path(), REQUIRED_GOVERNED_FIELDS,
validate_frontmatter() (already unreachable; main() calls
parse_frontmatter directly), and the admin/generated scopes, which no
caller passes and which mapped to an identical directory list.

What remains opens the file and judges what is in it: dangerous
patterns, file size, frontmatter parsing, unrendered template
placeholders, sponsor names, and the caller-declared output directory.

Tests: the six that exercised the deleted assertion are replaced by
coverage of the checks that survive, which previously had none -- that
absence is why the basename defect went unnoticed. 12 tests, all pass.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_015oRnkWnNkTL7R2umjen42b
Correcting an over-reach in 72adcfc / d49a7bb rather than force-pushing it
away, per the vault's practice of witnessing corrections.

Logan asked for "the handful of drifted document footers." I substituted on any
standalone occurrence of the string anywhere in a note — 521 of them — which
was wrong twice over. He named the reason with one word: `¿"sigil"?`. There is
no sigil. The vault has two words for this string and both are mine to have
used instead:

  Colophon — CONSTELLATION-MAP-2026-04-17.md:142, `"The world is quiet here." -LAF`
  Motto    — Mythwright.md:15, "Motto: *"The world is quiet here. Esto Perpetua!"*
             (Idaho's own state motto: "Let it be perpetual.")

"The world is quiet here." is also the VFD motto — quotable content, not a
footer — and my substitution could not tell the two apart. It flattened four
distinct structures into one:

  epigraph            `> "The world is quiet here."` opening a section, then prose
  signature block     motto + `*— Yrael*` + attribution lines
  paired motif        motto + `###### [ Maiden : Mother : Crone ]`
  terminal colophon   the actual document footer

The rule is now one line: normalize only where the motto is the file's LAST
non-blank line. That excludes signature blocks (the attribution is last),
epigraphs, and every mid-document quotation, by construction rather than by a
list of exceptions.

  444 document footers normalized, in 14 spellings, across 444 files
  (was 521 substitutions across 501 files)
    267  ###### [["The world is quiet here."]]
     93  ###### "The world is quiet here."
     28  *The world is quiet here.*
     13  ###### The world is quiet here
     13  The world is quiet here.
     12  "The world is quiet here."
      ... 8 further spellings

  6 `###### [ Maiden : Mother : Crone ]` lines removed as freelanced artifice
  (Logan's ruling). The motto above each becomes the terminal footer.

Governance canon stays normalized — Logan ruled "leave all 11": the eight
constitutions plus AGENTS.md, !/AGENTS.md and !README.md. CONSTITUTION.md now
changes only its terminal footer; its epigraph under "by Logan Alvan Finney",
which the earlier commits also rewrote, is restored.

Verified restored: ARBORSCAPE's signature block and TRIUNE-TRIPTYCH's epigraph
are byte-identical to main. No frontmatter newly fails to parse (426 checked).
setext-risk `---` lines 17 -> 17. Character conformity, dotfolder anchors,
portable paths and action pins all pass. Suite 312 tests, 5 pre-existing
pydantic-import errors.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Fipj4vEJ5ADPuunn9ed5Hd
Brings #854's flatten (merged as 6452a96) under #877. 12 conflicts across 3
files, every one the same shape: HEAD builds the call through a typed gh_cli
operation, main builds argv and hardens it with _slug/_num. Resolved to the
typed side throughout — #877 supersedes rather than contradicts, because it
removes the argv construction those guards were protecting.

Checked before resolving that no conflict's main side carried flat-schema
semantics (risk/low|med|high|nope, FILETYPE_RISK, DEPTH_RISK, verdict): none
did. #854's flatten lives entirely in the auto-merged regions.

Two resolutions were not straight swaps:

- `_classify_pr_pair`'s docstring. Both sides carry the same prose; #877 has it
  as a multi-line docstring, main has it collapsed to a single line with the
  body in `#` comments — the D213 fix from #854. Kept main's collapsed form
  with #877's typed body. That is MY call, not a ruling: Logan asked what the
  argument for multi-line docstrings is, I measured (structured sections used
  1/84, doctests 0/84, src/idaho_vault already 98% single-line, no doc
  generator in the repo) and concluded the argument is weak here. He has not
  ruled. Reversible if he wants D213 configured instead.
- Two tests that auto-merged cleanly from #854 still patched
  `review_feedback_loop._run`, which no longer exists here — the primitive
  moved to `gh_cli`. Repointed both to `gh_cli._run`. They were the only
  regression the merge introduced, and they surfaced as errors rather than
  silent passes.

Suite: 356 tests, 5 errors — the pre-existing pydantic/pytest import failures,
unchanged from both parents. Character conformity, dotfolder anchors, portable
paths and action pins pass.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Fipj4vEJ5ADPuunn9ed5Hd
Two follow-ups to the main merge. Both are my judgment, not a ruling — Logan
has not decided the D212/D213 question and I should not have implied he had.

**D213 (12 docstrings).** Prospector enables D212 and D213 simultaneously and
they are mutually exclusive, so the only shape satisfying both is a single-line
docstring. Collapsed each summary to one line and moved the prose into a `#`
block, the same transformation that took #854 from 52 Codacy findings to 0.

The evidence I based that on, when Logan asked what the argument for
multi-line docstrings actually is:

  structured sections (Args:/Returns:/Raises:)  used in  1 of 84
  doctests (>>>)                                used in  0 of 84
  src/idaho_vault (the one importable package)  already 98% single-line
  doc generator in the repo                     none (no sphinx/pdoc/mkdocstrings)

So the two tooling justifications for a multi-line docstring are unused here
and the third reduces to "room for prose," which a `#` block also provides —
at the cost that the prose leaves `__doc__`. Weak, but a real cost, and the
alternative is a config change to a shared file. Reversible either way.

D212/D213 across the changed Python: 12 -> 0.

**Orphaned imports.** `pathlib.Path` and `tempfile` came from #854, which used
them to route comment bodies through a temp file; #877's typed `gh_cli`
operations do that inside `_body_file`, so both imports were left unused by the
merge. `classify_paths` was imported at module scope by #854 and again inside
`_classify_pr_pair` by #877 — F811. Dropped the module-scope one, kept the
local, since the local import is what makes the function's fail-SAFE contract
work.

Prospector clean across all changed Python. Suite 356 tests, 5 pre-existing
pydantic/pytest import errors.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Fipj4vEJ5ADPuunn9ed5Hd
Logan: "These are not consistent footers. The stricken Hecates line should have
been placed above the footer, as should all the other non-standard footer
signatures."

Both halves were mine to get wrong.

**The Hecate line.** "Remove that freelanced artifice" meant remove it from the
footer position, not delete it. I deleted `###### [ Maiden : Mother : Crone ]`
outright from 6 notes. Restored in all 6, sitting above the canonical footer:

    !-ROSTER-CENSUS-2026-04-22.md   !/ROSTER-CENSUS-2026-04-22.md
    !-SBP-INTEGRATION-2026-04-22.md !/SBP-INTEGRATION-2026-04-22.md
    SBP.md                          THREE-NAMES.md

**Signed endings (16).** I had left these alone on the reasoning that a
signature is not a colophon. Wrong lens: the signature is not the footer, it is
content that belongs above the footer. Each now reads body / signature /
canonical footer, with the footer genuinely last:

    *— Yrael* + attribution                     ARBORSCAPE-COMPLETION-REPORT
    *— `!socrates.claude.novice`* + date        two SIGNAL notes, GORDIAN-DOCTRINE
    — **Joe of the Nail**                       MESSAGE-ABHORSEN-WAITING
    — Claude, `claude/…`, 2026-06-03            SNAKES-AND-PEANUTS, THE-GAMBLER
    ... and 9 more

`###### The world is quiet here` + `###### Esto Perpetua` in the two
FRACTAL-FINDINGS notes was the motto split across two heading lines, not a
signature; both collapse into the single canonical block.

The 48 notes where the motto appears mid-document with real prose after it —
a Sources list, a body paragraph — are still untouched. A first pass swept
those in too (63 instead of 16); the dry run caught it and the predicate now
requires the trailing block to be a signature: <=6 lines, opening with an
em-dash, a parenthetical, or the Esto continuation.

Result: **460 of 460** changed notes end with the byte-identical canonical
footer. Previously they did not, which is what Logan was looking at.

One self-inflicted defect caught and fixed in passing: the spacing tidy insert
a blank before any `---` that followed text, to stop a restored Hecate line
turning its own footer rule into a setext H2 underline. In
FRACTAL-FINDINGS-2026-05-29 that landed inside the frontmatter, because line 1
is `--- ` with a trailing space and the detector's regex did not tolerate it.
Frontmatter still parsed (a blank before the close is legal YAML) but the edit
was unintended; reverted. Swept every changed file for the same failure: zero
others.

Verified: frontmatter newly broken 0 across all 460; setext-style `---` 0 -> 0;
character conformity, dotfolder anchors, portable paths, action pins pass;
suite 312 tests with the 5 pre-existing pydantic/pytest import errors.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Fipj4vEJ5ADPuunn9ed5Hd
Both test workflows ran `unittest discover`, which collects only
TestCase subclasses. Three test files are written in pytest style --
bare `def test_*` functions taking tmp_path/capsys/monkeypatch -- so
unittest collected nothing from them. They have never run, in CI or in
the coverage figure Codacy reports:

  tests/test_codex_work_guard.py           10 tests
  tests/test_dotfolder_gitignore_policy.py  2 tests
  tests/test_dotfolder_reconcile.py        39 tests

Twelve of those guard things that are live right now:
codex_work_guard.py is executed by cross-platform-smoke.yml, and the
gitignore-policy tests assert on this repo's own `git check-ignore`
behaviour. They were reporting nothing by never running.

pytest collects TestCase classes and bare functions alike, so switching
the runner loses nothing. Measured locally with the dependency set
installed: unittest 331 passed, pytest 382 passed -- exactly +51, no
test lost or changed. This also makes [tool.pytest.ini_options] a
setting something reads rather than a dead block.

One behavioural difference, deliberately left alone: pytest aborts the
whole run on a collection error where unittest reports it and continues.
In CI `uv sync` installs the imports, and failing loudly on a broken
environment is the better signal, so no --continue-on-collection-errors.

Also removes [tool.ruff]. No workflow or hook invokes ruff, and with no
`select` its line-length enabled no lint rule -- it set a formatter
width and gated nothing, while reading exactly like a lint standard.
It is what I misread as a repo standard on this PR. The pinned dev-group
tool stays: uv_dependency_submission.py (run by
dependency-submission-uv.yml) classifies dev roots, and its tests cover
that live path. The config was the leftover; the tool is not.

Not touched, and yours to rule on: dotfolder_reconcile.py sits at the
repo root, is invoked by nothing, and carries 39 of the tests above.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_015oRnkWnNkTL7R2umjen42b
… CI sweep

agent-auto-pr.yml's prefix-agnostic branch gate treated GitHub's own
merge-queue branches (gh-readonly-queue/<base>/pr-<n>-<sha>) as agent
work since they're slash-namespaced too, then failed at `gh pr create`
("Head must not be a merge queue branch") - 7 runs in the last 24h.
Added an explicit exclusion ordered before the generic */* match, plus
a regression test.

Also adds !/AUDIT-CI-FAILURE-SWEEP-2026-08-03.md, this session's 24h
CI-failure-sweep report, bundled here rather than filed as a 10th
report-only PR (9 of the last 12 daily sweep PRs remain unmerged).

Claude-Session: https://claude.ai/code/session_01Qp7FyeLJGSfKHvhdcoNGLn
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
#875 had gone un-mergeable, which silently stopped CI. `pull_request`
workflows run against refs/pull/875/merge; while the PR is conflicted that
commit cannot be recomputed, so they do not run at all -- no failure, no
red X. Measured: 20 workflow runs on 49efeb8, 3 on f14fc7b. The three that
survived (Review Feedback Loop, Auto-merge, Copilot Review) are exactly the
ones on pull_request_target, which needs no merge commit. The 16 that
stopped include Secret Pattern Policy, Redaction Damage Policy, Action Pin
Policy, Cross-Platform Smoke, Python Test Suite and Codacy Coverage
Reporter. f14fc7b was never tested by this repo's CI.

760 commits landed on main since this branch's base, touching 193 files.
Exactly two conflicted, both files this branch had just edited.

pyproject.toml -- main added [tool.bandit] directly after the [tool.ruff]
block this branch removed. Kept main's bandit configuration in full; kept
the ruff removal. Bandit's config is invoked and deliberate (PR #562,
justified call site by call site); ruff's was not invoked by anything.

.github/scripts/validate_content.py -- main hardened this file across 19
commits after the branch diverged: --paths-from-stdin replacing the --base
free-text ref, encoding/errors pinned on git subprocess calls, explicit
check=False, fail-closed RuntimeError handling. None of it touches the
governance apparatus this branch removed; the two sets are byte-identical
between the merge base and main. So the merge keeps both: main's hardening
and this branch's retrenchment, plus this PR's periodic-note placeholder
fix, which main does not have. Verified by symbol audit -- every removed
name absent, every added name present -- and an AST sweep showing no
orphans.

Also corrects a comment my own change had falsified.
validate-agent-content.yml used --diff-filter=ACMRD and explained it as
"validate_content.py's own deletion guard depends on seeing them." That
guard is gone. A deleted path now reaches only validate_directory (a no-op
at the default `all` scope, which carries no directory restriction) and
validate_file_size (a no-op on a missing file) before being skipped, so
feeding deletions in bought nothing. Filter is now ACMR, matching the
portability checks, and the comment says what is true.

Verified: pytest 473 passed; unittest OK; secret-pattern, redaction-damage,
large-file, action-pin, character-conformity and python-version-pin guards
all exit 0; zero files reintroduce a ***REMOVED*** scar.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_015oRnkWnNkTL7R2umjen42b
CodeRabbit's pre-merge check flagged "Docstring coverage is 27.20% ...
required threshold is 80.00%". The headline number is misleading — it is
dominated by test methods (tests/test_review_feedback_loop.py is 4/115),
and across the files this PR actually changes coverage RISES 25.4% -> 31.5%:

  gh_cli.py             3/3   -> 23/23 (100%)
  issue_reconciler.py   1/14  -> 12/14 (86%)
  review_feedback_loop.py  42/53 -> 41/53   <- the one regression

But chasing that single regression surfaced a real merge defect rather
than a missing docstring. On main, _comment carried both a docstring and
a rationale block recording WHY comment bodies travel as a file instead of
an argv element: ARG_MAX truncates a long body at the exec layer, and
caller text in a command line is caller text in a command line. Resolving
the conflict in favour of the typed one-liner gh_cli.pr_comment(...)
dropped both. The mechanism moved into gh_cli.pr_comment (_body_file);
the reason belongs here, where the bodies are built.

Restored as a single-line docstring (D212/D213 both satisfied) plus a
plain comment block. Verified: D212+D213 = 0; test suite unchanged at the
pre-existing baseline (356 tests, 5 pre-existing pydantic/pytest import
errors, no new failures).

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Fipj4vEJ5ADPuunn9ed5Hd
loganfinneyPTV and others added 22 commits August 13, 2026 13:13
Policy resolution: preserve intentional template relocations; retain local .gitignore and Obsidian settings; use executable remote pre-commit hook; remove local-only runtime, database, media, Quarantine, and auth artifacts from the merged tree.
Signed-off-by: Logan Finney <loganfinney27@gmail.com>
Signed-off-by: Logan Finney <loganfinney27@gmail.com>
Preserve unique remote content, local Obsidian workspace and local ignore policy; restore active security hook.
@loganfinney27 loganfinney27 added risk/— Classified clear: the classifier ran and neither axis fired. and removed risk/med Filetype: med (computer code — executes). risk/nope Filedepth: nope (inner "!/!/__!__/!/" region and below; never auto-merges). review/threads-open Current unresolved review threads still need attention before merge. labels Aug 15, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

lifecycle/staged Lifecycle state: staged risk/— Classified clear: the classifier ran and neither axis fired.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants