docs: post-convoy cleanup for drop-public-setup #14
No reviewers
Labels
No labels
agent-context-drift
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: rstillwell/deckhearth#14
Loading…
Reference in a new issue
No description provided.
Delete branch "docs/drop-public-setup-cleanup"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Post-merge documentation cleanup for the just-shipped
drop-public-setupconvoy (PR #13, P0 #3). Small focused pass; no behavior changes.3 files, +13/-5 lines:
AGENTS.mdff80753+b63b509), document as-shipped behavior, Brief 2's CJS→ESM Node 22.x fix, and the R1 operator caveat. Entry kept (not renumbered) per the same convention used for resolved gotchas #2, #3, #5.ADMIN_INITIAL_PASSWORDto env-var template list with a note that setup-db exits 1 if it's unset.convoys/ship-readiness.mdpurge-weak-creds-from-helpers.cursor/rules/no-go-zones.mdcscripts/setup-neon-db.js.drop-public-setupset the precedent that operational changes (env-var gating, pre-flight validation, module-system fixes) are allowed in place, while DDL changes still need a separate migration script. Future agents shouldn't have the same Decision-B confusion the architect did.What did NOT change
package.json,package-lock.jsonlib/**,pages/**,components/**,scripts/**.github/**README.md— already updated in PR #13.cursor/rules/auth-and-permissions.mdc,.cursor/rules/api-routes.mdc— these were updated in thefix-auth-bypassdoc-writer pass (PR #12); nothing new fordrop-public-setupto add there.cursor/rules/db-and-schema.mdc— its mention ofsetup-neon-db.js("bootstrap DDL — idempotent") is still accurate; no changeTest plan
AGENTS.mdrendering on GitHub — confirm Gotcha #4's RESOLVED block reads cleanly alongside the existing #2/#3/#5 entries.convoys/ship-readiness.mdP0 #3 — confirm RESOLVED block + R1 caveat are visible.cursor/rules/no-go-zones.mdcschema-vs-operational distinction is clear🤖 Generated with Cursor
Made with Cursor
The latest updates on your projects. Learn more about Vercel for GitHub.
Pipeline Health
Build + CI gates
Build runs on Vercel; this CI runs lint and schema-map drift only (no duplicate build).
Role reports
See individual comments above for details. This rollup updates automatically.