fix: ensure demo recordings detect template changes + prepare 1.0.0 release

[t1mmen]

User description

Summary

• Fix demo recording bug where template changes weren't triggering rebuilds
• Add buildlog cleanup to record_demo.sh (root cause of the issue)
• Fix Claude Code integration copy commands in README.md
• Create major changeset for 1.0.0 release celebrating 365 days since first public release
• Re-record demo video showing v1.0.0 version numbers (validated frame-by-frame)

Changes

Bug Fix

• record_demo.sh now cleans up .srtd.buildlog.json and .srtd.buildlog.local.json before recording
• Without this cleanup, SRTD's hash-based change detection would miss template modifications from prior runs

README Fix

• Fixed Claude Code integration copy commands (added mkdir -p, corrected cp syntax)

1.0.0 Release Preparation

• Major changeset with comprehensive release notes covering December 2025 features:
  • Dropped React/Ink dependencies (zero version conflicts)
  • srtd doctor command for setup diagnostics
  • --json flag for all commands (CI/CD integration)
  • @depends-on template dependency ordering
  • Actionable Postgres error hints
  • Claude Code integration
  • Refreshed CLI UI
  • 528+ passing tests

Test plan

• Demo video re-recorded with v1.0.0 version numbers
• All 1206 frames validated (init, watch, build, apply, promote, doctor all show v1.0.0)
• Changeset correctly marked as major

🤖 Generated with Claude Code

---

PR Type

Bug fix, Enhancement

---

Description

• Fix demo recording to detect template changes via buildlog cleanup

• Correct Claude Code integration copy commands in README

• Prepare 1.0.0 major release with comprehensive feature summary

• Update documentation for skill activation scope

---

Diagram Walkthrough

flowchart LR
  A["Demo Recording Script"] -->|"Clean buildlog files"| B["Template Change Detection"]
  C["README Documentation"] -->|"Fix copy commands"| D["Claude Code Integration"]
  E["Changeset File"] -->|"Major version bump"| F["1.0.0 Release Notes"]
  D -->|"Update activation scope"| G["Enhanced Documentation"]

Loading

File Walkthrough

	Relevant files
Bug fix	record_demo.sh Add buildlog cleanup for template change detection              scripts/record_demo.sh Add cleanup of .srtd.buildlog.json and .srtd.buildlog.local.json files before demo recording Include critical comments explaining why buildlog cleanup is necessary for change detection Ensure fresh state to prevent SRTD from missing template modifications from previous runs +5/-0      README.md Fix Claude Code integration commands and documentation      README.md Add mkdir -p .claude/skills .claude/rules to create necessary directories Fix Claude Code rule copy command from cp -r to cp for single file Expand skill activation scope to include migrations-templates directories and .buildlog.json files Clarify documentation for Claude Code integration setup +3/-2
Documentation	one-point-oh.md Create 1.0.0 release changeset with feature summary            .changeset/one-point-oh.md Create major version changeset for 1.0.0 release Document architecture overhaul including dropped React/Ink dependencies List new commands and features (srtd doctor, --json flag, @depends-on comments, --bundle flag) Highlight developer experience improvements and stability enhancements Include 528+ passing tests and comprehensive release notes +45/-0

---

[changeset-bot]

🦋 Changeset detected

Latest commit: 9ec591a

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@t1mmen/srtd	Major

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[qodo-free-for-open-source-projects]

PR Compliance Guide 🔍

Below is a summary of compliance checks for this PR:

