docs(profile): weekly-demos visibility vs public clone instructions

[enricopiovesan]

Drift

profile/README.md org table currently says:

[weekly-demos](...) — Runnable weekly demos (private).

Standing intent (CEO): traverse-framework/weekly-demos is the shared public weekly demo monorepo, linked from the deny-demo blog, Announcement #1517, llms.txt, and /questions/how-do-i-run-the-agent-blocked-weekly-demo.html (which still documents git clone https://github.com/traverse-framework/weekly-demos.git).

Cold readers / agents following the site will hit a closed door if the repo is private; labeling it private on the org profile while the site teaches a public clone is an honesty bug either way.

Pick one

1. Make (or keep) the repo public and drop (private) from the org profile table — preferred if the standing weekly-demos rule still holds.
2. Keep it private and scrub public clone instructions from website Q&A / blog / llms.txt / Announcement — cite the blog write-up only, or publish a public mirror artifact.

Also grant the Cursor GitHub App access to weekly-demos if it should stay in the CEO publish loop (App currently cannot see the repo).

Not inventing

No change to Callweave / private proof apps. This is only the weekly-demos visibility vs public docs mismatch.

[enricopiovesan]

Cross-link: start-here blog + SEO pack is drafted but blocked on CloudAgent usage / Contents write — traverse-framework/website#123.

[enricopiovesan]

Afternoon recheck (2026-09-23 ~3:10 PM MT): Cursor GitHub App still cannot see traverse-framework/weekly-demos (scm_repo_not_accessible). Confirms the App-access half of this issue. Visibility vs public-clone docs decision still needs a human pick (prefer public + drop (private) from profile table if standing weekly-demos rule holds).