Reconnect Vercel native Git deploy; refresh README/architecture/agent docs for v1.1 - #3
Merged
Merged
Conversation
…ect Vercel native Git deploy Production had drifted 2+ hours behind master — the Variant B cockpit workbench was merged and never actually deployed, because Vercel's native Git-triggered deploy was disabled (`vercel.json` `deploymentEnabled: false`) after an earlier failure, and every deploy since has been a manual `vercel deploy --prebuilt`. Root-caused the original failure: the Vercel project's Output Directory was still `public`/`.` (a zero-config default that's wrong for this pnpm monorepo — the built app lives at `apps/web/dist`). Fixed via the Vercel API: Build Command `pnpm build`, Output Directory `apps/web/dist`, Install Command `pnpm install --frozen-lockfile`, Framework Preset Vite. Re-enabled `deploymentEnabled: true` — master now redeploys production automatically on every merge, the actual "native Vercel solution". Docs and screenshots were describing the v1.0-era app three commits' worth of shipped work behind reality (design-sync-v2, the Variant B cockpit workbench, and initializer-value visibility never got a README/architecture pass). Fixed: - README: new hero screenshot of the current cockpit-bar workbench (source↔assembly sync, live storage strip with a real byte-diff, cockpit bar, execute strip, share, challenges — all in one shot); rewrote the feature list to cover settings, the live storage strip, constructor-value visibility, revert forensics, events, challenges, and session v2; fixed the package table (was missing executor, semantics, challenges, lifecycle) and stale doc links (limitations-v0.1 → v1.0). - docs/architecture.md: updated the dependency diagram and package table for the four packages added since v0.2; fixed the data-flow description for settings-aware compiles and session v2. - CLAUDE.md / AGENTS.md: same package-list and doc-link fixes (mirrored per this repo's own convention, since the files aren't symlinked), plus the new branch-protection and native-deploy facts in the workflow rules. - CONTRIBUTING.md: "git pushes never deploy" was true when written and is no longer true; documented the actual required-checks list for the now-protected `master` and the native deploy path. - Removed 18 orphaned ad-hoc debug screenshots from `.playwright-screens/` (unreferenced by any doc) now that the repo is public; kept the one historical release-evidence image `v0.5-semantics.png` untouched. Leak audit (prompted by the repo going public): scanned all tracked files and full git history for credential files, API keys, tokens, private keys, and connection strings — clean. `.beads/interactions.jsonl` contains only issue-audit metadata (status changes, actor username already public as the repo owner), no secrets. CHANGELOG: already covered by the 1.1.0 entry added alongside the initializer-value-visibility commit. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Production had drifted 2+ hours behind master: the Variant B cockpit workbench (PR #1) and the constructor-value-visibility feature (PR #2) were both merged but never deployed, because Vercel's native Git-triggered deploy has been disabled since early in the project (
vercel.json→deploymentEnabled: false, after an earlier auto-deploy failure). Every deploy since has required a manualvercel deploy --prebuilt, which I forgot to run after the last two merges.Vercel fix
Root-caused the original failure: the Vercel project's Output Directory was still the zero-config default (
public/.) — wrong for this pnpm monorepo, since the built app lives atapps/web/dist. Fixed the actual project settings via the Vercel API:npm run build(fallback)pnpm buildpublicor.apps/web/distpnpm install --frozen-lockfilevercel.json'sgit.deploymentEnabledflips back totrue— master now redeploys production automatically on every merge. Root Directory was already correctly.and the GitHub↔Vercel connection already existed; only the flag and the build settings were wrong.Docs
README,
docs/architecture.md,CLAUDE.md, andAGENTS.mdwere all describing the v1.0-era app — three merges' worth of shipped work (design-sync-v2, the Variant B cockpit workbench, constructor-value visibility) never got a documentation pass:executor,semantics,challenges,lifecycle) and stale links fixed (limitations-v0.1.md→v1.0.md).CONTRIBUTING.md's "git pushes never deploy" was true when written, isn't anymore — documented the actual required-checks list for the now-protectedmasterand the native deploy path..playwright-screens/(unreferenced by any doc) now that the repo is public; kept the one image a release doc actually cites as evidence.Leak audit
Prompted by the repo going public earlier this session: scanned every tracked file and the full git history for credential files, API keys, tokens, private keys, and connection strings. Clean.
.beads/interactions.jsonl(bd's audit trail) contains only issue status-change metadata and the actor username, which is already public as the repo owner.Changelog
Already covered by the
1.1.0entry from PR #2 — no gap.Verification
pnpm format:checkclean🤖 Generated with Claude Code