Problem
Until the repo is public, marked as a template, and discoverable via topics, it isn't a portfolio piece — it's a private folder.
Proposed solution
Flip repo visibility to public (gh repo edit --visibility public). Mark as template (gh repo edit --template). Apply branch-protection JSON via branch-protection.yml workflow_dispatch. Add topics: template, python, fastapi, react, vite, typescript, claude-code, llm-coding, harness, pre-commit, opentelemetry. Add screenshots/GIFs to README (green CI, hello page, Jaeger trace, just check run). Pin to the GitHub profile.
Acceptance criteria
Priority rationale
Medium: the work is done by ticket #27; this ticket just flips the switches that make it a portfolio piece.
Depends on
#27
Problem
Until the repo is public, marked as a template, and discoverable via topics, it isn't a portfolio piece — it's a private folder.
Proposed solution
Flip repo visibility to public (
gh repo edit --visibility public). Mark as template (gh repo edit --template). Apply branch-protection JSON viabranch-protection.ymlworkflow_dispatch. Add topics:template,python,fastapi,react,vite,typescript,claude-code,llm-coding,harness,pre-commit,opentelemetry. Add screenshots/GIFs to README (green CI, hello page, Jaeger trace,just checkrun). Pin to the GitHub profile.Acceptance criteria
mainanddevelop.Priority rationale
Medium: the work is done by ticket #27; this ticket just flips the switches that make it a portfolio piece.
Depends on
#27