feat(calendar-to-brain): add ClawVisor-backed collector and privacy tests#790
Open
alexandreroumieu-codeapprentice wants to merge 2 commits into
Conversation
5935837 to
b9c5b70
Compare
Author
|
check:wasm appears to fail on Bun’s compiled-binary embedded-WASM runtime path (also reproducible on master). PR #790 only touches calendar-to-brain files and does not modify that codepath. |
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
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.
Summary
Adds a first Calendar-to-Brain collector backed by ClawVisor task output.
This introduces a safe local workflow for turning Google Calendar events into dated Brain source pages under:
What changed
integrations/calendar-to-brain/collector.mjs.Validation
bun test test/calendar-to-brain.test.jsExpected result:
Notes
This PR supersedes the older draft #751 with a smaller first slice.
This PR only introduces the base collector and privacy/safety tests. Preview UX, overwrite protection, and French human-readable dates are intentionally split into follow-up PRs.