- Delete obsolete change proposals and bio content source
- Rewrite README.md with correct features, data sources, structure
- Update PROJECT_REFERENCE.md with accurate status and completed work
- Update CLAUDE.md references and sprint status
- Add docs/CONTRIBUTING.md developer guide with:
- How to add blog posts (frontmatter, markdown)
- How to add new pages (Dash routing)
- How to add dashboard tabs
- How to create figure factories
- Branch workflow and code standards
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Captured two lessons from Sprint 9:
1. Gitea Labels API requires org context - workaround for user repos
2. Always read CLAUDE.md before asking questions about sprint context
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
- Create docs/project-lessons-learned/ for local lesson storage
- Add INDEX.md with lesson template and index table
- Document Phase 4 dbt test syntax deprecation lesson
- Update CLAUDE.md with backup method when Wiki.js unavailable
This provides a fallback for capturing lessons learned while
Wiki.js integration is being configured.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
- Delete toronto_housing_dashboard_spec_v5.md (TRREB-based design)
- Delete wbs_sprint_plan_v4.md (outdated sprint plan)
These documents reference the deprecated TRREB-based approach.
New implementation will follow Change-Toronto-Analysis-Reviewed.md.
Closes#51
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
- Create comprehensive transition plan (Change-Toronto-Analysis-Reviewed.md)
covering cleanup, new data pipeline, dbt restructuring, and dashboard tabs
- Update CLAUDE.md to reflect current app structure (Sprint 8 pages)
- Add reference to new documentation in CLAUDE.md
- Update import examples from TRREB to neighbourhood-based
- Mark legacy docs as being replaced
- Add Jupyter notebook requirements (one per graph with data reference)
- Add CRITICAL rule: NEVER delete development branch
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
