The Whole-Tree Survey Example Now Shows Public Repos Only

Why Care?

The survey page shows what the dashboards look like on a real tree: ours. The first version was built from everything on one laptop, including client work that should never sit on a public page. Now the example only shows what anyone can already see on GitHub.

What's New?

• Public repos only: the whole-tree examples now cover 651 docs in 72 repos, all public on GitHub. Client folders and private repos are gone.

• Links that work: each doc in the examples links to its file on GitHub, instead of to a file on the laptop that built the page.

• New screenshots: the survey page and the 10-28 changelog entry show the new examples.

How it Works

The scanner already had a --public mode. It drops docs marked private, hides client and collaborator folders, and strips local paths. The examples just weren't built with it.

A new --github-public option goes one step further. It asks GitHub whether each repo is public, keeps only those, and links each doc to its file there.

python3 agent-skills/survey/scripts/scan.py . --scope tree --public --github-public

A client's private repo can sit anywhere in a tree, not only in a client folder, so checking GitHub is more reliable than checking folder names. It needs the gh command line tool, signed in.

Under the Hood

• More folder names hidden: client-stacks/ and clients/ now join client-sites/ and collaborations/ on the list of folders that never appear in a public survey or an OKF export. They hold client work even inside a public repo.

• Dashboards use the GitHub link: Board, Ledger and Map link to a doc's GitHub URL when the survey has one, and to the local file otherwise. Local use is unchanged.