[brsbl]

What changed

• Choose a time zone when creating a Content calendar; existing calendars retain their zone.
• New items start without a format and remember your choice. Setup guidance and examples apply to any user.
• The overview explains Google setup, secret settings, metadata storage, and optional file/Moss attachments.

Verification

• Final plugin checks and both repository-wide install-validation passes succeeded. CI run.
• Isolated install: unconfigured setup, fake OAuth, timed moves, format persistence, gates, links, disconnect, and reconnect passed.
• Chrome for Testing 155.0.8059.39: final setup, fake connection, and neutral File label passed without page errors.
• All four credential settings remained masked; verification used only loopback fake Google.
• Version-tag publishing is prepared for content-calendar/v0.1.4; publication remains with the release lead.

Isolated verification provenance

Isolated bb: upstream main 46da8461c107ee9dc95480a16fa17decaca2cc5d, dependencies installed first, fresh temporary data, no live Google credentials. First artifact 399732124d008eb7b58b04f344d1d5015f745b4d covered the full connection flow. Final artifact 670e6aa97e76f9903779f780d6f38ec71dc78bd4 was generated by the install-ref publisher from source 0e9f9b68 and installed by immutable commit; the follow-up changed documentation and attachment labels only. Tokyo’s current day was October 19 while UTC was still October 18; both the UI and posting an undated item used October 19. Changing the new-calendar setting to London and reconnecting retained the Tokyo calendar and its items.

Live inspection showed that generic file attachments work on connected machines; macOS is required only for the Moss opener. No existing note was opened or captured. No offline-host result or real-Google authentication result is claimed. No images were modified, no tags pushed, and no merge or marketplace publication performed.

Screenshots needed

A separate screenshot worker owns all captures and image changes. Use an isolated bb with the local install artifact and fake Google only. Replace the existing month, week, and inline images; do not reuse their content.

• Unconfigured setup: blank secret settings; show the client requirements, time-zone instruction, and disabled Connect button.
• Month calendar: October 2026 with Workshop announcement, Workshop guide, Workshop recap, Evergreen checklist, and Interview idea.
• Week calendar and item details: week of October 19, with a text gate and a synthetic brief URL on Workshop guide.
• Inline calendar: the same synthetic week inside an isolated fixture conversation, with no personal sidebar content.

Synthetic fixture recipe

Start plugins/content-calendar/fake-google-server.ts 47963 with the isolated bb checkout's tsx binary, through host-care. Start the fresh isolated bb with BB_CONTENT_CALENDAR_FAKE_GOOGLE=http://127.0.0.1:47963. No production data or credentials.

Run every command below against that isolated server. Set clientId=fixture-client, clientSecret=fixture-secret, and timeZone=Asia/Tokyo with bb plugin config content-calendar set. Capture the unconfigured state before setting credentials. Run bb content-calendar connect --json, open its loopback fake authorization URL, and paste the redirect into bb content-calendar connect --paste. This creates only an in-memory fake calendar.

bb content-calendar add 'Workshop announcement' --format tweet --date 2026-10-19 --status ready
bb content-calendar add 'Workshop guide' --format blog --date 2026-10-21 --status drafting
bb content-calendar add 'Workshop recap' --format none --date 2026-10-23 --status posted
bb content-calendar add 'Evergreen checklist' --format none --tray evergreen
bb content-calendar add 'Interview idea' --format essay --tray later

Use the returned Workshop guide item ID for:

bb content-calendar gate add ITEM_ID --text 'Review outline'
bb content-calendar attach ITEM_ID --url https://example.com/workshop --title 'Workshop brief'
bb content-calendar view --week 2026-10-19

Render the returned directive in a fixture conversation. Capture real product surfaces at least 1200px wide, at most 2 MiB each. Use URL attachments in these captures. Do not open the file picker on a host with existing personal notes; a fresh bb data directory does not isolate the host filesystem. Use a neutral sidebar and synthetic machine labels only; do not expose local paths, identifiers, email addresses, account details, or unrelated conversations.

Screenshots

Before: main 0cd4457, described in text because those images show a real content plan and machine name · After: 4d36593 · Captured at 2× from an isolated bb (get-bb/bb main 46da8461) with this PR's build installed from source, fake Google Calendar, and sample data only

Screen / state	Viewport	Before	After
Setup / not configured	Desktop · 1100×720	No setup capture; the README showed only the month view
Calendar / month	Desktop · 1440×900, sidebar collapsed	Month view of a real content plan (image withheld)
Calendar / week with item details	Desktop · 1440×900, sidebar collapsed	Week view of a real content plan (image withheld)
Conversation / inline week	Desktop · 1440×900	Inline calendar in a real conversation with a named Mac (image withheld)

BB-Thread-ID: thr_uu9geeuhef

AGENT GENERATED

[brsbl]

Superseded by #527, which ships this change together with the other plugins in one release. This PR's exact head is merged into #527 unchanged. The branch is kept.