PR #958 follow-ups: stale org-Projects-permission docs + missing default-owner regression test nf-9h0d ← Beads

Twinned from https://github.com/cfsh/ninefold/issues/959 by tools/beads/import_github.py's reconcile pass.

Suggestions from ninefold-reviewer's review of #958.

PR #958 flipped operationalize_design.py's DEFAULT_PROJECT_OWNER from jcantsp-bot to cfsh, now that #913's org-Projects-permission gap is resolved. Two residuals, both advisory (CONVERGED, not blocking):

1. Stale documentation elsewhere in tools/github_live/ still describes the permission gap as a live, current blocker — the exact fact #958 just falsified in operationalize_design.py's own comment, left unswept in the sibling package: - tools/github_live/gh.py:17-24 (module docstring, gap 1) — "Relevant because jcantsp-bot cannot create organization-owned Projects... every Project this package creates today is user-owned" - tools/github_live/tasks.py:95-96 (project_status docstring) — points at gh.py's docstring "for why every Project this package creates is user-owned today" - tools/github_live/tasks.py:146-149 (create_project docstring) — "jcantsp-bot can create Projects under its own account but not under the cfsh org... until that's resolved" - tools/github_live/README.md:32-36 — same claim, present tense

All four should move to past tense / note the 2026-08-14 resolution, consistent with the updated comment above DEFAULT_PROJECT_OWNER.

1. No test guards the changed default. design_docs/tools/tests/test_operationalize_design.py never calls apply()/main() without an explicit --owner, so nothing would catch a future accidental revert/typo of DEFAULT_PROJECT_OWNER. A one-line test asserting the constant's value, or a main() test that omits --owner and checks the resolved owner, would close the gap.

Default ships if unactioned — file for whoever next touches either area.