docs: spec 00 v2.0 — six-month timeline, AWS/Terraform infra, meeting decisions (2026-07-23)

[HexSleeves]

Summary

Revises docs/specs/00-spec-chapter-11-appdev/00-spec-chapter-11-appdev.md to v2.0, encoding the decisions from the 2026-07-23 planning meeting:

• Timeline: Replaces the "2-3 week chapter budget" constraint with the actual ~six-month bootcamp timeframe for college seniors with no prior app-dev exposure. Overrunning the original chapter estimate is acceptable. Adds an explicit content guideline: front-matter time estimates (estReadingMinutes, exercise estMinutes) must be generous, since students are first-time application developers.
• Infrastructure: Replaces the "no external/paid services, local-only" constraint with: production exercises (Specs 06-08) deploy to the learner's own AWS account via committed Terraform in the repo, no GitHub Actions coupling (the bootcamp is open source), everything self-contained under examples/ so learners cd in and run one command. Documents the researched deployment direction from #921: single EC2 VM running the OTel Demo App's official Docker Compose via thin Terraform (~$1/day while running, clean terraform destroy), with a k3s-on-EC2 fallback if pod-level blue-green is later needed.
• Design decisions: Adds "framework-agnostic; each section uses a different language to highlight one core principle" and "open source — anyone can take it" as explicit key design decisions.
• Spec table: Adds a new standalone Spec 08 (Infrastructure: Terraform/AWS One-Command OTel Demo Environment), numbered consistently with the existing 00-07 scheme, consumed by Specs 06 and 07.
• Status accuracy: Corrects stale status/Next Steps/Current State/Resuming Work text — Spec 01 content is in review (PRs Add Business Logic Patterns documentation and TypeScript examples (11.2.3) #822/Add Classical Gang of Four Patterns documentation and multi-language examples #824/Add Task 4.0: Integrated Refactoring Exercise (11.2.5) #826), Spec 02 content is built (PR Add 11.3 System Thinking section (spec 02) #914) with ARM validation pending (Validate OTel Demo locally on Apple Silicon #920), Spec 03 has a written spec with tasks file in progress (Write spec 03 (Databases) tasks file #919), Spec 04 has round-1 questions in flight (Answer spec 04 (REST API) round-1 questions #918). Links the wayfinder map (Wayfinder map: Chapter 11 App-Dev Bootcamp — specs decision-complete #915) as where open decisions across the chapter are tracked.

Builds on 0211d07 (the maintainer's own table-formatting/revision-history cleanup on add-specs-for-app-dev), cherry-picked as the base commit. ARM-macOS compatibility constraint is unchanged.

Verification

• npx markdownlint-cli2 on the changed file directly: 0 issues
• npm run lint (full repo, which excludes specs/): 0 issues
• Pre-commit hooks (cspell, front-matter condenser, markdownlint) all passed on commit

Closes #916
Refs #915

[coderabbitai]

Warning

Review limit reached

@HexSleeves, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 59 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: b988606b-d1c2-44ae-a582-9bf64e2b77bb

📥 Commits

Reviewing files that changed from the base of the PR and between 025a6de and 54fb21c.

📒 Files selected for processing (3)

• .cspell.json
• CLAUDE.md
• docs/specs/00-spec-chapter-11-appdev/00-spec-chapter-11-appdev.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch spec/00-v2.0

---

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.}