v0.11.0: HabitAgility rebrand complete - infra renamed end-to-end + docs rewritten

Infrastructure renamed: HabitAgilityCert + HabitAgility stacks (was GoodHabitTrackerCert + GoodHabitTracker). DynamoDB: habit-agility-meta + habit-agility-rows. Lambda: habit-agility-sync, habit-agility-auth. S3: habit-agility-app-{account}. Construct IDs cleaned up too: MetaTable + RowsTable replace the misleading CyclesTable + CheckinsTable.

Old stacks destroyed via 'aws cloudformation delete-stack' (data was wiped earlier so no migration needed). Lambda@Edge replicas of the old auth function need ~hours to age out before AWS will let the function itself be deleted; retained from the stack via --retain-resources and will self-clean. Old DDB tables and S3 bucket survived stack delete via RemovalPolicy.RETAIN and will be cleaned up out-of-band.

Repo renamed: StevenEmelander/HabitAgility (PascalCase matching the brand, replaces the kebab-case habit-agility from v0.10.4). Local git remote updated; GitHub auto-forwards.

Documentation rewrite: README.md is now a product-marketing landing page (streaks-vs-HabitAgility table, concept glossary, three-tab overview, privacy + ownership section, quick-start, architecture diagram, roadmap). CLAUDE.md updated for v0.11 infra names. CONTRIBUTING.md sharpened around CI-only deploys, rollback recovery, and the pure-helpers-in-their-own-module pattern for testability.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Author: StevenEmelander

CHANGELOG.md

@@ -4,6 +4,76 @@ All notable changes to this project are documented here.
 
 ## [Unreleased]
 
+## [0.11.0] - 2026-05-19
+
+Full rebrand to HabitAgility — completes what v0.10.4 started. **AWS
+infrastructure renamed end-to-end**, repo renamed to PascalCase (matches brand),
+and **all documentation rewritten with a product-marketing voice** instead of
+the previous "personal notes" tone.
+
+### Documentation rewrite
+
+- **README.md** — rewritten from scratch as a marketing landing page. Hero
+  pitch ("treat your habits like a Scrum team treats their work"). Streaks-vs-
+  HabitAgility comparison table. Concept glossary (Sprint / Velocity /
+  Granularity / Burndown / PACE / Retrospective / Planning). Tab-by-tab
+  feature overview. Privacy + ownership section. Quick-start, architecture
+  diagram, costs, shipped + roadmap sections. The repo now reads like an
+  *invitation* to fork and run, not a maintenance log.
+- **CLAUDE.md** — fully aligned to v0.11 infra names; new "Brand vs infra"
+  table is now a single column (all HabitAgility); explicit list of bulk-
+  endpoint / streak / telemetry anti-patterns under "What to avoid".
+- **CONTRIBUTING.md** — sharpened around the deploy-is-CI-only rule, the
+  cross-region rollback recovery procedure, and the new pure-helpers-in-their-
+  own-module pattern that lets `tests/` import without the AWS SDK.
+
+### Infrastructure rename (the big one — full destroy + recreate)
+
+- **CDK stacks renamed**: `GoodHabitTrackerCert` → **`HabitAgilityCert`**,
+  `GoodHabitTracker` → **`HabitAgility`**. The old stacks were deleted via
+  `aws cloudformation delete-stack` after the prior data wipe (no entries or
+  sprint defs to migrate).
+- **DynamoDB tables renamed**: `good-habit-tracker-cycles` → **`habit-agility-meta`**,
+  `good-habit-tracker-day-checkins` → **`habit-agility-rows`**. Construct IDs
+  also renamed for clarity (`CyclesTable` → `MetaTable`, `CheckinsTable` →
+  `RowsTable`) — the new names match what each table actually holds in the
+  current schema (meta row vs DAY/SPRINT_DEF/SPRINT_SUM rows).
+- **Lambda functions renamed**: `good-habit-tracker-sync` → **`habit-agility-sync`**,
+  `good-habit-tracker-auth` → **`habit-agility-auth`**.
+- **S3 bucket renamed**: `good-habit-tracker-app-{account}` →
+  **`habit-agility-app-{account}`**.
+- **Stack interface renamed**: `GoodHabitTrackerStackProps` → `HabitAgilityStackProps`;
+  class `GoodHabitTrackerStack` → `HabitAgilityStack`; `CertStack` →
+  `HabitAgilityCertStack`.
+- **Lambda env-var names retained** (`CYCLES_TABLE_NAME`, `ENTRIES_TABLE_NAME`)
+  to avoid changing the lambda source in this release. The names are now
+  misleading; they'll be renamed to `META_TABLE_NAME` / `ROWS_TABLE_NAME` in
+  a follow-up patch alongside their `require()` consumers in `constants.js`.
+
+### Orphan resources from the destroy
+
+- **`good-habit-tracker-auth` Lambda@Edge** remained after stack delete
+  because edge replicas take hours to clear; it's a no-op orphan and was
+  detached from the deleted stack via `--retain-resources`. AWS will let it
+  delete cleanly in a few hours.
+- **Old DDB tables and S3 bucket** were `RemovalPolicy.RETAIN`; they survived
+  the stack delete as empty orphans. Cleaned up out-of-band via the AWS CLI
+  after the new stacks deploy successfully.
+
+### GitHub repo rename
+
+- `StevenEmelander/good-habit-tracker` → `StevenEmelander/habit-agility` (in
+  v0.10.4) → **`StevenEmelander/HabitAgility`** (in v0.11, PascalCase matching
+  the brand exactly). Old URLs auto-forward; local git remote updated.
+
+### `package.json` updates
+
+- Root `package.json`: name `good-habit-tracker` → `habit-agility`, version
+  bumped to 0.11.0.
+- `infrastructure/package.json`: name `good-habit-tracker-infrastructure` →
+  `habit-agility-infrastructure`, version bumped to 0.11.0.
+- Lockfiles regenerated.
+
 ## [0.10.4] - 2026-05-19
 
 Rebrand + Scrum-vocabulary alignment + Plan-tab date compaction.

