fix(profile): default profile actually 'standard' (align stale 'pro' default refs)

[sgwannabe]

Summary

/pf:new was silently spinning up the pro profile (18 previews · 3×5 eng · ~70min) when users expected the standard demo path (9 previews · 2×5 eng · ~25min). User-reported during demo prep.

Root cause

settings.json.pf.defaultProfile has been "standard" since v1.4.0 (LESSON 0.10 — demo-first UX flip). But several markdown / Python files still claimed "pro" as the default. LLM agents reading commands/new.md and ideation-lead.md trust the markdown over the JSON config, so the documented (stale) default won.

Fix

File	Change
commands/new.md	examples + flag table + comparison table + flow §7 all corrected to standard; explicit "use --profile=pro|max" + PF_PROFILE=pro env-var examples added
agents/ideation/ideation-lead.md L110	profile-resolve doc updated; LESSON 0.10 cross-ref
hooks/cost-regression.py L46-60	docstring + 3 fallback branches "pro" → "standard" (matches settings.json shipped value)
schemas/pf-profile.schema.json	description: "pro (default)" → "standard (default since v1.4)"

Plus an unrelated chore: untrack .claude/scheduled_tasks.lock (accidentally included in first push) + gitignore.

How to opt into pro/max from the start (now documented)

/pf:new "..." --profile=pro
/pf:new "..." --profile=max
PF_PROFILE=pro /pf:new "..."

Side effects

• bash scripts/verify-plugin.sh → 58 Pass / 0 Fail (unchanged)
• No advocate boilerplate impact
• Historical references in LESSONS.md / CHANGELOG.md preserved (they document the flip itself)
• Fresh /pf:new invocations now hit the documented intended UX

Codex review

Skipped — documentation/string alignment, no behavior change beyond fixing the silent contradiction.

[gemini-code-assist]

Warning

You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again!

[coderabbitai]

Warning

Rate limit exceeded

@sgwannabe has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 31 minutes and 31 seconds before requesting another review.

Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 31 minutes and 31 seconds.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: c4312bd3-a747-4008-a834-60dc5a38ce16

📥 Commits

Reviewing files that changed from the base of the PR and between f87ab33 and b8713f6.

📒 Files selected for processing (5)

• .gitignore
• plugins/preview-forge/agents/ideation/ideation-lead.md
• plugins/preview-forge/commands/new.md
• plugins/preview-forge/hooks/cost-regression.py
• plugins/preview-forge/schemas/pf-profile.schema.json

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/profile-default-stale-docs

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}