Checkpoint commits use placeholder git identity, breaking Vercel deployments on private repos

[davegomez]

Entire CLI pushes checkpoint branches (e.g. entire/checkpoints/v1) with commits that use placeholder or empty git author/committer identities:

Author: Unknown <unknown@local>
Committer: Unknown <unknown@local>
Subject: Checkpoint: c5d1abb3d68c

and in some cases completely empty:

Author:  <>
Committer:  <>
Subject: carry forward: uncommitted session files

This breaks Vercel's deployment pipeline for private repositories. Vercel requires the commit author to be associable with a GitHub user who is a member of the Vercel team. Since Unknown <unknown@local> (and <>) can't be mapped to any GitHub account, every push to an entire/* branch results in a "Deployment Blocked" error:

The Deployment was blocked because GitHub could not associate the committer with a GitHub user.

I attempted two workarounds on the Vercel side, neither of which fully resolved the issue:

1. ignoreCommand in vercel.json — doesn't work because Vercel's committer authorization check runs before the build step, so the ignore script never executes.
2. git.deploymentEnabled: { "entire/**": false } in vercel.json — the intended solution per Vercel's docs, but the blocked deployment notification still appears.

Expected behavior: Entire CLI should use the repository owner's git identity (or the authenticated user's identity) for checkpoint commits, so they can be associated with a valid GitHub account.

Documentation request: Even if the identity issue is fixed, Entire's checkpoint branches are not meant to be deployed. Every push to an entire/* branch triggers a build on platforms like Vercel, wasting compute. It would be helpful if Entire's docs included a section on how to prevent CI/CD platforms (Vercel, Netlify, etc.) from building checkpoint branches — or if Entire provided a built-in mechanism to opt out of pushing these branches to the remote entirely.