CLAUDE.md

@@ -1,34 +1,91 @@
-# Contributing
+# Contributing to HabitAgility
 
-Thanks for your interest in this project.
+Thanks for your interest! HabitAgility is a personal-use product, but the repo
+exists so you can fork it. The code is small and intentional — the contribution
+guidelines below match.
 
 ## Principles
 
-- Keep the app in a **single file**: `app/tracker.html` (inline CSS/JS, no frameworks or CDN assets).
-- Prefer **small, focused changes** over drive-by refactors.
-- Do not commit **secrets**: `unlock_token` is only passed at deploy time (`--context unlock_token=...` or `UNLOCK_TOKEN` in the deploy scripts). Never paste real tokens into issues or PRs.
+- **Single-file shell.** `app/tracker.html` is the only HTML — inline CSS/JS or
+  small ES modules under `app/scripts/`. No frameworks. No CDN assets.
+- **Strict per-item REST.** API endpoints under `/api/*` operate on one row at
+  a time. No bulk endpoints. No DynamoDB Scans on read paths. See
+  [CLAUDE.md](./CLAUDE.md) for the current route list.
+- **Cloud-first.** No `localStorage` for tracker data. Boot loads exactly two
+  rows; everything else is lazy.
+- **Small, focused diffs.** Avoid drive-by refactors mixed into feature changes.
+- **No secrets in the repo.** `UNLOCK_TOKEN` is passed only at deploy time —
+  `--context unlock_token=...` or `UNLOCK_TOKEN` in the deploy script. Never
+  paste real tokens in commits, issues, or PR descriptions.
 
 ## Local checks
 
-From `infrastructure/`:
+```bash
+npm ci                              # root: lint + test deps
+npm run check                       # Biome (format + lint)
+npm test                            # Vitest (101 tests)
+
+cd infrastructure
+npm ci
+npx cdk synth --context unlock_token=ci-synth-only --quiet
+```
+
+The first `synth` against a fresh checkout may write `infrastructure/cdk.context.json`
+(the `HostedZone.fromLookup` cache). That file is committed in this repo so
+synth is reproducible across machines and CI.
+
+## Deploy is CI-only
+
+Local `cdk deploy` is **denied** by `.claude/settings.json` + a `PreToolUse`
+hook (`.claude/block-local-deploy.js`). Deploys go through GitHub Actions:
+
+```bash
+git tag 0.11.1
+git push origin 0.11.1
+```
+
+The `.github/workflows/deploy.yml` workflow runs `cdk deploy --all` against
+the `production` environment. The required secrets are `AWS_ACCESS_KEY_ID`,
+`AWS_SECRET_ACCESS_KEY`, and `UNLOCK_TOKEN`.
+
+If a deploy fails mid-stream and CloudFormation gets stuck in
+`UPDATE_ROLLBACK_FAILED` on `ExportsWriteruswest2…`, the recovery is:
 
 ```bash
-npm install
-npm run build
-npx cdk synth --context unlock_token=dummy-token-for-synth-only
+aws cloudformation continue-update-rollback \
+  --stack-name HabitAgilityCert --region us-east-1 \
+  --resources-to-skip ExportsWriteruswest209BD44F0A7CF058B
 ```
 
-The first `synth` / deploy that uses `HostedZone.fromLookup` may create `cdk.context.json` (ignored by git). That is expected.
+then re-run `cdk deploy --all` via CI.
 
 ## Forking and your own domain
 
-The CDK stacks assume a Route 53 hosted zone and DNS names wired in code:
+The CDK stacks assume a Route 53 hosted zone and DNS names wired in code:
 
-- `infrastructure/lib/cert-stack.ts` — ACM certificate domain, auth asset generation
-- `infrastructure/lib/stack.ts` — CloudFront alternate domain, Route 53 `A` record name
+- `infrastructure/lib/cert-stack.ts` — ACM cert domain, Lambda@Edge auth asset
+- `infrastructure/lib/stack.ts` — CloudFront alternate domain, Route 53 ARecord
 
-Update those to match your zone and hostname before deploying. Search the repo for `ght.vexom.io` and `vexom.io` as a starting point.
+Search the repo for `ght.vexom.io` and `vexom.io` and replace with your zone +
+subdomain before deploying. (Future: parameterize via `cdk.json` context so a
+fork doesn't need to edit source — see roadmap in README.)
+
+## Adding a test
+
+The `tests/` directory is at the repo root and contains pure-function tests
+against both the front-end and the lambda. New utility helpers should land
+with tests — see `tests/lambda-sprint-helpers.test.js` for the pattern (pure
+helpers extracted from a handler module so the test loads without the AWS SDK
+at the test runner's resolution scope).
 
 ## Maintainer notes
 
-See [CLAUDE.md](./CLAUDE.md) for architecture, data schema, and editing conventions shared with automation tools.
+[CLAUDE.md](./CLAUDE.md) is the architecture + editing-conventions doc shared
+between human contributors and coding agents. It records:
+
+- The strict per-item REST contract
+- DynamoDB partition design and attribute conventions
+- Which AWS constructs are stable IDs and which can be renamed safely
+- Token-rotation deploy procedure + recovery steps
+- The "user-facing HabitAgility / infra `good-habit-tracker`" rule from before
+  v0.11 (resolved in v0.11 — see CHANGELOG)