docs(plans): record the Google sign-in plan where the other plans live #357

2026-09-12T07:13:24-05:00

bermudalamb commented

2026-09-12 07:13:24 -05:00

The plan for this feature existed as a published page and nowhere in the repository, which made it the only sizeable piece of work here with no record beside its siblings in docs/superpowers/plans.

docs/superpowers/plans/2026-09-09-google-sign-in.md, written to that folder's conventions: dated filename, goal and architecture up front, global constraints, the file structure, then the phases as tasks.

The boxes are checked rather than open. All six phases merged before this was written, and an implementation plan full of unticked work that is already done reads as a to-do list nobody started.

It is a record rather than a reconstruction. The file list comes from the commits themselves, and a check confirms every one of the 21 paths it names exists in the tree.

The corrections section is the part worth keeping

Two things the plan asserted turned out to be false, and both are written down rather than quietly fixed:

QA could never run this feature. It can. That claim cost a deploy and put the wrong constraint into a compose file and two issues.
Local development should register the port 3000 callback. It browses the Vite dev server on 5173, so that is the URI the server sends. The omission cost an hour of redirect_uri_mismatch.

A plan that silently stops saying something teaches nobody why it said it.

It also records the two smaller corrections made during the work — account deletion never asked for a password, and the button was initially missing from the sign-up tab — and the three follow-ups deliberately not built: unlinking, Apple, and One Tap.

Testing

Every file path named in the document exists. No code changes.

🤖 Generated with Claude Code

The plan for this feature existed as a published page and nowhere in the repository, which made it the only sizeable piece of work here with no record beside its siblings in `docs/superpowers/plans`. `docs/superpowers/plans/2026-09-09-google-sign-in.md`, written to that folder's conventions: dated filename, goal and architecture up front, global constraints, the file structure, then the phases as tasks. **The boxes are checked rather than open.** All six phases merged before this was written, and an implementation plan full of unticked work that is already done reads as a to-do list nobody started. It is a record rather than a reconstruction. The file list comes from the commits themselves, and a check confirms every one of the 21 paths it names exists in the tree. ## The corrections section is the part worth keeping Two things the plan asserted turned out to be false, and both are written down rather than quietly fixed: - **QA could never run this feature.** It can. That claim cost a deploy and put the wrong constraint into a compose file and two issues. - **Local development should register the port 3000 callback.** It browses the Vite dev server on 5173, so that is the URI the server sends. The omission cost an hour of `redirect_uri_mismatch`. A plan that silently stops saying something teaches nobody why it said it. It also records the two smaller corrections made during the work — account deletion never asked for a password, and the button was initially missing from the sign-up tab — and the three follow-ups deliberately not built: unlinking, Apple, and One Tap. ## Testing Every file path named in the document exists. No code changes. 🤖 Generated with [Claude Code](https://claude.com/claude-code)

bermudalamb added 1 commit 2026-09-12 07:13:24 -05:00

docs(plans): record the Google sign-in plan where the other plans live

SonarQube Analysis / sonarqube (pull_request) Failing after 28m42s

Details

Linting / lint (pull_request) Successful in 3m11s

Details

1838bb38d1

The plan for this feature existed as a published page and nowhere in the repository, which made it the only sizeable piece of work here without a record beside its siblings in docs/superpowers/plans.

Written to that folder's conventions — dated filename, goal and architecture up front, global constraints, the file structure, then the phases as tasks. The boxes are checked rather than open, because all six phases merged before this was written and an implementation plan full of unticked work that is already done would read as a to-do list nobody had started.

It is a record rather than a reconstruction. The file list is taken from the commits themselves rather than from memory, and a check confirms every path it names exists.

The corrections section is the part worth keeping. Two things the plan asserted turned out to be false, and both are written down rather than quietly fixed: that QA could never run this feature, which cost a deploy and put the wrong constraint into a compose file and two issues; and that local development should register the port 3000 callback, when the dev server it actually browses is on 5173. A plan that silently stops saying something teaches nobody why it said it.

Also records the two smaller corrections made during the work — that account deletion never asked for a password, and that the button was initially missing from the sign-up tab — and the three follow-ups that were deliberately not built.

Verified: every file path named in the document exists in the tree.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Some required checks failed

Linting / lint (pull_request) Successful in 3m11s

Details

SonarQube Analysis / sonarqube (pull_request) Failing after 28m42s

Details

You are not authorized to merge this pull request.

This pull request can be merged automatically.

View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.

git fetch -u origin docs/google-sign-in-plan:docs/google-sign-in-plan

git checkout docs/google-sign-in-plan

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: bermudalamb/redefined-designs#357