Security Compliance
🟢	No security concerns identified No security vulnerabilities detected by AI analysis. Human verification advised for critical code.
Ticket Compliance
⚪	🎫 No ticket provided Create ticket/issue
Codebase Duplication Compliance
⚪	Codebase context is not defined Follow the guide to enable codebase context checks.
Custom Compliance
🟢	Generic: Comprehensive Audit Trails Objective: To create a detailed and reliable record of critical system actions for security analysis and compliance. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Meaningful Naming and Self-Documenting Code Objective: Ensure all identifiers clearly express their purpose and intent, making code self-documenting Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Robust Error Handling and Edge Case Management Objective: Ensure comprehensive error handling that provides meaningful context and graceful degradation Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Error Handling Objective: To prevent the leakage of sensitive system information through error messages while providing sufficient detail for internal debugging. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Logging Practices Objective: To ensure logs are useful for debugging and auditing without exposing sensitive information like PII, PHI, or cardholder data. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Security-First Input Validation and Data Handling Objective: Ensure all data inputs are validated, sanitized, and handled securely to prevent vulnerabilities Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
Update

Compliance status legend

🟢 - Fully Compliant
🟡 - Partial Compliant
🔴 - Not Compliant
⚪ - Requires Further Human Verification
🏷️ - Compliance label

[qodo-free-for-open-source-projects]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Impact
General	✅ Simplify and improve directory cleanup logic Suggestion Impact: The commit implemented the core intent of the suggestion by replacing the wildcard-based cleanup (`rm -rf dir/*`) with a more robust approach. However, instead of using `rm -rf dir && mkdir -p dir` as suggested, the commit used `git clean -fd` to remove untracked files while preserving git-tracked content. The explicit dotfile cleanup for `.srtd.buildlog.json` was removed as suggested, though `.srtd.buildlog.local.json` cleanup was retained. The mkdir commands were also removed since the directories are preserved by git. code diff: -# Prepare clean environment using git -echo "🧹 Preparing clean environment..." +# Reset to clean git state - this gives us the 3 shipped templates + migrations +echo "🧹 Resetting to clean git state..." git checkout -- "${DEMO_PATHS[@]}" 2>/dev/null || true -rm -rf supabase/migrations-templates/* -rm -rf supabase/migrations/* +git clean -fd supabase/migrations-templates supabase/migrations 2>/dev/null || true rm -f srtd.config.json # CRITICAL: Clean up buildlog files to ensure fresh state # Without this, SRTD may not detect template changes from previous runs -rm -f supabase/migrations-templates/.srtd.buildlog.json rm -f supabase/migrations-templates/.srtd.buildlog.local.json -# Copy demo templates -echo "📝 Setting up demo templates..." -mkdir -p supabase/migrations-templates -mkdir -p supabase/migrations Simplify the cleanup logic by removing and recreating the supabase/migrations-templates directory to ensure all files, including hidden ones, are properly deleted. scripts/record_demo.sh [52-64] -rm -rf supabase/migrations-templates/* -rm -rf supabase/migrations/* +rm -rf supabase/migrations-templates +rm -rf supabase/migrations rm -f srtd.config.json - -# CRITICAL: Clean up buildlog files to ensure fresh state -# Without this, SRTD may not detect template changes from previous runs -rm -f supabase/migrations-templates/.srtd.buildlog.json -rm -f supabase/migrations-templates/.srtd.buildlog.local.json # Copy demo templates echo "📝 Setting up demo templates..." mkdir -p supabase/migrations-templates mkdir -p supabase/migrations [To ensure code accuracy, apply this suggestion manually] Suggestion importance[1-10]: 6 __ Why: The suggestion correctly identifies that rm .../* doesn't remove dotfiles and proposes a more robust and idiomatic shell pattern (rm -rf dir && mkdir -p dir), which simplifies the script and makes it more future-proof.	Low
Update

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 80.17%. Comparing base (19263d3) to head (9ec591a).
⚠️ Report is 1 commits behind head on main.
✅ All tests successful. No failed tests found.

Additional details and impacted files

@@           Coverage Diff           @@
##             main      #66   +/-   ##
=======================================
  Coverage   80.17%   80.17%           
=======================================
  Files          46       46           
  Lines        2229     2229           
  Branches      551      551           
=======================================
  Hits         1787     1787           
  Misses        442      442           

Flag	Coverage Δ
e2e	80.17% <ø> (ø)
unittests	80.17% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.