fix-env.tsminor (#1261)
# READ CAREFULLY THEN REMOVE
Remove bullet points that are not relevant.
PLEASE REFRAIN FROM USING AI TO WRITE YOUR CODE AND PR DESCRIPTION. IF YOU DO USE AI TO WRITE YOUR CODE PLEASE PROVIDE A DESCRIPTION AND REVIEW IT CAREFULLY. MAKE SURE YOU UNDERSTAND THE CODE YOU ARE SUBMITTING USING AI.
- Pull requests that do not follow these guidelines will be closed without review or comment.
- If you use AI to write your PR description your pr will be close without review or comment.
- If you are unsure about anything, feel free to ask for clarification.
## Description
Please provide a clear description of your changes.
---
## Type of Change
Please delete options that are not relevant.
- [ ] 🐛 Bug fix (non-breaking change which fixes an issue)
- [ ] ✨ New feature (non-breaking change which adds functionality)
- [ ] 💥 Breaking change (fix or feature with breaking changes)
- [ ] 📝 Documentation update
- [ ] 🎨 UI/UX improvement
- [ ] 🔒 Security enhancement
- [ ] ⚡ Performance improvement
## Areas Affected
Please check all that apply:
- [ ] Email Integration (Gmail, IMAP, etc.)
- [ ] User Interface/Experience
- [ ] Authentication/Authorization
- [ ] Data Storage/Management
- [ ] API Endpoints
- [ ] Documentation
- [ ] Testing Infrastructure
- [ ] Development Workflow
- [ ] Deployment/Infrastructure
## Testing Done
Describe the tests you've done:
- [ ] Unit tests added/updated
- [ ] Integration tests added/updated
- [ ] Manual testing performed
- [ ] Cross-browser testing (if UI changes)
- [ ] Mobile responsiveness verified (if UI changes)
## Security Considerations
For changes involving data or authentication:
- [ ] No sensitive data is exposed
- [ ] Authentication checks are in place
- [ ] Input validation is implemented
- [ ] Rate limiting is considered (if applicable)
## Checklist
- [ ] I have read the [CONTRIBUTING](../CONTRIBUTING.md) document
- [ ] My code follows the project's style guidelines
- [ ] I have performed a self-review of my code
- [ ] I have commented my code, particularly in complex areas
- [ ] I have updated the documentation
- [ ] My changes generate no new warnings
- [ ] I have added tests that prove my fix/feature works
- [ ] All tests pass locally
- [ ] Any dependent changes are merged and published
## Additional Notes
Add any other context about the pull request here.
## Screenshots/Recordings
Add screenshots or recordings here if applicable.
---
_By submitting this pull request, I confirm that my contribution is made under the terms of the project's license._Jun 9, 2025, 7:10 PMindex.tsfeat: add helper cliMay 21, 2025, 4:56 AMreinstall-node-modules.tsfeat: add helper cliMay 21, 2025, 4:56 AMsync.tschore: remove the dead Cloudflare scaffolding left over from the AWS migration
There was no live Workers runtime left — no wrangler.toml, no @cloudflare/* dependency, no
wrangler scripts, no Cloudflare CI, and the Env bindings are already AWS-named
(S3Bucket/KVStore/Queue). What remained was scaffolding around it.
Deleted: the `caches` polyfill (including caches.default) and the `scheduler` global, both
with zero references in first-party code AND in node_modules; WorkflowStep.sleep(), never
called by any workflow; the WorkerEntrypoint/RpcTarget/Container exports, zero importers;
the DurableObjectState/Stub/Namespace ambient declarations; nizzy writing .dev.vars (a
wrangler-only convention it was the sole writer of — vite and dotenv read the .env it also
writes); CF_PAGES_COMMIT_SHA, a Cloudflare Pages build var never set on AWS.
Also dropped the vite plugin emitting a Cloudflare Pages `_headers` file. The frontend ships
to S3+CloudFront now, so it was uploaded as an inert file. All four of its headers are
already set by the CDK ResponseHeadersPolicy in aws/lib/stacks/app-stack.ts (HSTS, CSP with
frame-ancestors 'none', X-Content-Type-Options, Referrer-Policy) and cache-control comes from
`aws s3 sync --cache-control`. No security regression.
And two docs that had become actively misleading rather than merely stale: they describe
main.ts, sync-worker.ts and aws-primary-mail-runtime.ts (all deleted), call
routes/agent/index.ts "6,300 lines" (it is 202), and present ZeroDriver/ZeroAgent/
ShardRegistry as live Durable Objects. Every phase in the migration plan is already done.
Kept deliberately: aws/scripts/backfill-utils.ts genuinely reads FROM R2 as the migration
source; the cf-migration-phase1/3 regression guards still pass; and the Cloudflare-named
KV/R2 aliases in aws-runtime-bindings and the mail test helpers are AWS adapters wearing old
labels — renaming them is churn, not cleanup.
Co-Authored-By: Claude Opus 5 (1M context) <<email>>Aug 2, 2026, 3:30 PM