Patrick's Inbox

Created 2026-03-03

Updated 2026-03-20

Tags inboxpatrickworkflow

Review queue. Items are added by Claude when something needs your attention. Mark done [x] and note any decisions.

See WORKFLOW-PROTOCOL.md for how this works.

Open Items

[ ] 2026-04-20 | Form 67 → FluentCRM custom-field sync complete

Added by Claude Code on Asia’s Mac Mini

Asia has completed the Formidable Form 67 → FluentCRM custom-field hook (prerequisite for the Participant Support Layer, Tier 1).

What was done

Two custom fields created in FluentCRM:

Label	Slug	Type
Last segment completed	`last_segm_completed`	text
Last segment completed at	`last_segm_completed_at`	date/text

Note on slug spelling: The slugs are last_segm_completed / last_segm_completed_at — not last_segment_completed. FluentCRM has a character limit on custom field slugs. If you’re writing automations or code that references these fields, use the shortened spelling.

WP Fusion automation on practice.baseworks.com is configured to sync both fields to FluentCRM on every Form 67 submission.

Useful capability to know about

FluentCRM has a “Contact Custom Data Updated” trigger — when a custom field is updated to a specific value. This is the automation trigger you’d use to kick off segment-specific flows (e.g., “when last_segm_completed is set to ‘Segment 3’, enroll in the Segment 4 intro sequence”). Each value/field combination needs its own trigger row.

participant-support-layer-plan — this completes Tier 1 prerequisite item 2
Asia’s inbox item 2026-04-20 21:32 ET (now marked complete)

[ ] 2026-04-19 14:00 ET | Session 3 Summary — Round 1 revision complete, ready for your review

Added by Claude Code on Asia’s Mac Mini

Asia has completed her Round 1 editorial revision of the Session 3 summary. The file is ready for your review and any Round 2 edits before posting.

File: session-3-summary-en
Round 1 revision logged under ## Editorial Notes → ### Round 1 revision (2026-04-18) in the file

What changed in Round 1: Squat added as Form 1; Noémie/Natalie Q&A attribution corrected; Structure focus and Marta’s Q&A significantly expanded; conceptual correction on Simple Cross foot pressure (“opposes” not “drives”); two Key Concepts entries (Intensity Modification, NODAA) relocated into their respective Q&A entries; resources section updated. Six typos also corrected.

Next step: Your Round 2 edits go under ### Round 2 revision below Asia’s notes. Once approved, Group Post section needs to be drafted and posted.

[ ] 2026-04-17 12:00 ET | WPRUS security fix deployed — admin accounts now properly protected + username decision needed

Added by Claude Code on Asia’s Mac Mini

What happened

Asia discovered a serious vulnerability in our WPRUS setup today. When Asia registered a test account asia@cevaco.co on baseworks.com, WPRUS matched the username asia to Asia’s admin account on practice.baseworks.com and overwrote her email, locking her out of practice admin. This happened because WPRUS matches users by username (not email), and we had no role-based protection — the original “mismatched usernames” approach was the intended protection, but it had a gap: any public user registering with a username that collides with an admin’s username on the other site could trigger the overwrite.

This affects you too: if anyone registered basework@whatever.com or patrick@whatever.com on either site, your admin accounts could have been compromised the same way.

What was fixed

Two independent protection layers are now in place on both sites:

Layer 1 — WPRUS role filter The outgoing_roles setting on both sites now whitelists only non-admin roles (subscriber, customer, etc.). The administrator role is excluded, so admin accounts never generate outgoing sync events. Configured via wp eval + update_option('wprus').

Layer 2 — MU plugin: bw-protect-admin-from-wprus.php Deployed to /wp-content/mu-plugins/ on both sites and committed to the changelog repo. Hooks into WordPress core’s wp_pre_insert_user_data filter (fires inside wp_insert_user() before the DB write). If the target user is an administrator and the caller is not a logged-in admin, the plugin restores the user’s original email, password, display name, and URL — the sync update becomes a no-op. This catches the attack vector that Layer 1 misses: a non-admin on Site A with the same username as an admin on Site B.

Layer 2 was needed because WPRUS’s native incoming_roles setting only filters the role-sync action, not create/update actions. We confirmed this by reading the plugin source on the server.

Verified: Asia tested by creating a main@baseworks.com admin on practice, then registering main@cevaco.co (username main) on baseworks.com. Practice admin was untouched. Fix is working.

One decision needed from you — username alignment

Our admin usernames are currently mismatched between the two sites:

Person	baseworks.com	practice.baseworks.com
You	`basework`	`patrick`
Asia	`Pandasia`	`asia`

The mismatch was originally the protection mechanism. With the two layers above, it’s no longer needed for security. Aligning usernames (same username on both sites) would be cleaner — it makes it obvious the accounts belong to the same person and removes any residual ambiguity.

Asia plans to align to pandasia on both sites. What username do you want to use on both sites? Once you decide, let Asia know and she’ll coordinate the rename with a Claude Code session.

No urgency — the sites are fully protected as-is. This is a cleanliness decision.

Where to find the full record

Changelog: changelog-entries/20260417-wprus-admin-role-filter.md
Vault: cross-site-user-sync — Admin Account Protection section rewritten with current architecture
MU plugin: sites/baseworks.com/mu-plugins/bw-protect-admin-from-wprus.php and sites/practice.baseworks.com/mu-plugins/bw-protect-admin-from-wprus.php

[ ] 2026-04-17 11:30 ET | Asia’s comments on People Profiles Aggregation Plan — review requested

Added by Claude Code on Asia’s Mac Mini

Asia has reviewed people-profiles-aggregation-plan and left four comments (marked “Asia’s comment” / “Asia Comment” inline). Summary:

Suggestions:

§4 Identity key — Journal form (form id=61): The Journal on practice.baseworks.com doesn’t store email, only a user ID field. Asia suggests verifying exactly how the user ID is stored in that form, and using it as the secondary identity key (in place of or alongside user_login). The secondary key should be the practice site username/user ID.
§5 Activity tiers — use bw-activity-plugin: The best signal for active/past tier derivation is entries in the BW Activity plugin (historical data already imported for all users). Also: the inquiry tier needs a filter to separate spam/sales from genuine inquiries before implementation.
§8 Person file shape — rename user_id: Since user IDs differ between baseworks.com and practice.baseworks.com, Asia suggests renaming the frontmatter field to practice_site_user_id to avoid ambiguity.

Question needing your answer:

§6 Entry-path categorization: Asia is offering to manually tag CRM contacts using WP-Fusion based on significant categories (she notes CRM has Lead Background / Movement Industry / Lead Source fields but they’re inconsistently populated). She wants to know: should she go ahead and do this categorization for the existing CRM contacts?

→ File: people-profiles-aggregation-plan

[ ] 2026-04-17 | Bot registrations on baseworks.com — CAPTCHA plugin installed, needs Cloudflare API setup

Added by Claude Code on Asia’s Mac Mini

Three bot accounts registered via the WooCommerce My Account page (April 13–15). Usernames/emails were random alphanumeric strings (e.g. 3m3o3kwjw5@gmail.com); two of them registered from the same IP, 8 seconds apart. They auto-logged in via WooCommerce’s immediate-session-on-registration flow without ever setting a password. No purchases were made, but they had access to member-gated content and were synced to practice.baseworks.com via WPRUS.

What’s been done:

All three accounts deleted from baseworks.com and practice.baseworks.com
Plugin installed: Simple CAPTCHA Alternative with Cloudflare Turnstile
Issue documented in CHANGELOG.md in the baseworks-changelog repo

Action needed from you: The Turnstile plugin needs to be connected to Cloudflare to work. You’ll need to generate a Turnstile site key + secret key in your Cloudflare dashboard and enter them in WordPress here:

👉 https://baseworks.com/wp-admin/options-general.php?page=cfturnstile

Steps: Cloudflare dashboard → Turnstile → Add site → copy Site Key and Secret Key → paste into that settings page → save. The CAPTCHA will then appear on the WooCommerce registration form automatically.

[ ] 2026-04-17 09:49 ET | ✅ Done — questionnaire exports now emit `user_login` + new anti-drift rules in place

Added by Claude Code on Patrick’s Mac

This closes your 2026-04-13 09:27 item (“Add user_login to questionnaire export”) for the plugin-side work. You can mark that one done. The skill-side update (Pre-Flight participant map + Phase 4 @mention rewrite) is next and still yours or Asia’s to pick up.

What was shipped

Plugin change — both sites (additive, safe to re-run):

Site	File	Form
baseworks.com	`sites/baseworks.com/mu-plugins/bw-questionnaire-export-cli.php`	40
practice.baseworks.com	`sites/practice.baseworks.com/mu-plugins/bw-questionnaire-export-cli.php`	74

Each export now resolves $entry->user_id (with email fallback via get_user_by('email', …)) and writes three new frontmatter fields when a WP user is found:

user_id: 123
user_login: caitlin_b
profile_url: "https://practice.baseworks.com/members/caitlin_b/"

Absent users → fields stay absent (the session-summary skill should fall back to first name). The parse_frontmatter regex was widened to [a-z0-9_\-]+ so the new keys are readable to detect_changes. user_login added to the change-label map so the update log says “Forum handle changed” instead of “Form re-submitted” when a handle first resolves.

Deployment: The practice plugin had been living only on the server. I pulled the baseline into the repo first (e3e89b9), then committed the modified version (cf2c895), then sudo cp deployed to /var/www/practice.baseworks.com/wp-content/mu-plugins/. md5 matches the repo version. Will activate on the next agents-VPS cron cycle (6x daily).

Anti-drift rules added (per your request)

CLAUDE-INSTRUCTIONS.md §3 “Mirror-From-Server Checklist” — any plugin/snippet/config edited on a server must be scp-ed back into sites/[site]/... and committed. No plugin edit may live only on the server.
Vault CLAUDE.md new section “Code Belongs in the Changelog Repo” — explicitly scopes the vault as knowledge-only and names which categories of code always belong in baseworks-changelog. Vault-native scripts (sync, wikilink checker, agent system) are called out as the permitted exception.

Forks question (your earlier ask)

My recommendation is don’t fork per-site. Monorepo is working — the sites/[name]/... tree already gives clean per-site segregation, and four repos would multiply pull/push coordination without a matching benefit. Revisit only if any one site grows a real CI/build pipeline.

Scan result

I checked the vault for orphan site code and didn’t find any. What’s in ~/Obsidian/baseworks-kb-shared-brain/ is vault-native (sync, indexing, wikilink check) or agent-system infra (CrewAI deploy scripts on the VPS). The only real drift I found was the practice plugin itself — now resolved.

Backups

Practice DB (pre-deploy snapshot): practice-pre-user-login-plugin-20260417-094631.sql, 538 MB, uploaded to B2 cbbpracticesite/practice-baseworks-web/adhoc-backups/. Retention per bucket policy.
Practice plugin (pre-deploy copy): /tmp/bw-questionnaire-export-cli-practice-backup-20260417-094639.php on baseworks-web (server-local only — can delete if not needed).
Baseworks.com side: no server deploy performed there (Form 40 plugin is already under CI/manual control of the mu-plugins folder on that site). If you want me to also mirror-deploy it to baseworks.com server, flag it and I’ll run the same checklist.

Commits (main, `baseworks-changelog`)

c6f04c0 Add user_login/user_id/profile_url to Form 40 questionnaire export
e3e89b9 Mirror bw-questionnaire-export-cli.php baseline from practice.baseworks.com
cf2c895 Apply user_login additive change to Form 74 plugin + doc rule

Vault commit (this inbox update + CLAUDE.md addition) will follow.

Suggested next

Verify on the Spring 2026 cohort after the next cron: open one event-participants/*.md file and confirm user_login is populated for logged-in submitters.
Update /session-summary skill (Pre-Flight map build + Phase 4 @mention rewrite). The data is ready.
Consider whether baseworks.com’s Form 40 plugin also needs the mirror-deploy (currently only the repo was edited on that side).

[ ] 2026-04-13 22:20 ET | Community forums consolidation — paused mid-migration, resume tomorrow

Added by Claude Code on Patrick’s Mac

Status: In progress, safe to resume. Cron on baseworks-agents for forum-content-sync.sh is PAUSED (commented out with # PAUSED 2026-04-13 consolidation migration: prefix). Overnight forum activity will accumulate in BuddyBoss and be picked up on the first sync after re-enable.

Done today:

Fixed a 2026-04-09 script drift (VPS ~/scripts/ had 355 lines of uncommitted DM/SQL/translation code). Pulled running copies back into the repo and repointed cron at the git-tracked location so drift can’t recur (commits 9a2233c, a6b1ed1).
Step 1 of the plan: added build_id_index, new slug/cohort/topic-type helpers, rewrote all four sync functions to match by ID instead of filename, improved DM title generation (df7f972).

Still to do (resume here):

Step 2-auto: write scripts/migrate-community-folders.py (dry-run first) — renames existing files, moves manual-only files, migrates _community-index.md
Step 2-manual: hand-merge three overlapping files (mimi/thread-48, any/topic-21816, terminology/topic-21907)
Step 2e: update external wikilinks + check-wikilinks.py
Step 4: delete 02-areas/community-forums-groups/
Verification: dry-run full sync on VPS, confirm no duplicates
Re-enable cron (remove the paused-prefix from the crontab line)
Changelog entry covering the whole session

Full details: “Current session state” section at the top of 03-resources/plans/community-forums-consolidation-plan.md. Read that first on resume.

[ ] 2026-04-13 09:27 ET | Add `user_login` to questionnaire export — enables forum @mentions in session summaries

Added by Claude Code on Patrick’s Mac

Context: While drafting the Spring 2026 Session 2 group post and reviewing the summary, you raised the idea of referring to participants by their practice platform handles (BuddyBoss @username) wherever they are mentioned, so the names copy-paste into the forum post as live @mentions and pull the connection directly. Currently the session summary skill uses participants’ first names from the transcript, and the questionnaire export at 02-areas/method-admin/audience/event-participants/ captures full names plus form data but no platform login or display handle. As a result, there is no copy-paste-ready handle available to the skill at draft time.

This inbox item documents the implementation ideas so you can configure the participation form / questionnaire to surface the handle.

What’s missing

The questionnaire export plugin (bw-questionnaire-export-cli.php on practice.baseworks.com, exporting Form 74) writes one Markdown file per respondent into 02-areas/method-admin/audience/event-participants/{name}-{date}.md. The frontmatter currently has:

type: event-participant
respondent: Caitlin Bartlett
event: "Montreal Study Group 2026 (Spring Cohort)"
cohort: study-group-spring-2026
source: practice.baseworks.com
date: 2026-04-03
sex: F
age: 35
athletic-level: 2
backgrounds: ["endurance", "yoga"]
…

What’s not there: the WordPress user_login (the slug used in BuddyBoss @mention URLs and autocomplete) and optionally the BuddyBoss display name, profile URL, and user ID.

Implementation idea (smallest viable change)

When the export script processes a Formidable Form 74 entry on practice.baseworks.com, the entry already has a created_by (or user_id) field for logged-in submitters. From that user ID, the plugin can pull the WordPress user object once and write three additional frontmatter fields:

user_id: 123
user_login: caitlin_b              # the @mention handle
profile_url: https://practice.baseworks.com/members/caitlin_b/

Pseudocode for the plugin change in bw-questionnaire-export-cli.php:

$user_id = intval( $entry->user_id );
if ( $user_id ) {
    $user = get_userdata( $user_id );
    if ( $user ) {
        $frontmatter['user_id']     = $user_id;
        $frontmatter['user_login']  = $user->user_login;
        $frontmatter['profile_url'] = bp_core_get_user_domain( $user_id );
    }
}

(bp_core_get_user_domain is the BuddyBoss/BuddyPress helper that returns the canonical member profile URL, which is cleaner than constructing it manually.)

For practice site Form 74 specifically, the field IDs the plugin already maps are 1231–1249. The user mapping is independent of those; it comes from $entry->user_id, not from a form field. So the change is additive and shouldn’t disturb existing field handling.

Edge cases to think about

Anonymous / not-logged-in submissions. If $entry->user_id is 0 (form submitted by a logged-out user via the public form on baseworks.com), there is no WordPress user to look up. The fields stay absent. The session-summary skill should treat the absence as “no handle available” and fall back to the first name. This matters because the same plugin pattern probably applies to the baseworks.com-side export of Form 40, where a lot of submitters won’t have accounts at the time of submission.
User-platform sync after the fact. If a participant submits the questionnaire before they have a practice account (e.g., during enrollment) and only later registers, the export file will permanently lack the handle. Possible fixes:
- Add a one-time backfill CLI command (wp bw-questionnaire-backfill-handles --cohort=study-group-spring-2026) that re-walks existing participant files, looks up users by email in the form data, and patches in user_login if found.
- Or: have the export script always re-resolve handles by email on every run, not just on first export.
Email as the lookup key. If user_id is unreliable, falling back to email lookup (get_user_by( 'email', $entry->user_email )) is a robust secondary path. Form 74 likely has an email field; check the field map.
Privacy. Verify whether event-participants/ is committed to git or gitignored before committing handles. If committed, handles are not particularly sensitive (they’re visible to other cohort members on the platform anyway), but worth a moment of thought.

Skill-side change (after the plugin is updated)

Once user_login is in the participant frontmatter, the /session-summary skill’s Pre-Flight phase can:

Read all 02-areas/method-admin/audience/event-participants/*.md files matching the current cohort (cohort: study-group-spring-2026).
Build an in-memory map: { first_name: user_login } (and { full_name: user_login } for disambiguation when multiple participants share a first name).
During Phase 4 (English Draft), wherever the draft would write a participant’s first name (e.g., “Caitlin asked about…”), also resolve the user_login and emit it as @caitlin_b asked about…, so the forum post auto-mentions on paste.

The skill update would be roughly: in the speaker-attribution section, add a “participant handle resolution” step that consults the cohort participant map and rewrites named mentions to @handle form, with a fallback to plain first name if the handle isn’t found.

Suggested order of operations

You configure the form / plugin. Add the three frontmatter fields to the export plugin (user_id, user_login, profile_url). One-time change to bw-questionnaire-export-cli.php. Re-run the cron once and confirm the new fields show up in the existing participant files, or add a backfill command if the export is one-shot per entry.
Verify on Spring 2026 cohort. Open one or two participant files in event-participants/ and confirm user_login is populated. Spot-check the URL by visiting the profile.
Then I update the /session-summary skill. This adds the participant-map lookup in Pre-Flight and the @mention rewrite in Phase 4. Skill change is straightforward once the data is in place.

Reference

Plugin file: bw-questionnaire-export-cli.php on practice.baseworks.com (mu-plugins)
Cron: /home/patrick/scripts/questionnaire-export.sh on agents VPS, runs 6x daily
Form: Formidable Form 74 (practice.baseworks.com production)
Sample participant file: 02-areas/method-admin/audience/event-participants/caitlin-bartlett-260403.md
Project memory: project-questionnaire-system.md (system overview, v1.1.0 export properties)
Feedback memory: feedback-session-summary-posting-instructor-voice.md (records the @mention gap)

Your action: Decide whether to implement this in the questionnaire export plugin. Once user_login is in the participant frontmatter, ping me and I’ll wire the @mention resolution into the /session-summary skill.

Added by Claude Code on Asia’s Mac Mini

Status update: Asia has posted the Instagram carousel (@baseworks_method) and the Baseworks Facebook page post for the proprioceptive awareness / BRNet 2026 campaign.

Your action: Your personal Facebook post is still to be posted. The draft is in the campaign file — see the ## Facebook — Patrick’s Personal Page section: 02-areas/communications/campaigns/2026-04-proprioceptive-awareness-brnet/2026-04-proprioceptive-awareness-brnet.md

[ ] 2026-04-10 12:00 ET | ImageMagick stroke-state bug — consider adding to carousel skill

Added by Claude Code on Asia’s Mac Mini

What: While polishing the proprioceptive awareness Instagram carousel, Asia noticed text outlines on several slides. Root cause: ImageMagick’s -stroke and -strokewidth are global state within a magick command — once set for a line draw, they silently apply to every subsequent -annotate (text) call unless explicitly reset with -stroke none -strokewidth 0.

Fix applied: Added -stroke none -strokewidth 0 after every -draw "line..." in instagram-carousel-generate.sh. All 7 slides regenerated and preview HTML rebuilt.

Technical note: ImageMagick Bug Note: Stroke State Persists Across Annotate Calls — includes the rule, a full explanation, and a table of other ImageMagick properties that carry state.

Your action: This is a non-obvious gotcha that will affect any future carousel or ImageMagick script we build. Consider whether it belongs in the /create-campaign skill, a dedicated ImageMagick reference note, or both.

2026-04-10

ImageMagick stroke-state bug — consider adding to carousel skill

Inbox cleanup agent deleted an open item — needs investigation

2026-04-09

Site updates: article tagline tag + Last Updated field implemented

2026-04-07

Vault health: 149 broken wikilinks + 244 backtick path warnings — cleanup needed

2026-04-06

Pracstage staging checklist updated — Automator throttling + post-push cleanup

2026-04-05

Karpathy Auto-Research Pattern — Explore for Baseworks

Voice guide draft — Established Teaching Vocabulary (needs your confirmation)

2026-04-03

Primer assignments widget configured for Spring 2026 group (group 5)

2026-04-02

Resume: Calendar setup + Preparation Guide page + Welcome email

2026-04-01

Questionnaire system deployed — Phase 2 plan

2026-03-24

Vault SQLite Index + Git Sync Plan — Ready for Review

2026-03-20

Claude Code Channels — Discord Integration Plan (5 phases)

[ ] 2026-04-10 | Inbox cleanup agent deleted an open item — needs investigation

Added by Claude Code on Asia’s Mac Mini

The automated inbox cleanup agent (commit 21464a5, run 2026-04-10 ~15:15 UTC, author: Baseworks Agent <agents@baseworks.com>) deleted an open [ ] item from Asia’s inbox along with the completed [x] items it was supposed to archive.

What was deleted: 2026-04-10 09:30 ET | Instagram carousel for proprioceptive awareness article — ready for you to polish — this item was open and unreviewed.

What should have happened: Only items marked [x] should be moved to the archive. Open [ ] items must be left untouched.

What was done: The item was restored manually from the git diff and pushed (commit 82ba321).

Action needed: Investigate the cleanup script/agent logic to ensure it only archives completed ([x]) items going forward.

2026-04-09

[ ] 11:45 ET | Site updates: article tagline tag + Last Updated field implemented

Added by Claude Code on Asia’s Mac Mini

Two front-end improvements completed on baseworks.com today.

1. Article tagline changed from H2 to styled P tag

The subtitle/tagline in the article hero was previously rendered as an <h2>. Asia changed it to a <p> tag with identical visual styling in the Elementor template.

Why it was changed: Some articles had duplicate H2s — the hero tagline and the first section heading in the body used the same tag. While Google doesn’t penalize for this (it sees the page as one document; duplicate H2s are neutral-to-slightly redundant, not harmful), it’s semantically incorrect. A deck/tagline below an H1 is descriptive text, not a section opener. Changing it to <p> is the correct semantic structure.

Effect on your articles: Your articles use the tagline/H2 in two ways — some repeat the tagline as the first H2 in the body, some don’t. Both approaches are fine to keep as-is. Inconsistency between articles has no SEO impact (each page is evaluated independently by Google). Feel free to use whichever format suits a given article’s content — no need to standardize.

What changed: The <h2> tag for the hero subtitle in the article template was swapped to <p> with the same CSS class applied. Visually identical.

2. ACF field `article_last_updated` implemented

New custom date field added to the article post type. Display logic in the template:

article_last_updated empty → only “Published [date]” shows
article_last_updated set → shows “Published [date]” and “Updated [date]” on separate lines

The “Originally published” phrasing was intentionally skipped — when there’s no updated date present, “Originally published” reads redundantly. Plain “Published” is cleaner.

Note for /publish-article skill: Worth adding a step to check/set this field when publishing a substantive revision (not needed for typos or minor edits — only when arguments, data, or sections change meaningfully).

2026-04-08

[ ] 03:45 ET | Daily Infrastructure Update Report

Added automatically by daily-infra-updates.sh on baseworks-agents VPS

Date: 2026-04-08

Claude Code updated: 2.1.92 (Claude Code) → 2.1.94 (Claude Code)
baseworks-agents system packages: 3 packages updated
n8n — UPDATE NEEDS ATTENTION: health=unknown, version=unknown
PostgreSQL — UPDATE NEEDS ATTENTION: health=unknown

Backup health:

Site	Schedule	Last Success	Size	Status

| n8n | Daily | 2026-04-04 | 15MB | STALE (4 days) | | baseworks.com | Weekly | 2026-04-05 | DB=544MB, Files=143MB | OK | | staging | Weekly | 2026-04-05 | DB=254MB, Files=141MB | OK | | practice | Weekly | 2026-04-05 | DB=507MB, Files=183MB | OK | | crm | Weekly | 2026-04-05 | DB=38MB, Files=16MB | OK |

Needs your attention:

Warning: n8n update may have failed — health status: unknown
Warning: PostgreSQL update may have failed — health: unknown
Warning: n8n daily backup is 4 days old (last: 2026-04-04)
Warning: Claude CLI authentication failed — vault captures will not work. Check CLAUDE_CODE_OAUTH_TOKEN in ~/.bashrc (must be before the interactive guard)
Warning: n8n cannot SSH to baseworks-agents — vault capture pipeline is broken. Check SSH key at /opt/n8n-ssh/ on baseworks-n8n

Updates applied: 2

Requested action: Review any items flagged above. Auto-updates have already been applied and verified.

[ ] 2026-04-07 22:51 ET | Vault health: 149 broken wikilinks + 244 backtick path warnings — cleanup needed

Added by Claude Code on Patrick’s Mac

The new daily vault audit (now reporting to #agent-alerts in Slack) surfaced pre-existing issues worth addressing. None are urgent or caused by today’s work — they’ve accumulated over time.

Broken wikilinks (149 total)

Top missing targets — these account for most of the breakage:

Missing target	Count	Likely cause
`Micro-Movements`	15	File renamed or never created — referenced across multiple vault captures and forum content
`montreal-film-schools-master-list`	13	All in `02-areas/collaborations/photography-videography-2026/contacts/` — planned file never created
`Sense Control Adapt`	11	Baseworks concept — file may have been renamed or needs to be created
`groups/`	9	Partial path references that don’t resolve
`_index`	8	Old-style index references from before the rename to `index.md`
`posting-job-board`	5	Planned file in photography contacts, never created
`study-group-participant-interview-request`	4	Reference to a planned document
`wikilinks` / `wikilink` / `wiki-links`	6	Example/placeholder text in documentation files (KB-Site logs, etc.) — not real broken links

Other categories:

settings-local-json-backup-patrick-mac-mini-2026-04-07 (3) — the JSON backup file exists but isn’t an .md file, so Obsidian can’t resolve it as a wikilink. Harmless.
image.png, filename, Page (6) — example placeholders in documentation, not real links
Various one-off references to files that were moved or renamed during today’s reorganization

Backtick path warnings (244 total)

These are paths written as `02-areas/path/to/file.md` instead of [wikilinks](/wikilinks/). Many are in CLAUDE.md, setup guides, and technical documentation where backtick paths are appropriate (filesystem references, not navigational links). The audit script flags them but most are intentional.

Recommended approach

Create Micro-Movements.md and Sense Control Adapt.md as Baseworks concept files (or redirect to existing files if they were renamed)
Create montreal-film-schools-master-list.md or remove the dead links from the photography contacts directory
Fix the _index → index references (leftover from the earlier rename plan)
Ignore placeholder links in documentation files (wikilinks, image.png, filename, Page)
Run python3 scripts/check-wikilinks.py after fixes to verify the count drops

Requested action: Pick this up in a future session. Ask Claude Code to fix the broken links starting with the highest-count targets.

2026-04-07

[ ] 22:45 ET | Google Workspace CLI setup — wrong tool installed, needs clarification

Added by Claude Code on Asia’s Mac Mini

Asia tried to follow the setup instructions from the 2026-04-06 inbox item (brew install gws → gws auth login) and got “Not in a workspace” on both commands.

The gws package installed by Homebrew (v0.2.0) is a git workspace manager — completely unrelated to Google Workspace. It has no auth command, no gmail command, and no knowledge of Google APIs. The commands documented in google-workspace-cli-setup don’t correspond to anything this tool can do.

This looks like either:

The CLI tool was referenced by a name that collides with a different Homebrew package
Or the tool is custom/non-standard and needs a different install path

What’s needed from you: Clarify what the actual Google Workspace CLI is and how to install it on Asia’s Mac Mini. The executed plan at google-workspace-cli-setup will need updating too.

Asia’s setup is blocked until this is resolved.

[ ] 22:00 ET | Forum sync + moderation plan — Asia’s review complete, decisions needed

Added by Claude Code on Asia’s Mac Mini

Asia has reviewed the forum content sync setup and the moderation plan. Here are her responses to your five questions:

1. Vault structure — add URLs to forum notes The structure looks good overall. One improvement: vault notes for forum posts should include a direct URL to the live post on the platform. Right now there’s no way to click from a note like 02-areas/practice-platform/community-forums-groups/topics/260305-terminology-ignition-assimilation-orientation.md and land on the actual forum thread. Adding the post URL to each note’s frontmatter or body would make the vault genuinely useful for moderation and reference.

2. Moderation categories — notification timing is the key issue The five categories look fine, but there’s a more fundamental workflow concern: when a post goes live, BuddyBoss sends automatic subscriber notifications immediately. If moderation happens after the fact, subscribers will have already received the alert — and then find the post missing or flagged. Asia’s recommendation: disable automatic post notifications and send them manually after moderation approval. This should be built into the pipeline.

3. Post handling — hide, don’t delete Rather than removing flagged posts, hide them from all users except the author. This serves two purposes: (a) it lets us test the system and catch false positives before they become irreversible, and (b) it avoids the bad experience of someone receiving a notification, clicking through, and finding nothing there.

4. Removal notification email — use support@baseworks.com

5. Content extraction signals — depends on the implementation If this is keyword-based, more specific criteria will be needed. If an AI agent is evaluating posts, the main filter is straightforward: flag content that questions Baseworks’ credibility or intentions, contains insults or hostile language, or goes outside the forum guidelines (participants should be asking questions about the content and sharing their experience, not airing grievances or debating the methodology). This can be the starting brief for the agent.

6. Moderated post retention — keep them, decide case by case Start by keeping moderated posts in the vault with a moderated flag. Don’t try to write a full retention policy now — adjust as real cases come in.

Decisions needed from you:

Is disabling auto-notifications and replacing with post-approval sends technically feasible in BuddyBoss?
What’s the implementation path for content extraction — keyword or AI agent?

[ ] 21:35 ET | Next session: instruction consolidation audit across CLAUDE.md, READMEs, skills, and shared context

Added by Claude Code on Patrick’s Mac

The 03-resources/ reorganization is complete (14 loose files moved into 5 topical subfolders, all references updated, index rebuilt). But during the work, we identified a deeper structural issue: instructions, operational references, and folder indexes overlap and duplicate across multiple locations.

What needs auditing:

CLAUDE.md (vault root + global) — voice guide loading instructions are duplicated in voice-guides/README.md. How much of CLAUDE.md is repeated elsewhere?
agent-system/README.md — contains server IPs, SMTP creds, Slack IDs, kill switch commands. Overlaps with 00-inbox/claude-code-shared-context.md (which is the declared single source of truth). One of these should be authoritative; the other should just point to it.
voice-guides/README.md — instruction guide for loading voice guides. This content is already in both CLAUDE.md files. May be redundant, or could become a skill.
claude-code-skills/index.md vs .claude/skills/ — the Obsidian-visible skills index may be redundant with the actual skills folder structure. Need to decide if both are needed.
README vs index naming — collaborations/README.md is a genuine folder index that should follow the 00-{name}-index.md convention. Root README.md stays (GitHub renders it). The others need to be resolved based on what they actually are.
19 bare index.md files in 02-areas/ + 10 bare [index](/index/) wikilinks — fragile, ambiguous in graph view. Should follow 00-{folder}-index.md convention.

Approach: Plan mode first. Read every overlapping file side by side, map duplications, then propose a consolidation that doesn’t break any session-start behavior for either machine.

Asia has the same inbox item — her input on voice guide and skills organization is relevant.

[ ] 13:30 ET | Vault infrastructure optimization — session summary

Added by Claude Code on Patrick’s Mac

What was done this session:

CLAUDE.md cleanup — Reduced from 225 → 175 lines. Moved backup commands to shared-context, machine identity table to WORKFLOW-PROTOCOL.md, skills creation protocol to skills index. All behavioral rules preserved. Principle: CLAUDE.md is a router, not an encyclopedia.
SQLite relationship index — scripts/build-vault-index.py indexes all wikilinks, tags, frontmatter into vault-index.db. 754 files, 2,133 links, 364 tags. 0.38s full rebuild, 0.02s incremental.
Automated vault sync — scripts/vault-sync.sh replaces Obsidian Git auto-commit. Pull/commit/push every 5 min. Post-sync hook rebuilds index + runs qmd update. Deployed on all machines + VPS.
Vault audit skill — /vault-audit checks CLAUDE.md health, index freshness, qmd status, vault structure, sync status, growth trends. Logs to scripts/audit-log.json.
LightRAG evaluated and deferred — Overkill for ~754 files with explicit wikilinks. Revisit at ~2,000+ files.

Pending:

MacBook Pro setup (commands provided, you said it’s done)
Obsidian Git auto-commit to be disabled after confirming sync stability across all machines
Forum content ingestion (Workstream 4) — separate session planned

Open items flagged by vault audit:

132 broken wikilinks (run check-wikilinks.py for details)
228 single-use tags (possible typos)
47 directories missing index.md
4 stray markdown files at vault root
_static/ folder contains KB site logos — may not belong at root level

Changelog: Updated at ~/Documents/baseworks-changelog/CHANGELOG.md Asia’s inbox: Detailed explanation of what changed and why added to her inbox

[ ] 03:45 ET | Daily Infrastructure Update Report

Added automatically by daily-infra-updates.sh on baseworks-agents VPS

Date: 2026-04-07

n8n — UPDATE NEEDS ATTENTION: health=unknown, version=unknown
PostgreSQL — UPDATE NEEDS ATTENTION: health=unknown

Backup health:

Site	Schedule	Last Success	Size	Status

| n8n | Daily | 2026-04-04 | 15MB | STALE (3 days) | | baseworks.com | Weekly | 2026-04-05 | DB=544MB, Files=143MB | OK | | staging | Weekly | 2026-04-05 | DB=254MB, Files=141MB | OK | | practice | Weekly | 2026-04-05 | DB=507MB, Files=183MB | OK | | crm | Weekly | 2026-04-05 | DB=38MB, Files=16MB | OK |

Needs your attention:

Warning: n8n update may have failed — health status: unknown
Warning: PostgreSQL update may have failed — health: unknown
Warning: n8n daily backup is 3 days old (last: 2026-04-04)
Warning: Claude CLI authentication failed — vault captures will not work. Check CLAUDE_CODE_OAUTH_TOKEN in ~/.bashrc (must be before the interactive guard)
Warning: n8n cannot SSH to baseworks-agents — vault capture pipeline is broken. Check SSH key at /opt/n8n-ssh/ on baseworks-n8n

Updates applied: None

Requested action: Review any items flagged above. Auto-updates have already been applied and verified.

[ ] 2026-04-06 12:30 ET | Pracstage staging checklist updated — Automator throttling + post-push cleanup

Added by Claude Code on Asia’s Mac Mini

Asia reviewed the inbox item you filed last night about the 502s on practice.baseworks.com. This session investigated the full picture and updated the pracstage deployment checklist accordingly. Summary of what was done and what was confirmed.

What we confirmed

Production (practice.baseworks.com) also has 1-minute Automator cron hooks:

Hook	Interval
`action_scheduler_run_queue`	Every 1 minute
`automator_pro_loops_run_queue`	Every 2 minutes

System cron fires every 5 minutes on production. The production PHP-FPM pool is dynamic, max_children=15, memory_limit=1024M — no throttling. Worth watching if Automator starts doing heavier work (e.g. questionnaire notification batches).

Your server-side fixes from last night persist across staging pushes. The PHP-FPM pool config lives at /etc/php/8.3/fpm/pool.d/ — xCloud doesn’t touch it when pushing prod → staging. The throttling you applied (ondemand, max_children=3, process.priority=15, memory_limit=256M, system cron at 30 min) is permanent and doesn’t need to be reapplied.

What was updated

sites/practice.baseworks.com/staging-setup-checklist.md in the changelog repo was updated (commit a9e611f):

Automator deactivated by default — the sanitization script now deactivates Uncanny Automator (both free and pro) as part of the standard post-push cleanup. A $keep_automator = false flag at the top of the script can be flipped to true when a session specifically needs to test Automator recipes.
Action Scheduler queue cleared — new step 4 in the sanitization script deletes all pending rows from areb_actionscheduler_actions. Production builds up a large queue of pending Automator jobs; without this, they’d all fire at once on the first staging cron run even with throttled PHP-FPM.
Verify SQL expanded — added a 5th check to the post-sanitization SQL that confirms the Action Scheduler queue is empty, with a fallback manual DELETE.
New “Server-side resource limits” section — documents your 2026-04-05 PHP-FPM changes with verification commands, and explicitly notes that these settings survive staging pushes.

No action needed from you — informational only.

[ ] 2026-04-06 11:00 ET | CRM site: SQL injection probe detected and blocked

Added by Claude Code on Asia’s Mac Mini

An automated scanner hit the crm.baseworks.com comment form with SQL injection probes (Oracle and PostgreSQL time-based blind injection variants). All 4 comments were held in the moderation queue and never executed — WordPress core sanitizes comment fields, so no data was accessed.

Actions taken:

4 probe comments deleted
Comments closed site-wide (crm.baseworks.com had public commenting open with no login required — this was the root cause)
Documented in the changelog under sites/crm.baseworks.com/

No follow-up required unless you’d like to review the CRM site’s other exposed surfaces (e.g. contact forms, registration).

2026-04-06

[ ] 03:45 ET | Daily Infrastructure Update Report

Added automatically by daily-infra-updates.sh on baseworks-agents VPS

Date: 2026-04-06

n8n — UPDATE NEEDS ATTENTION: health=unknown, version=unknown
PostgreSQL — UPDATE NEEDS ATTENTION: health=unknown

Backup health:

Site	Schedule	Last Success	Size	Status

| n8n | Daily | 2026-04-04 | 15MB | STALE (2 days) | | baseworks.com | Weekly | 2026-04-05 | DB=544MB, Files=143MB | OK | | staging | Weekly | 2026-04-05 | DB=254MB, Files=141MB | OK | | practice | Weekly | 2026-04-05 | DB=507MB, Files=183MB | OK | | crm | Weekly | 2026-04-05 | DB=38MB, Files=16MB | OK |

Needs your attention:

Warning: n8n update may have failed — health status: unknown
Warning: PostgreSQL update may have failed — health: unknown
Warning: n8n daily backup is 2 days old (last: 2026-04-04)
Warning: Claude CLI authentication failed — vault captures will not work. Check CLAUDE_CODE_OAUTH_TOKEN in ~/.bashrc (must be before the interactive guard)
Warning: n8n cannot SSH to baseworks-agents — vault capture pipeline is broken. Check SSH key at /opt/n8n-ssh/ on baseworks-n8n

Updates applied: None

Requested action: Review any items flagged above. Auto-updates have already been applied and verified.

[ ] 2026-04-05 21:30 ET | Karpathy Auto-Research Pattern — Explore for Baseworks

Added by Claude Code on Patrick’s Mac

Andrej Karpathy released an open-source project called auto-research — an automated experimentation loop where an AI agent runs experiments autonomously, keeps what improves a metric, discards what doesn’t, and repeats. The core pattern: one file to modify, one metric to optimize, a time-boxed loop with no human in the loop.

Why this matters for Baseworks:

Could be applied to optimize landing page conversion, email copy, course enrollment flows, or any measurable marketing/engagement metric
The pattern is domain-agnostic — works anywhere you have a clear metric and API access to change inputs
Multiple practitioners are reporting significant improvements running these loops overnight

What to explore:

Karpathy’s repo: github.com/karpathy/auto-research
Whether any Baseworks metrics (practice platform engagement, email open rates, enrollment conversions) are good candidates for auto-research loops
Whether this could be combined with the Claude Code skill/agent architecture already in the Baseworks KB

Also saved: A reference file about Karpathy’s LLM wiki/knowledge base pattern has been added to 03-resources/ — see karpathy-llm-wiki-pattern. This is relevant to how the Baseworks KB itself is structured and whether we should adopt elements of the raw/wiki separation and lint workflow.

Requested action: Review when you have time. Not urgent — this is a “future optimization” item, not a current-session task.

[ ] 2026-04-05 12:00 ET | Session 1 review complete — Asia’s feedback and action items

Added by Claude Code on Asia’s MacBook Air

Asia completed her review of the Session 1 summary and Session 1 prep document. Below is a summary of what she did and what needs your attention.

What Asia did:

Reviewed and edited the session-1-summary-en — factual corrections, major additions (marked in red), and an editorial summary comparing her version to your original (at the bottom of the file)
Read your “Notes After Session” in session-1-prep and added her response directly in the document
Read the Winter 2026 Learnings document and added comments to two sections (“The arc from instruction to practice” and “Balancing explanation and experience”)

Documents:

Actions needed from you:

1. Review Session 1 summary edits Asia made additions to your original draft. Please review:

The three red-marked paragraphs (Distributed Activation opening paragraph, Gurdjieff paragraph, Ignition note before “The Forms We Practiced”) — confirm these are correctly framed and you’re happy for them to stand
The editorial summary at the bottom of the file — a comparison of her version vs. your original, organized by factual corrections / major additions / other edits

2. Review Asia’s response in the Session 1 Prep document Asia added her response to your “Notes After Session” directly in session-1-prep.md. Topics covered: the co-teaching dynamic during introductions (time balance, interruptions, credibility framing), the waiver and questionnaire status (both confirmed before session), and her position on feedback in early sessions. This needs a discussion.

3. Session summary skill — informational, no action needed The /session-summary skill was updated based on Asia’s review: Primer lesson summaries are now a required input at Phase 3, and “teaching document not transcript summary” was added as the first principle at Phase 4. Worth knowing the skill changed.

4. Winter 2026 Learnings document — next steps needed Asia read the document and considers it genuinely useful and well-constructed. Two questions to discuss: (a) how to leverage it systematically within the session prep and summary workflow — the skill doesn’t currently read it explicitly, and there’s no structure for how “What to Improve” items carry forward; (b) whether it’s a starting point for content creation beyond the session summary skill — it contains the kind of distilled teaching observations that could be valuable in other contexts (platform content, onboarding materials, etc.). Asia’s embedded comments in the document also haven’t been addressed. Suggest a brief discussion to decide what this document should feed into.

[ ] 2026-04-05 11:00 ET | Voice guide draft — Established Teaching Vocabulary (needs your confirmation)

Added by Claude Code on Asia’s MacBook Air

Asia’s review of the Session 1 Spring 2026 summary identified a gap in the voice guide: it didn’t distinguish between established Primer teaching terms (vocabulary you use in lessons that participants have already encountered) and ad-hoc metaphors (which the voice guide prohibits). Without that distinction, Claude may flag your own teaching vocabulary as voice violations.

A new subsection — Established Teaching Vocabulary — has been drafted in the voice guide at 03-resources/voice-guides/VOICE-GUIDE-UNIFIED.md (version 2.5 draft). It includes two initial entries:

Term	Source
”empty shell” / “container”	Lesson 02.01 — how a form is a neutral container for movement patterns
”marionette arms”	Ignition instruction — arms lifted as if by a puppeteer, wrists limp

What’s needed from you: Confirm these two entries are correct as written (or adjust the descriptions). If you have other teaching terms from the Primer that should be in this list, add them here or note them and Asia/Claude will add them.

This section will also feed into the session summary guidelines and skill, which now cross-reference it.

2026-04-05

[ ] 03:45 ET | Daily Infrastructure Update Report

Added automatically by daily-infra-updates.sh on baseworks-agents VPS

Date: 2026-04-05

baseworks-agents system packages: 1 packages updated
n8n — UPDATE NEEDS ATTENTION: health=unknown, version=unknown
PostgreSQL — UPDATE NEEDS ATTENTION: health=unknown
FileBrowser — UPDATE NEEDS ATTENTION: health=starting

Backup health:

Site	Schedule	Last Success	Size	Status

| n8n | Daily | 2026-04-04 | 15MB | OK | | baseworks.com | Weekly | 2026-03-29 | DB=531MB, Files=143MB | OK | | staging | Weekly | 2026-03-29 | DB=254MB, Files=141MB | OK | | practice | Weekly | 2026-03-29 | DB=503MB, Files=183MB | OK | | crm | Weekly | 2026-03-29 | DB=31MB, Files=16MB | OK |

Needs your attention:

Warning: n8n update may have failed — health status: unknown
Warning: PostgreSQL update may have failed — health: unknown
Warning: FileBrowser update may have failed — health: starting
Warning: Claude CLI authentication failed — vault captures will not work. Check CLAUDE_CODE_OAUTH_TOKEN in ~/.bashrc (must be before the interactive guard)
Warning: n8n cannot SSH to baseworks-agents — vault capture pipeline is broken. Check SSH key at /opt/n8n-ssh/ on baseworks-n8n

Updates applied: 1

Requested action: Review any items flagged above. Auto-updates have already been applied and verified.

[ ] 2026-04-05 | New feature: lesson title auto-tagged on discussion creation

Added by Claude Code on Asia’s Mac Mini

Asia implemented a new feature on the practice site: when a participant creates a discussion from the Discussion tab on a Primer lesson, the lesson title is now automatically added as a bbPress tag to the new topic.

What’s live:

New wrapper shortcode [bw_topic_form forum_id=XXXXX title_tag=1] (Snippet 47, codesnippets.pro)
All 79 Primer lessons updated via WP-CLI to use the new shortcode
Compatible with manually added tags — appends, does not overwrite
Tested on pracstage before deploying to production

Why it matters: Discussions created from any lesson will be filterable/searchable by lesson title tag in the bbPress forum, making it easier to find discussions tied to specific content.

Changelog: sites/practice.baseworks.com/code-snippets/47-bw-lesson-topic-form.php

2026-04-04

[ ] 03:45 ET | Daily Infrastructure Update Report

Added automatically by daily-infra-updates.sh on baseworks-agents VPS

Date: 2026-04-04

Claude Code updated: 2.1.91 (Claude Code) → 2.1.92 (Claude Code)
baseworks-agents system packages: 5 packages updated
baseworks-n8n system packages: 6 packages updated

Backup health:

Site	Schedule	Last Success	Size	Status

Needs your attention:

Warning: Claude CLI authentication failed — vault captures will not work. Check CLAUDE_CODE_OAUTH_TOKEN in ~/.bashrc (must be before the interactive guard)

Updates applied: 3

Requested action: Review any items flagged above. Auto-updates have already been applied and verified.

2026-04-03

[ ] 03:45 ET | Daily Infrastructure Update Report

Added automatically by daily-infra-updates.sh on baseworks-agents VPS

Date: 2026-04-03

Claude Code updated: 2.1.90 (Claude Code) → 2.1.91 (Claude Code)
baseworks-agents system packages: 6 packages updated
baseworks-n8n system packages: 7 packages updated

Backup health:

Site	Schedule	Last Success	Size	Status

| n8n | Daily | 2026-04-03 | 15MB | OK | | baseworks.com | Weekly | 2026-03-29 | DB=531MB, Files=143MB | OK | | staging | Weekly | 2026-03-29 | DB=254MB, Files=141MB | OK | | practice | Weekly | 2026-03-29 | DB=503MB, Files=183MB | OK | | crm | Weekly | 2026-03-29 | DB=31MB, Files=16MB | OK |

Needs your attention:

Warning: Claude CLI authentication failed — vault captures will not work. Check CLAUDE_CODE_OAUTH_TOKEN in ~/.bashrc (must be before the interactive guard)

Updates applied: 3

Requested action: Review any items flagged above. Auto-updates have already been applied and verified.

Added by Claude Code on Asia’s Mac Mini

The [primer-assignments group=5] shortcode is now live for the Spring 2026 Montreal study group cohort. Configuration uses the same 49-lesson structure as group 3, with 6 assignment deadlines (S1–S6) — the 7th session (May 16) has no assignments.

You can see the shortcode on the front end here: https://practice.baseworks.com/hang/

[ ] 2026-04-03 22:30 ET | Background tab — redirect guard + form ID fixed (v1.3.0)

Added by Claude Code on Asia’s Mac Mini

Asia noticed that navigating directly to /members/{other-user}/background/ was showing her own questionnaire form under another member’s profile. Two fixes applied and tested:

Redirect guard — bw_profile_background_screen() now redirects anyone (including admins) to the displayed member’s profile root if it’s not their own profile. The admin exception was removed from the screen function (admins still see the tab in nav on their own profile).
Form ID corrected — was 76 (pracstage), should be 74 (practice production). This was causing “Please select a valid form” on the Background tab.

Plugin bumped to v1.3.0. Deployed to practice.baseworks.com. Changelog updated.

[ ] 2026-04-02 23:30 ET | Auto-syncing iCal files — explore dynamic .ics generation

Added by Claude Code on Patrick’s Mac

The static .ics files hosted at practice.baseworks.com/calendars/ fix the Apple Calendar timezone issue but don’t auto-update when Google Calendar event times change. Explore a solution — options include:

A proxy script on the agents VPS that fetches the Google iCal feed, rewrites UTC times to explicit TZID=America/New_York, and serves the result (cron refresh every hour)
A lightweight endpoint on the practice site that does the same transformation on-the-fly
An n8n workflow triggered by Google Calendar changes that regenerates and re-uploads the .ics

Current static files: study-group-spring-2026.ics, practice-sessions-spring-2026.ics Root cause: Google’s public iCal feed uses UTC Z timestamps that Apple Calendar misinterprets as local time

[ ] 2026-04-02 11:45 ET | upcoming_event_filter snippet — glitch explained, now resolved

Added by Claude Code on Asia’s Mac Mini

The snippet 26-baseworks-event-queries.php you disabled earlier is now back in a clean state. Here’s what happened:

During the session I made a failed attempt to write the snippet via an SSH heredoc. The shell expanded $query to an empty string, leaving bare ->set() calls — invalid PHP, which is what was crashing WP-CLI. I caught the syntax error immediately and re-uploaded a corrected version via scp, but by the time you found the broken version, the correct file was already on disk. OPcache was holding the stale version for a while, which caused some confusion on the front end.

I’ve deleted the .disabled artifact you created. The snippet is currently published and running correctly.

What the snippet now does (changed from original):

Filter changed from event_start_date >= today → (event_end_date >= today) OR (event_start_date >= today) so multi-day events stay visible while running
Ordering now uses a named meta_query clause to reliably sort by event_start_date ASC
Also corrected the event_start_date on Montreal Practice Sessions (was manipulated to June 27 to work around the old filter; now correctly set to March 15)

Full details in the baseworks-changelog: 20260402-upcoming-event-filter-fix.md

2026-04-02

[ ] 03:45 ET | Daily Infrastructure Update Report

Added automatically by daily-infra-updates.sh on baseworks-agents VPS

Date: 2026-04-02

Claude Code updated: 2.1.89 (Claude Code) → 2.1.90 (Claude Code)
baseworks-agents system packages: 11 packages updated
baseworks-n8n system packages: 11 packages updated

Backup health:

Site	Schedule	Last Success	Size	Status

| n8n | Daily | 2026-04-02 | 15MB | OK | | baseworks.com | Weekly | 2026-03-29 | DB=531MB, Files=143MB | OK | | staging | Weekly | 2026-03-29 | DB=254MB, Files=141MB | OK | | practice | Weekly | 2026-03-29 | DB=503MB, Files=183MB | OK | | crm | Weekly | 2026-03-29 | DB=31MB, Files=16MB | OK |

Needs your attention:

Warning: Claude CLI authentication failed — vault captures will not work. Check CLAUDE_CODE_OAUTH_TOKEN in ~/.bashrc (must be before the interactive guard)

Updates applied: 3

Requested action: Review any items flagged above. Auto-updates have already been applied and verified.

[ ] 2026-04-02 00:30 ET | Resume: Calendar setup + Preparation Guide page + Welcome email

Added by Claude Code on Patrick’s Mac

Context: Long session tonight covering Google Calendar integration and practice session onboarding flow. Continuation file at 00-inbox/session-resume-2026-04-02.md — use this as the prompt when starting a new terminal session.

What’s done:

Google Calendar connected via MCP (pat@baseworks.com)
3 calendars created and populated (60 total events): Baseworks MTL Sessions (private), Study Group (public), Practice Sessions (public)
All events have full address, studio numbers, Google Maps directions link
Public calendar events prefixed with “Baseworks” for participant clarity
Asia’s inbox updated about calendar setup
Preparation guide page created on practice.baseworks.com (ID 22134, DRAFT, slug: preparation-guide)
WP Fusion gating set: track-introductory, track-standard, track-alumni
Welcome email (welcome-new.md) replaced with abridged version pointing to the guide

What’s pending (pick up tomorrow):

Preparation guide page design — 720px max-width is too narrow, you have a different design idea
Finalize and publish the preparation guide page
Make both participant calendars public (Google Calendar settings)
Add calendar descriptions
Link preparation guide from practice site dashboard
Update welcome email’s preparation guide link to live URL once published
Generate HTML version of welcome email via /create-email

[ ] 2026-04-01 22:55 ET | Questionnaire system deployed — Phase 2 plan

Added by Claude Code on Patrick’s Mac

Event Participation Questionnaire is now live on practice.baseworks.com:

Background profile tab with the form at /members/me/background/
Persistent prompt banner for enrolled participants (tag-based)
Dashboard teaser for practice-session-only users ([bw_dashboard_teaser] shortcode)
Obsidian export running 6x daily from agents VPS cron

Remaining items for you:

Update Elementor dashboard link — change the “Event Participation Questionnaire” link in the existing Elementor notification block to /members/me/background/
Place [bw_dashboard_teaser] shortcode on the dashboard page via Elementor Shortcode widget (if not already done)
Re-enable admin exclusion on the prompt banner when done testing (tell Claude to flip it back)

Phase 2 plan:

Groups teaser page — Create an Elementor page with a [bw_groups_teaser] shortcode showing muted group cards (Primer Community, Study Group cohorts, Practice Community) with CTA overlay. Tag-based menu item: practice-session-only users see this page; Primer/Study Group users see the real BuddyBoss groups directory. No BuddyBoss hooks needed — just Elementor + WP Fusion menu visibility.
Soft-gate form completion — require questionnaire completion before certain LearnDash/BuddyBoss milestones (e.g., after Primer Lesson 3, or before group discussions)
Real-time Obsidian sync — webhook on form submission triggers immediate export + Git commit (replaces 4-hourly cron)
Custom multi-step form — replace Formidable with custom PHP form, light modern design, step-by-step flow, editable profile card on dashboard
Broader data accumulation — capture forum posts, DMs, email inquiries as supplementary profile data in Obsidian vault

2026-04-01

[ ] 03:45 ET | Daily Infrastructure Update Report

Added automatically by daily-infra-updates.sh on baseworks-agents VPS

Date: 2026-04-01

Claude Code updated: 2.1.88 (Claude Code) → 2.1.89 (Claude Code)
baseworks-agents system packages: 3 packages updated
baseworks-n8n system packages: 3 packages updated

Backup health:

Site	Schedule	Last Success	Size	Status

| n8n | Daily | 2026-04-01 | 15MB | OK | | baseworks.com | Weekly | 2026-03-29 | DB=531MB, Files=143MB | OK | | staging | Weekly | 2026-03-29 | DB=254MB, Files=141MB | OK | | practice | Weekly | 2026-03-29 | DB=503MB, Files=183MB | OK | | crm | Weekly | 2026-03-29 | DB=31MB, Files=16MB | OK |

Needs your attention:

Warning: Claude CLI authentication failed — vault captures will not work. Check CLAUDE_CODE_OAUTH_TOKEN in ~/.bashrc (must be before the interactive guard)

Updates applied: 3

Requested action: Review any items flagged above. Auto-updates have already been applied and verified.

[ ] 2026-03-31 | “Mystery of Proprioceptive Awareness” — Japanese translation needs updating

Added by Claude Code on Asia’s Mac Mini

The article has been substantially rewritten (March 2026). The Japanese translation needs to be updated against the archived original.

New version: mystery-of-proprioceptive-awareness
Archive (translation source): mystery-of-proprioceptive-awareness-v1 (02-areas/website/blog-articles/_archive/)
Live URL: https://baseworks.com/article/the-mystery-of-proprioceptive-awareness/

Main changes that affect translation: receptor speculation section replaced with fusimotor hypothesis, “Injury Prevention” section removed, three new sections added (Three Dichotomies, two-component spindle model, What’s the Usefulness), survey data added, DCML section rewritten.

[ ] 2026-03-31 23:30 ET | Open a session in baseworks-changelog to investigate forum auto-tagging from Primer lessons

Added by Claude Code on Patrick’s Mac

Forum posts created via the “post to forum” button on Primer lesson pages don’t auto-tag with the lesson/segment reference. Participants have to manually specify which lesson they’re referring to. Open a session in the baseworks-changelog repo to investigate whether a snippet or mu-plugin can pre-fill this metadata (segment + lesson number + title) so forum posts are automatically tagged and searchable.

[ ] 2026-03-30 20:40 ET | New inquiry: James Murray — Spring Cohort (Session 2 logistics)

Added by Claude Code on Patrick’s Mac

James Murray (Montreal, self-employed) submitted a contact form asking about the Spring Cohort. He works online all day on April 11 and wants to know if he can work onsite at Proto Studio so he can attend Session 2 (1:10-2:50 PM). He’s read the landing page, knows the exact time, and really doesn’t want to miss any sessions.

Action needed: Review draft response at 2026-03-30-james-murray-study-group — the key question is whether there’s a workspace or nearby spot at Proto Studio where he could set up a laptop before/after the session. Once you confirm the venue logistics, the response can be finalized and sent.

[ ] 2026-03-27 22:30 ET | Media CDN pipeline fully operational — session summary + next steps

Added by Claude Code on Patrick’s Mac

Full B2 + Cloudflare CDN + NAS media pipeline is live and tested. All vault images (102 files, 136 MB) uploaded to B2 and serving from media.baseworks.com. Markdown references updated to CDN URLs for proprioceptive awareness article (both versions) and Meta campaign note.

What was done this session:

Installed B2 CLI on Mac, authorized with baseworks-media bucket key
Created B2 bucket baseworks-media (public, us-east-005)
Set up Cloudflare CNAME (media → f005.backblazeb2.com) with proxy ON
Created Transform Rule (URL path rewrite for B2 native endpoint)
Created Header Modification Rule (fixes APO interference with browser requests)
Created NAS folder structure at /volume1/baseworks/media/ (with SMB access + quota removed)
Moved old MacBook backup from baseworks share to Pat Stuff
Re-enabled Cloudflare proxy for baseworks.com, crm.baseworks.com, practice.baseworks.com (safe with Let’s Encrypt + /etc/hosts for WPRUS)
Rewrote /compress-photos skill as full media processing pipeline (resize → WebP + JPEG → B2 upload → CDN URLs)
Uploaded all 102 vault images to B2 in organized folder structure
Updated 3 markdown files to use CDN URLs instead of local asset paths
Created media organization memo for broader photo taxonomy planning

Cloudflare notes:

APO (WordPress optimization) was intercepting browser requests to media.baseworks.com — fixed with Accept header override rule
CNAME must point to f005.backblazeb2.com (B2 native endpoint), NOT the S3 endpoint
B2 pricing update: $0 API transaction fees starting May 1, 2026

Tomorrow:

Batch test: full pipeline from NAS → rename → compress → B2 → manifest
Discuss forms reference library and broader media taxonomy
Consider /organize-media skill for the incoming → sort → rename workflow
Remove binary image files from vault + update .gitignore
Ask Asia to test WPRUS cross-site login (proxy re-enabled)

Reference files:

media-storage-plan — technical setup details
media-organization-memo — taxonomy/organization planning
/compress-photos skill — updated pipeline

[ ] 2026-03-27 | Website functionalities docs restructured — new home for infrastructure context + action needed on changelog path

Added by Claude Code on Asia’s Mac Mini

02-areas/website/functionalities/ is now the organised home for all website infrastructure documentation. If you need to give your Claude context about the website ecosystem, custom plugins, or site architecture, point it at that directory — the index will tell it where to look.

What’s in there now:

Website Ecosystem Overview — the three-site integration (WP Fusion, FluentCRM, Uncanny Automator)
Cross-Site User Sync (WPRUS) — login sync, admin account isolation, the View As fix
Practice Site Platform Infrastructure — BuddyBoss, LearnDash, activity tracking
Custom Code Overview — full inventory of every mu-plugin, code snippet, and theme override on both sites
Baseworks Changelog Repo — reference note for the changelog git repo

Action needed: The changelog reference note has your repo path as unconfirmed. Please check where your local clone sits and update baseworks-changelog-ref with the correct path under the Patrick’s Mac row in the Location table.

[ ] 2026-03-27 | WPRUS admin session sync — how it works, what was fixed, what must not change

Added by Claude Code on Asia’s Mac Mini

Background: After the 2026-03-23 WPRUS login sync fix, Asia was intermittently losing admin privileges on baseworks.com after logging into the practice site. Investigation revealed a deeper account structure issue.

What happened: WPRUS matches users by username. Asia had pandasia as admin on baseworks.com and asia as admin on practice. When asia logged into practice, WPRUS synced the session to a separate asia subscriber account on baseworks.com (auto-created by WPRUS create sync) — logging her in as a subscriber, not admin.

The fix: Deleted the subscriber mirror accounts on both sites. Asia changed her practice admin email to asia@baseworks.com (matching her baseworks.com admin pandasia). This creates an email conflict that silently blocks WPRUS from ever recreating the mirror.

Why this also applies to you: Your setup has always worked the same way — basework on baseworks.com and patrick on practice, both with pat@baseworks.com. WPRUS tries to sync your sessions, hits the email conflict, fails silently, and your admin sessions stay independent. You never noticed because you don’t use BuddyBoss “View As” (which was the trigger that exposed the issue for Asia).

What must not change: The username mismatch between your admin accounts on the two sites must be preserved. If the usernames ever align, WPRUS will sync admin sessions cross-site and one of them will lose privileges. This is now documented in Cross-Site User Sync (WPRUS).

Also fixed: BuddyBoss “View As” on practice.baseworks.com was propagating the impersonated session to baseworks.com (giving access to that member’s WooCommerce billing data). Fixed with a mu-plugin. No action needed from you.

[ ] 2026-03-27 | Neuro 2026 abstract submitted

Added by Claude Code on Asia’s Mac Mini

Asia submitted a poster abstract to the 27th Annual Brenda Milner Neuropsychology Day (McGill). Full abstract and notes: Neuro 2026 Abstract.

[ ] 2026-03-27 | SEOPress “closest match” redirect — needs review

Added by Claude Code on Asia’s Mac Mini

During a newsletter test send today, Asia noticed a broken image link was silently redirecting to a WooCommerce product page instead of returning a 404. The broken URL (/event/montreal-study-group-2026/) ended up at /product/montreal-study-group-2026-spring-cohort-m/ — a single 301, no error shown.

The broken link itself was just a typo (missing “spring” in the slug, likely a leftover from a previous newsletter template). That’s fixed. But the behaviour it exposed is the real issue: SEOPress Pro’s “closest match” auto-redirect is on, and it’s silently routing broken URLs to whatever slug looks most similar — including product/purchase pages. This could look spammy to newsletter recipients and makes broken links invisible during test sends.

Action needed: Review the SEOPress redirect settings on baseworks.com — specifically whether the fuzzy “closest match” 404 redirect feature is intentional or can be restricted to exact old-slug matches only.

Full write-up in the baseworks changelog: changelog-entries/20260327-seopress-unpredictable-redirect-behaviour.md

[ ] 2026-03-26 | New skill: /update-science-content + BRNet prep work

Added by Claude Code on Asia’s Mac Mini

Session summary for tonight’s work — a few things to be aware of:

New skill: /update-science-content Asia and Claude designed and created a new Claude Code skill for updating science-based web content (pages and blog posts). It works similarly to the existing writing skills — loads voice guides, key-definitions.md, and science.md as context — but adds a structured strategy conversation before any drafting, plus a literature scan step and a specialist accuracy check. Guidelines doc: update-science-content-guidelines.

First test case: the “3 types of body awareness” blog post The mystery-of-proprioceptive-awareness blog post has been imported to 02-areas/website/blog-articles/_rework/ and is queued for a full update using the new skill. The main issues: fitness/injury-prevention framing from 2022, and the neurobiological substrate section needs to replace the receptor speculation with the fusimotor reafference hypothesis (Luu et al., 2011). This update is prep for the BRNet 2026 conference campaign (Padua, June 8–9).

Other files created this session:

02-areas/website/events/2025-05-neuropsychology-day.md — past presentation archived
02-areas/website/events/2025-10-perceptual-skills-movement-miscommunication.md — past presentation archived
BRNet 2026 abstract status updated to: accepted — poster presentation confirmed

No action needed from you on any of this — just FYI.

[ ] 2026-03-26 | Synology SSH — both machines failing, troubleshooting needed

Added by Claude Code on Asia’s MacBook Air — updated by Claude Code on Asia’s Mac Mini

Both the Mac Mini and MacBook Air are failing. The Mac Mini key was supposedly authorized (you marked the previous item [X]), but it’s still being rejected. Error on both machines:

Asia Shcherbakova@100.106.46.99: Permission denied (publickey,password)

Mac Mini public key (from the [X] item you already processed):

ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIOH99qK6CIIemBEhK4PNPPXAOBNIW4sQKrLA9zZwfDwZ as@baseworks.com

MacBook Air public key (new, needs to be added):

ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIMxHqc5V0vhR1ieIm8Do1NS26oyb+o7TGEnfRLK6MGdY server-access

Things to check in DSM:

Is SSH service enabled? (Control Panel → Terminal & SNMP → Enable SSH service)
What is the exact login username for Asia’s account? (User & Group → check the actual username, not just the display name — it may not be “Asia Shcherbakova” for SSH purposes)
Were both keys added to the correct user? The Mac Mini key should already be there per the previous item, but it’s still failing — worth verifying it was saved correctly.

[ ] 2026-03-26 | Winter Study Group Photos — Renamed and pushed to vault, ready for your review

Added by Claude Code on Asia’s MacBook Air

Asia has renamed the WebP files and pushed everything to the vault campaign assets folder. All 20 WebP files and JPEG originals are now in:

02-areas/communications/campaigns/2026-03-winter-study-group-campaign/2026-03-winter-study-group-recap-assets/

Do a git pull to get them. Review the filenames and upload to the WordPress media library when ready.

[ ] 2026-03-25 | BRNet 2026 — Asia’s abstract accepted, please block calendar

Added by Claude Code on Asia’s Mac Mini

Asia’s abstract for BRNet 2026 has been accepted as a poster presentation. The conference is officially confirmed.

Please block your calendar:

Dates: June 8–9, 2026
Location: Padua, Italy
Conference: 8th Annual BRNet Meeting

Poster format is standard vertical A0 (84.1 × 118.9 cm). Full programme with poster session details coming soon from the organizers.

See: BRNet 2026 Abstract

[X] 2026-03-25 | Synology SSH — authorize Asia’s public key

Added by Claude Code on Asia’s Mac Mini

Tailscale is working on Asia’s Mac Mini (Synology visible at 100.106.46.99). The SSH alias ssh synology is configured. The SSH key is in place. The only missing step is authorizing Asia’s public key on the Synology.

Action: In Synology DSM → Control Panel → User & Group → Asia Shcherbakova → Edit → SSH Public Keys, add:

ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIOH99qK6CIIemBEhK4PNPPXAOBNIW4sQKrLA9zZwfDwZ as@baseworks.com

Once added, ssh synology will work from Asia’s Mac Mini. She’ll need to repeat the same key setup on her MacBook Air when ready.

Update 2026-03-25 — MacBook Air also ready: Added by Claude Code on Asia’s MacBook Air

Tailscale is now set up on Asia’s MacBook Air as well. The ssh synology alias is configured using her existing id_ed25519_server key. Please also authorize this public key on the Synology:

ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIMxHqc5V0vhR1ieIm8Do1NS26oyb+o7TGEnfRLK6MGdY server-access

Resolved 2026-03-25: Completed by Claude Code on Patrick’s Mac

Both keys added to ~/.ssh/authorized_keys on the Synology via SSH. Also fixed home directory permissions (777 → 755) which were causing OpenSSH StrictModes to reject key auth for all users. ssh synology now works passwordless from all authorized machines.

[ ] 2026-03-25 | Blog Feedback Workflow — Optimization Proposal Needed

Added by Claude Code on Asia’s Mac Mini

Asia documented the friction from the Winter 2026 blog post feedback session and is asking you and your Claude to propose a better workflow.

Full discussion document: 02-areas/website/blog-articles/feedback-workflow-optimization/blog-feedback-optimization-discussion.md

The short version: Asia’s Claude drafted proposed revisions in your voice based on her directional notes, but several came back needing voice correction on your end. The question is whether there’s a better routing — so that Asia’s raw observational feedback gets translated into voice-compliant proposals before they reach you, without adding work on her side.

Asia’s preferred outcome: a workflow where her role stays what it is (fact-checker, not editor), and you’re not doing voice cleanup on proposals that should have been right from the start.

[ ] 2026-03-25 | Participation terms — language clause (not interpreter clause)

Added by Claude Code on Asia’s Mac Mini

Asia reviewed the participation terms interpreter clause item and has a different take:

Asia’s position: “Where feasible, interpreters may be available for certain programs” is not appropriate for Terms & Conditions as written. Terms explain what we offer and protect us — we don’t list things we might occasionally do but don’t normally offer. If anything were added, it would need to be framed protectively: “unless otherwise specified, programs are conducted in English; interpretation is not provided by default.”

But Asia’s actual preference: a clear language clause stating that unless otherwise specified, programs are conducted in English — rather than an interpreter availability clause. This would be consistent with what the Study Group landing page already says about English as the working language for international accessibility.

Requested action: Review Asia’s framing and decide whether to add a language clause to the Terms. If yes, coordinate with Asia on the exact wording. No urgency.

[ ] 2026-03-25 | Blog post idea — Language as a Teaching Medium (Asia’s proposal)

Added by Claude Code on Asia’s Mac Mini

Asia has developed a blog post idea based on Baseworks’s history with language across Japan, South America, and Quebec. Asia proposes to author it herself, as she has the most direct connection to language as a practitioner and teacher.

Draft idea note: 02-areas/website/blog-articles/_blog-idea-language-teaching-at-baseworks.md

The post would cover: the organic bilingual origin in Japan, language as an adaptive medium (not a policy), the South America experience, the Quebec political context, why English is the international language of the operation (not anti-French), and what Baseworks is actively doing to improve accessibility (French subtitles, dubbing exploration).

Questions for you before Asia develops this further:

Is this a blog post or does it belong somewhere else (About page, separate page)?
Are you comfortable with the Quebec section as proposed?
Any points to add, cut, or reframe?
Main site blog or different audience?

[ ] 2026-03-24 23:30 ET | Vault SQLite Index + Git Sync Plan — Ready for Review

Added by Claude Code on Patrick’s Mac

Implementation plan for two vault infrastructure improvements:

SQLite relationship index — queryable database of wikilinks, tags, and frontmatter metadata (complements the existing qmd full-text/vector search)
Reliable git sync — replace the Obsidian Git plugin (which doesn’t auto-push) with a launchd/cron job that pulls, commits, and pushes every 5 minutes

The plan also covers fixing the stale qmd index, NAS as a pull-only backup mirror, cross-folder project referencing, and rollout to VPS + Asia’s machines.

Full plan: Vault SQLite Index + Reliable Git Sync — Implementation Plan

Open questions in the plan (review before starting implementation):

Sync interval (5 min vs 2-3 min?)
Commit message format (keep vault backup: or differentiate?)
Coordinate with Asia before disabling Obsidian Git auto-sync?
Set up NAS clone now or defer?
qmd embed frequency (daily sufficient?)

Next step: Point Claude at the plan file tomorrow morning to start Phase 1 implementation.

2026-03-24

[ ] 03:45 ET | Daily Infrastructure Update Report

Added automatically by daily-infra-updates.sh on baseworks-agents VPS

Date: 2026-03-24

baseworks-agents system packages: 3 packages updated
baseworks-n8n system packages: 3 packages updated

Backup health:

Site	Schedule	Last Success	Size	Status

| n8n | Daily | 2026-03-24 | 14MB | OK | | baseworks.com | Weekly | 2026-03-22 | DB=528MB, Files=141MB | OK | | staging | Weekly | 2026-03-22 | DB=254MB, Files=141MB | OK | | practice | Weekly | 2026-03-22 | DB=501MB, Files=182MB | OK | | crm | Weekly | 2026-03-22 | DB=18MB, Files=16MB | OK |

Needs your attention:

Warning: Claude CLI authentication failed — vault captures will not work. Check CLAUDE_CODE_OAUTH_TOKEN in ~/.bashrc (must be before the interactive guard)

Updates applied: 2

Requested action: Review any items flagged above. Auto-updates have already been applied and verified.

[ ] 2026-03-23 17:30 ET | Server: WPRUS fix — revert /etc/hosts + choose SSL path forward (URGENT first step)

Added by Claude Code on Asia’s Mac Mini — replaces earlier inbox item from 10:30 ET

Status: The /etc/hosts entries you added are currently making things worse. Needs a two-step fix.

Step 1 — URGENT: revert the /etc/hosts change

The entries are breaking WPRUS sync completely. Please remove them:

sed -i '/baseworks\.com/d' /etc/hosts

Verify they’re gone:

cat /etc/hosts | grep baseworks
# should return nothing

Why the /etc/hosts fix didn’t work:

The server uses a Cloudflare Origin Certificate — a cert that is only trusted by Cloudflare, not by standard HTTPS clients. When the /etc/hosts entries bypass Cloudflare, PHP’s cURL hits the Origin Cert, fails SSL verification, and throws an error. Token renewal breaks completely.

Step 2 — fix the SSL cert, then re-apply /etc/hosts

Two options. Full details in the changelog: CHANGELOG.md entry dated 2026-03-23.

Option A (recommended) — install Let’s Encrypt cert on the origin server Replace the Cloudflare Origin Cert with a publicly-trusted Let’s Encrypt cert. Certbot handles renewal automatically. After this, re-add the three /etc/hosts lines and the WPRUS fix will work.

Option B (faster) — add Cloudflare’s Origin CA to the server trust store

curl -o /usr/local/share/ca-certificates/cloudflare-origin-ca.crt \
  https://developers.cloudflare.com/ssl/static/origin_ca_rsa_root.pem
update-ca-certificates

Then re-add the /etc/hosts lines. Less clean long-term but faster to implement.

Full investigation details, test results, and both options documented in full in the changelog.

Why: baseworks.com, practice.baseworks.com, and crm.baseworks.com all live on the same server. WP Remote Users Sync makes HTTPS calls between the sites to sync logins, but because the domains point to Cloudflare, those calls route out through Cloudflare and back — an unnecessary round-trip that causes intermittent token renewal failures. The result is that cross-site login sync works sometimes but not others. Adding these hosts entries makes the server resolve those domains directly to its own IP, bypassing Cloudflare for internal server-to-server calls only. No impact on regular visitor traffic.

Why Asia couldn’t do it: Our SSH user doesn’t have write permission to /etc/hosts. Asia tried via xCloud and also via Claude on the agents VPS — both hit the same permission wall. Needs root on the web server.

Notes:

Safe and reversible — remove the three lines to undo
If the server ever moves to a new IP, update these lines to the new IP
After the change, Asia will test login sync with test user swantest2 (swanonthecliff@gmail.com)

2026-03-23

[ ] 03:45 ET | Daily Infrastructure Update Report

Added automatically by daily-infra-updates.sh on baseworks-agents VPS

Date: 2026-03-23

baseworks-n8n system packages: 8 packages updated

Backup health:

Site	Schedule	Last Success	Size	Status

| n8n | Daily | 2026-03-23 | 14MB | OK | | baseworks.com | Weekly | 2026-03-22 | DB=528MB, Files=141MB | OK | | staging | Weekly | 2026-03-22 | DB=254MB, Files=141MB | OK | | practice | Weekly | 2026-03-22 | DB=501MB, Files=182MB | OK | | crm | Weekly | 2026-03-22 | DB=18MB, Files=16MB | OK |

Needs your attention:

Warning: Claude CLI authentication failed — vault captures will not work. Check CLAUDE_CODE_OAUTH_TOKEN in ~/.bashrc (must be before the interactive guard)

Updates applied: 1

Requested action: Review any items flagged above. Auto-updates have already been applied and verified.

[ ] 2026-03-22 | Voice guide: confirm updates — Cowork session incomplete

Added by Claude via Dispatch (Cowork)

Requested action: Confirm and apply voice guide updates from the 2026-03-22 Cowork session in a proper Claude Code session Summary:

Voice guide changes were drafted during this Cowork session but rolled back — remote iPhone access made it difficult to validate properly, and Patrick flagged a discrepancy between Cowork edits and the established QMD/Obsidian workflow
Reference for all patterns: the Sylvia Edgerton sent response — 2026-03-22-sylvia-edgerton-study-group
Patterns to consider adding to VOICE-GUIDE-PATRICK.md: never use “Thank you for reaching out” (use “Thank you for your message” or “Thank you for your inquiry”); avoid first-person recommendations like “I’d recommend signing up” (use “We think you’d find the program relevant and interesting” or omit); “directly relevant” → “relevant”; no AI-typical paragraph-closing summary sentences; “We” for organizational positions, “I” for personal opinions

Open question: Review the sent response as the reference, then confirm which patterns should be formally added to the voice guide.

2026-03-22

[ ] 03:45 ET | Daily Infrastructure Update Report

Added automatically by daily-infra-updates.sh on baseworks-agents VPS

Date: 2026-03-22

baseworks-n8n system packages: 8 packages updated

Backup health:

Site	Schedule	Last Success	Size	Status

| n8n | Daily | 2026-03-22 | 14MB | OK | | baseworks.com | Weekly | 2026-03-15 | DB=519MB, Files=141MB | OK | | staging | Weekly | 2026-03-15 | DB=254MB, Files=141MB | OK | | practice | Weekly | 2026-03-18 | DB=496MB, Files=183MB | OK | | crm | Weekly | 2026-03-15 | DB=18MB, Files=16MB | OK |

Needs your attention:

Warning: Claude CLI authentication failed — vault captures will not work. Check CLAUDE_CODE_OAUTH_TOKEN in ~/.bashrc (must be before the interactive guard)

Updates applied: 1

Requested action: Review any items flagged above. Auto-updates have already been applied and verified.

2026-03-21

[ ] 03:45 ET | Daily Infrastructure Update Report

Added automatically by daily-infra-updates.sh on baseworks-agents VPS

Date: 2026-03-21

Claude Code updated: 2.1.80 (Claude Code) → 2.1.81 (Claude Code)
baseworks-agents system packages: 12 packages updated
baseworks-n8n system packages: 12 packages updated

Backup health:

Site	Schedule	Last Success	Size	Status

| n8n | Daily | 2026-03-21 | 14MB | OK | | baseworks.com | Weekly | 2026-03-15 | DB=519MB, Files=141MB | OK | | staging | Weekly | 2026-03-15 | DB=254MB, Files=141MB | OK | | practice | Weekly | 2026-03-18 | DB=496MB, Files=183MB | OK | | crm | Weekly | 2026-03-15 | DB=18MB, Files=16MB | OK |

Needs your attention:

Warning: Claude CLI authentication failed — vault captures will not work. Check CLAUDE_CODE_OAUTH_TOKEN in ~/.bashrc (must be before the interactive guard)

Updates applied: 3

Requested action: Review any items flagged above. Auto-updates have already been applied and verified.

[ ] 2026-03-20 14:30 ET | Session booking plugin — admin email notifications implemented

Added by Claude Code on Asia’s Mac Mini

Asia requested and tested a new feature in the session booking plugin (baseworks-session-booking.php): admin email notifications for bookings and cancellations.

What was added:

New checkbox in WP Admin → Session Bookings → Email Notifications: “Send booking confirmation and cancellation emails to admin”
When enabled, an email goes to the WordPress admin email address each time someone books or cancels
Admin emails identify the participant by full name and email address (subject: [Booking] Jane Smith — Practice Sessions — Montreal, Spring 2026)
Body includes which sessions were booked/cancelled, plus the participant’s full upcoming schedule and credit balance
Independent toggle from the participant email toggle; off by default

Status: Deployed to baseworks.com, tested live by Asia. Working.

Documentation: Practice Sessions Booking Widget updated (v2.1.0). Changelog entry: changelog-entries/20260320-practice-sessions-admin-email-notifications.md.

No action needed — FYI only. To enable admin notifications: WP Admin → Session Bookings → Email Notifications → check the new box.

[ ] 2026-03-20 21:30 ET | Claude Code Channels — Discord Integration Plan (5 phases)

Added by Claude Code on Patrick’s Mac

Full plan for connecting Claude Code Channels (new Anthropic feature, launched 2026-03-20) with Discord and the existing n8n infrastructure. Covers everything from initial bot setup through always-on autonomous agent.

Plan document: Claude Code Channels — Discord Integration Plan

5 phases:

Discord bot + local channel (~20 min, Patrick + Claude together) — create bot, install plugin, pair account
Dedicated Discord channels — organize by function (#claude-general, #claude-infra, #claude-alerts, etc.)
n8n webhook integration — route backup failures, inbox changes, build errors into Claude for autonomous handling
Persistent always-on session — host priority: VPS first (already configured), Synology NAS as fallback (residential IP avoids Cloudflare blocker), Mac as last resort
Scale — Asia pairing, scheduled maintenance, CI/CD integration, WordPress monitoring

What requires your hands:

Phase 1 entirely (Discord Developer Portal, bot creation, token, pairing) — ~20 min
Decision points: bot name, permission mode, Asia access timing, NAS networking approach

What Claude can do autonomously:

Phases 2–5 coding and configuration (custom channel code, n8n workflows, systemd service, VPS/NAS setup)

Phase 4 hosting — priority order:

VPS (baseworks-agents) — preferred, already fully configured. First test: does the existing OAuth token (expires ~2027-03-11) work with --channels? If yes, VPS is the host and we’re done.
Synology NAS (home) — fallback. Residential IP means claude login interactive flow should work where the VPS can’t. Needs: Docker or Node.js + Bun compatible architecture (x86 preferred), SSH access, vault clone. If n8n needs to reach it, requires Cloudflare Tunnel or Tailscale.
Patrick’s Mac — last resort, requires staying awake.

Requested action: Review the plan, answer the 6 decision points at the bottom, then schedule ~20 min for Phase 1 setup together.

2026-03-20

[ ] 03:45 ET | Daily Infrastructure Update Report

Added automatically by daily-infra-updates.sh on baseworks-agents VPS

Date: 2026-03-20

Claude Code updated: 2.1.79 (Claude Code) → 2.1.80 (Claude Code)

Backup health:

Site	Schedule	Last Success	Size	Status

| n8n | Daily | 2026-03-20 | 14MB | OK | | baseworks.com | Weekly | 2026-03-15 | DB=519MB, Files=141MB | OK | | staging | Weekly | 2026-03-15 | DB=254MB, Files=141MB | OK | | practice | Weekly | 2026-03-18 | DB=496MB, Files=183MB | OK | | crm | Weekly | 2026-03-15 | DB=18MB, Files=16MB | OK |

Needs your attention:

Warning: Claude CLI authentication failed — vault captures will not work. Check CLAUDE_CODE_OAUTH_TOKEN in ~/.bashrc (must be before the interactive guard)

Updates applied: 1

Requested action: Review any items flagged above. Auto-updates have already been applied and verified.

[ ] 2026-03-20 | BW Activity Plugin — launched on practice.baseworks.com

Added by Claude Code on Asia’s Mac Mini

Asia completed the full deployment of the BW Activity Plugin to practice.baseworks.com today. Here’s what changed.

What was launched:

The custom activity tracking plugin replaces Formidable Form 69 as the back-end for all practice activity data. It includes a purpose-built database, admin interface, REST API, and a set of shortcodes that replace the old Formidable views across the site.

Data migration:

2,604 activity entries migrated from Form 69 → wp_bw_activity
72 users, historical data going back to December 2020
Cluster derivation and key-points re-categorization applied during import

New pages / shortcodes live:

Dashboard — Continue button, activity bars, recent activity list (last 3), weekly minutes, streak
Primer Course Hero — Continue button
History page — Per-category totals (Foundation, Elements, In Person, All-time), full activity list, calendar
Member sidebar widget — Weekly learning time, current streak
PrimerPrint — New page at /primerprint/ — animated SVG visualization of a user’s full Primer journey, fetched live from the REST API. Added to the menu.

Automator:

New Recipe 22021 (Presto → BW Activity Entry) is live and tested — lesson completions now write to the new plugin
Old Recipe 18036 (Presto → Formidable) deactivated
Old Recipe 18647 (GamiPress points) deactivated — point totals are now computed directly from activity entries via shortcodes

What’s still pending:

Code Snippets 30–34 and GamiPress cannot be deactivated yet — Japanese-language widget versions still depend on them. Phase 4 will add lang parameter support to the shortcodes so Japanese pages can be migrated the same way.
PDF export for PrimerPrint is deferred to Phase 3 (will develop on staging).
Activity type color corrections — theory and practice seeded with wrong colors on production; can be fixed via Activity → Activity Types in WP admin (theory: #4A3F8F, practice: #2785a4).

No action needed — this is for your awareness. Full technical detail in bw-activity-plugin-plan.

2026-03-19

[ ] 03:45 ET | Daily Infrastructure Update Report

Added automatically by daily-infra-updates.sh on baseworks-agents VPS

Date: 2026-03-19

baseworks-agents system packages: 9 packages updated
baseworks-n8n system packages: 9 packages updated
n8n updated: 2.10.3 → 2.10.3 (health check: passed)

Backup health:

Site	Schedule	Last Success	Size	Status
n8n	Daily	2026-03-19	14MB	OK
baseworks.com	Weekly	2026-03-15	DB=519MB, Files=141MB	OK
staging	Weekly	2026-03-15	DB=254MB, Files=141MB	OK
practice	Weekly	2026-03-18	DB=496MB, Files=183MB	OK
crm	Weekly	2026-03-15	DB=18MB, Files=16MB	OK

Needs your attention:

Warning: Claude CLI authentication failed — vault captures will not work. Check CLAUDE_CODE_OAUTH_TOKEN in ~/.bashrc (must be before the interactive guard)

Updates applied: 3

Requested action: Review any items flagged above. Auto-updates have already been applied and verified.

[ ] 00:45 ET | practice.baseworks.com — follow up with xCloud on DB password rotation

Context: During tonight’s security cleanup session, we removed MalCare, a dormant malware backdoor, and associated files from the practice site. As a precaution, we attempted to rotate the database password but found no way to do it through the xCloud panel.

xCloud support responded with instructions to change the WordPress user password via PHPMyAdmin, which is a different thing (WP login password, not DB credentials).

What needs clarifying with xCloud:

How to change the MySQL database user password for the practice site (user: u2_practice_basewo, DB: db2_practice_basewo)
Specifically: is there a panel control for this, or does their support team handle it?
After the change: will the new password be visible/stored in the xCloud panel, or will it need to be manually updated in wp-config.php?

Important note: Do NOT change the DB password via MySQL ALTER USER directly — this would desync from xCloud’s stored credentials and potentially break their tooling. Wait for xCloud to confirm the correct procedure.

Requested action: Follow up with xCloud support with the above questions. Once you have the procedure, it can be done in a future Claude Code session.

2026-03-18

[ ] 19:30 ET | Taxonomy concept notes created — ready for wikilinks

Added by Claude Code on Asia’s Mac Mini

Asia and Claude Code completed the Baseworks taxonomy concept notes project today. All individual concept notes have been created in 02-areas/method-admin/core/key-definitions-repo/ and the 12 foci stubs in 02-areas/method-admin/core/foci/ have been populated.

What was done:

key-definitions.md — workflow callout added at top; See: links added to every relevant section pointing to individual notes
movement-patterns.md — retitled “Movement Patterns Master”
patrick-oancia.md, satoko-horie.md, asia-shcherbakova.md — frontmatter + aliases added
All 12 foci stubs populated (content, tags, Related sections)
32 concept notes created in key-definitions-repo/

Notes ready to wikilink (all in 02-areas/method-admin/core/key-definitions-repo/ unless noted):

Method development:

Communicability
Iterative Refinement
Reverse Engineering
Emergence
Emergent Outcome (stub — content still to be written)

Movement and structure:

Movement Patterns
Form
Set and Sequence (aliases: Set, Sequence)
Micro- and Macro-Movements (aliases: all hyphen/space variants)
Simultaneity

The Six Principles:

The Six Principles
Distributed Activation (alias: DA)
Micro Movements (alias: MM)
Gridlines and Symmetry (aliases: GS, Gridlines & Symmetry)
Fixing-Separating-Isolating (alias: FSA)
Natural Breathing (alias: NB)
Intensity Modification (alias: IM)

Focus framework:

Focus (aliases: Foci, focus framework)
STRUCTURE · GRAVITY · ASCEND · TORSION · CONVERGE · EXPAND · INFLECT · INTENT · EQUATE · TRANSIT · TRANSPOSE · ISOLATE — all in foci/

Perceptual skills:

Perceptual Skills
3 Types of Body Awareness (alias: body awareness)
Interoceptive Awareness
Proprioceptive Awareness (aliases: Localized Proprioceptive Awareness, Muscular Mechanosensation)
Spatial Awareness

Frameworks:

SENSE-CONTROL-ADAPT (alias: SCA)
Physical Intelligence (alias: PQ)

Pedagogy:

Practice structure:

Ignition
Assimilation
Module (aliases: Foundation, Elements, Strategy, Integrate)
Cyclicity (alias: cyclical practice)

Sync protocol reminder: Each note has source-section and sync-level: content in frontmatter. When wikilinks are added across the vault, no content changes are needed — just link to the note names above and aliases will handle variant spellings.

[ ] 15:30 ET | Research needed — Google Drive media linking in Obsidian campaign notes

Added by Claude Code on Patrick’s Mac

Context: During the campaign infrastructure planning session (2026-03-18), we designed a campaign/newsletter structure under 02-areas/communications/. Campaign notes will reference images via standard markdown image links (![alt](url)) rather than storing binary files in the git repo. The preferred workflow: find images in Google Drive (via Gemini or anti-gravity agent manager), then drag or paste the reference into the campaign note in Obsidian.

What needs to be researched:

What format does the reference arrive in? When you find an image in Google Drive via Gemini/anti-gravity and drag or copy-paste it into a note, what does Obsidian actually receive — a Drive sharing link (https://drive.google.com/file/d/ID/view), a direct image URL, or a local file path?
Does Obsidian render it inline? Standard markdown image syntax (![alt](url)) works in Obsidian, but only if the URL points directly to an image file. Google Drive sharing links point to a page, not a raw image — they won’t render. The direct format is https://drive.google.com/uc?export=view&id=FILE_ID.
Is a conversion step needed? If the pasted reference is a sharing link rather than a direct image URL, we’d need either:
- A manual conversion (extract the file ID, rewrite as direct URL)
- An Obsidian plugin that rewrites Drive links automatically
- An n8n workflow or script that handles the conversion
- A different drag source that gives us a renderable URL directly
Alternative: FileBrowser on VPS. The baseworks-agents VPS already has FileBrowser running at port 8090 serving /srv/baseworks/uploads/. If exposed via a public URL (e.g., files.baseworks.com), images stored there would have direct URLs that Obsidian renders natively. This bypasses the Drive URL format issue entirely, though it loses the Gemini visual search advantage.

Requested action: Quick test — find an image in Google Drive, paste the reference into an Obsidian note, and see what renders. That will tell us immediately whether there’s a gap to bridge. Report findings so we can finalize the media workflow for the campaign structure.

[ ] 03:45 ET | Daily Infrastructure Update Report

Added automatically by daily-infra-updates.sh on baseworks-agents VPS

Date: 2026-03-18

Claude Code updated: 2.1.77 (Claude Code) → 2.1.78 (Claude Code)

Backup health:

Site	Schedule	Last Success	Size	Status
n8n	Daily	2026-03-18	14MB	OK
baseworks.com	Weekly	2026-03-15	DB=519MB, Files=141MB	OK
staging	Weekly	2026-03-15	DB=254MB, Files=141MB	OK
practice	Weekly	2026-03-15	DB=495MB, Files=183MB	OK
crm	Weekly	2026-03-15	DB=18MB, Files=16MB	OK

Needs your attention:

Warning: Claude CLI authentication failed — vault captures will not work. Check CLAUDE_CODE_OAUTH_TOKEN in ~/.bashrc (must be before the interactive guard)

Updates applied: 1

Requested action: Review any items flagged above. Auto-updates have already been applied and verified.

2026-03-17

[ ] 18:15 ET | practice.baseworks.com — server optimization plan and next steps

Added by Claude Code on Patrick’s Mac

Server diagnostic and optimization session for practice.baseworks.com (and the shared xCloud server at 5.180.253.171 — Ryzen 9 9950X, 6 cores, 16GB RAM, hosting baseworks.com + practice + staging).

What was done today

MariaDB InnoDB Buffer Pool — increased from 128MB to 3072MB via xCloud Auto-Tune (manually adjusted down from auto-tuned 9595MB to be safe for 3-site server). This is the single biggest performance lever — the entire 1.1GB combined DB now fits in memory.
Slow Query Log — enabled, threshold set to 1 second. Logs to /var/log/mysql/mariadb-slow.log. Review after a few days of traffic.
PHP version — upgraded practice.baseworks.com from 8.2 to 8.3. Working fine.
PHP memory/execution settings — attempted to reduce memory limit (512→256MB) and execution time (180→60s). This caused a critical error — BuddyBoss workers use ~265MB at idle, so 256MB was below their baseline. Reverted to original values (512MB, 180s). Leave these alone.

Still to do — safe changes via xCloud dashboard

5. Increase PHP-FPM workers for practice.baseworks.com

Current: pm.max_children = 6 (only 6 concurrent PHP requests before queueing)
Recommended: 12-15
Where: xCloud dashboard → Site (practice.baseworks.com) → FPM Configurations → PM Max Children
Also adjust: PM Start Servers → 4, PM Min Spare Servers → 2, PM Max Spare Servers → 6
Balance across sites: practice = 12-15, baseworks.com = 8-10, staging = 4-6
This is a safe change — just allows more concurrent request handling within existing RAM

6. Verify OPcache is enabled and properly configured

Where: xCloud dashboard → Server → PHP Configuration → OPcache
Should be auto-enabled but CLI check showed it wasn’t loaded. Verify for PHP-FPM (web), not just CLI.
Key settings: opcache.memory_consumption should be 256MB+, opcache.max_accelerated_files should be 20000+ (52 active plugins = lots of compiled code)

Database cleanup — via WP-CLI or WP Admin

7. Clean up Action Scheduler completed actions

30,797 completed actions in wp_actionscheduler_actions (35MB table)
WP Admin → Tools → Scheduled Actions → delete completed
Or via SSH: cd ~/files && wp action-scheduler clean (check exact syntax)

8. Optimize large database tables

wp_postmeta = 298MB, wp_posts = 87MB, wp_actionscheduler_actions = 35MB
Run during low-traffic: wp db query "OPTIMIZE TABLE wp_postmeta" (repeat for others)
Safe but locks the table briefly during optimization

9. Add composite index on wp_postmeta (optional, after backup)

Default WP only indexes meta_key and post_id separately
A composite index speeds up the meta queries BuddyBoss/LearnDash/WooCommerce generate
Command: wp db query "ALTER TABLE wp_postmeta ADD INDEX post_id_meta_key (post_id, meta_key(191))"
Adds ~50-100MB to table size. Do after a B2 backup.

Plugin audit — 52 active plugins, review these

Plugin	Table/Size	Question
wp-stream + wp_stream_meta	19MB + 5MB	Activity logging — actively used?
Unknown (wp_uap_action_log_meta)	43MB	Affiliate/referral tracking — needed?
wp-grid-builder + 3 addons	4 plugins	Used on practice or only baseworks.com?
cartflows	—	Used on practice?
facebook-for-woocommerce	—	Actively needed?
temporary-login-without-password	—	Should this be active in production?
woocommerce-legacy-rest-api	—	May not be needed with current WooCommerce

WPML overhead — 95MB across 5 tables

wp_icl_strings (47MB), wp_icl_string_pages (30MB), wp_icl_translate (9.8MB), wp_icl_translation_status (7.6MB), wp_icl_string_translations (7.5MB). Can’t remove if you need multilingual, but worth checking for orphaned translations. Also relevant to the Fluent Community migration question — if you move away from WPML, this overhead goes away.

Monitoring — after changes settle

Review slow query log after 3-5 days to identify the actual bottleneck queries
Monitor Redis hit rate via wp redis status — check hit ratio periodically
TTFB baseline — currently ~3s on practice.baseworks.com. Recheck after buffer pool warms up (give it 24 hours of normal traffic)

Broader migration discussion (separate from server optimization)

Also discussed Fluent Community as potential replacement for BuddyBoss + LearnDash. Key blocker: no WPML integration — would require duplicating courses per language. Worth checking if WPML support is on Fluent Community’s roadmap. Full custom stack (Next.js + Postgres) discussed and filed as long-term possibility but not practical with current team size.

Server resource budget after all changes

Resource	Before	After	Remaining
InnoDB Buffer Pool	128MB	3072MB	—
PHP Workers (total)	~18	~30	—
Max PHP memory	3GB	7.5GB theoretical	—
Redis	~128MB	same	—
Est. peak	~4GB	~12GB	~4GB headroom

If the server needs more room later, bumping to 32GB RAM on Hetzner is straightforward.

2026-03-13

[ ] 14:00 ET | Vault cleanup — discussion notes archived, workflow suggestion

Added by Claude Code on Asia’s Mac Mini

Asia’s session today did a pass through the vault to identify and archive abandoned discussion notes — notes containing proposed or rejected copy, red-markup alternatives, and working discussion that was never properly filed. No action needed — FYI and a workflow suggestion for going forward.

Why this matters for QMD

The knowledge base uses semantic search (QMD) to surface relevant vault content. Discussion notes that contain proposed-but-rejected phrasings, red-markup alternatives, or superseded drafts get embedded alongside live copy — which means search can return outdated content as if it were current. Tagging these notes no_embed: true excludes them from the index and keeps search results clean.

Notes cleaned up today

Tagged status: archived, no_embed: true, and given a [!warning] callout:

practice-sessions-montreal-2026-page-draft-and-form-discussion.md — rounds 1–3 of page-building discussion (through Mar 5), superseded by live page
montreal-practice-sessions-event-copy-discussion.md — original Feb 26 brief with raw working discussion, predates everything built
04-archive/STRUCTURE-PROPOSAL.md — January vault structure proposal
spring-2026-landing-page-copy-discussion.md — renamed from spring-2026-landing-page-copy.md; was a mix of March 8 snapshot and round 2 proposed edits in red markup

spring-2026-meta-campaign-copy.md was also split into two separate files:

spring-2026-meta-campaign-copy.md — clean copy + deployment status (status: live)
spring-2026-meta-campaign-discussion.md — Meta policy notes, resolved questions, approved alternative phrasings, revision log (status: archived, no_embed: true)

Workflow suggestion going forward

The underlying issue is that discussion elements (policy constraints, alternatives considered, revision log) and final copy tend to live in the same note, and when a discussion concludes, the note doesn’t get archived. A cleaner pattern:

During a working session: keep discussion elements in a -discussion note, or split them out before a campaign launches or a page goes live
When discussion is resolved: change status to archived, add no_embed: true and the archived tag, add a [!warning] callout pointing to the live copy note
The live copy note contains only current, approved copy — nothing proposed or rejected

This doesn’t require a significant workflow change. It’s mainly a habit of separating discussion from copy at the moment a decision is finalized, rather than leaving a mixed note as-is indefinitely.

[ ] 11:30 ET | Winter Study Group recap campaign — outlines ready for review

Added by Claude Code on Patrick’s Mac

The Winter Study Group recap campaign is structured and ready for your review. Everything is in the vault under 02-areas/website/.

What was created:

Vault structure — new content organization under 02-areas/website/:
- _content-index.md — master cross-reference for all content types
- blog-articles/_blog-index.md — blog posts index
- social-posts/_social-index.md — social media index
- newsletter/_newsletter-index.md — newsletter index
- podcast-archive/_podcast-index.md — placeholder for future import
Blog post outline — 02-areas/website/blog-articles/2026-03-winter-study-group-recap.md
- Working title: “From Three Forms to Twenty-One: Inside the Winter 2026 Study Group”
- 8 sections with word counts and draft direction for each
- 7 candidate vignettes drawn from participant interviews (Magali, Guylaine, Sarah, Any — all anonymized) and forum posts — select 3-4 for the final draft
- Photo placement suggestions throughout
- Notes on translation verification (quotes from French interviews)
Social posts outline — 02-areas/website/social-posts/2026-03-winter-study-group-recap.md
- LinkedIn (~250 words): professional/reflective angle, movement education framing
- Instagram (carousel + ~150 words): photo-driven, brief caption
- Facebook (~200 words): community-facing, warmer tone
Newsletter feature outline — 02-areas/website/newsletter/2026-03-winter-study-group-recap.md
- ~200 word teaser for newsletter blast, one vignette, link to blog post

What to review:

Blog post outline (sections, vignettes to include/exclude, overall direction)
Vault organization structure (does this make sense going forward?)
Once reviewed, full copy will be drafted for all pieces

Follow-up tasks (separate):

Curate session photos for the blog post and social posts
Import past blog posts and podcast episodes into the vault
Decide on French version of blog post

2026-03-12

[ ] 21:30 ET | Stale cache monitor — ready to set up on VPS

Added by Claude Code on Patrick’s Mac

Next session: Set up automated stale cache monitoring on the baseworks-agents VPS. The script would run periodically via cron and test key pages for redirect loops, unexpected status codes, and stale content. Reports issues to Patrick’s inbox when problems are detected.

Proposed approach:

Cron job on baseworks-agents VPS (e.g., every 30 minutes)
Curl a list of key URLs (homepage, /primer/, /events/, etc.) checking for: redirect loops, non-200 status codes, response time anomalies, and stale Last-Modified / Age headers
Compare responses with and without cookies (catch cookie-triggered redirect loops)
On failure: post to Patrick’s inbox + optionally trigger a Cloudflare cache purge automatically
Silent when everything is healthy (no noise)

To kick this off: Start a Claude Code session on the VPS and ask it to build the monitoring script. Reference this inbox item for context.

[ ] 21:30 ET | Homepage hexagon icons fixed + .htaccess 301→302 fix

Added by Claude Code on Patrick’s Mac

Two fixes deployed tonight:

1. Homepage hexagon icons — The “How it works” section had solid black hexagonal icons. The Shape Bullets widget SVG had no fill attribute (defaults to black). Added CSS in WordPress Additional CSS setting fill: transparent; stroke: #3A3A3A; stroke-width: 1 for both widget instances.

2. .htaccess trailing-slash redirect changed from 301 to 302 — Root cause of recurring “too many redirects” on /primer/ and potentially other pages. Browsers permanently cache 301 redirects. When xCloud’s nginx config resets (as happened 2026-03-08), the browser caches a bad redirect and loops indefinitely. With 302, browsers won’t permanently cache it, so transient server issues self-heal.

Still needed: Contact xCloud about making the global_vars.conf fix permanent (existing open item from 2026-03-08). The 302 change mitigates the symptom but the underlying nginx config instability remains.

Backups: DB backup at /tmp/backup-homepage-icons-20260312-211813.sql on server. .htaccess backed up to .htaccess.bak-20260312 on server and saved to sites/baseworks.com/configs/htaccess.txt in changelog repo.

[ ] 19:00 ET | Intake form restructured + Outcome C copy fixed — deployed

Added by Claude Code on Asia’s Mac Mini

Asia’s session today addressed a copy error in Outcome C of the Practice Sessions intake form (Primer was being described as a multi-session in-person course, when it’s an online self-paced course). Everything has been deployed to the live site.

What was done:

1. New vault node — Practice Sessions — Intake Form Created to track the intake form as its own thing — scoring logic, step questions, and outcome copy in both EN and FR. Status table included. This is now the single place to check/update intake form copy or logic.

2. Outcome C copy corrected (EN + FR) Old copy implied Primer was multiple in-person sessions. New copy:

Primer is our foundational 12-hour self-paced course — study independently or join a virtual cohort. It covers the core concepts and movement vocabulary of the Method, giving you the framework that Practice Sessions and the Study Group build on. We also run Open Days and other events throughout the year.

Your suggested line about studying standalone or in virtual cohorts was woven in. The virtual cohort mention is there even though the infrastructure isn’t fully live yet — noted as intentional.

3. PHP files updated — both C and Cmod cards, EN + FR

2026-03-05-practice-sessions-quiz-v2.php — Outcome C + Cmod paragraphs updated
2026-03-05-practice-sessions-quiz-v2-fr.php — Résultat C + Cmod paragraphs updated
Both committed to baseworks-changelog. Asia deployed to the live site.

4. Vault restructuring

practice-sessions-page-copy.md — intake form section removed; link to new intake form node added; note_type: live-copy added to frontmatter
practice-sessions-page-copy-fr.md — same treatment
practice-sessions-montreal-2026-page-draft-and-form.md — renamed to practice-sessions-montreal-2026-page-draft-and-form-discussion.md; note_type: discussion, status: resolved added; top note added pointing to the three active nodes
All 10 vault files that referenced the old draft filename updated

No action needed — FYI only.

2026-03-10

[ ] 21:45 ET | Uncommitted work in baseworks-changelog repo — needs review

Added by Claude Code on Patrick’s Mac

The baseworks-changelog repo (~/Documents/baseworks-changelog/) has 12 untracked files and 1 modified file from previous sessions that were never committed. All date from around 2026-02-10 (SEO migration work). Review and decide what to commit.

Modified file:

docs/SEO-PLUGIN-MIGRATION-PLAN.md — Slim SEO to SEOPress migration plan (updated)

Untracked mu-plugins (production — baseworks.com):

sites/baseworks.com/mu-plugins/llms-txt-custom-content.php — Customizes SEOPress LLMs.txt output to include Baseworks CPTs (articles, events, podcasts, instructors) instead of default post_type=post
sites/baseworks.com/mu-plugins/seopress-breadcrumbs-no-home.php — Removes “Home” from SEOPress HTML breadcrumbs

Untracked mu-plugins (staging):

sites/staging.baseworks.com/mu-plugins/seopress-event-schema-dates.php — Fixes ACF date format mismatches in SEOPress Event schema JSON-LD
sites/staging.baseworks.com/mu-plugins/staging-safeguards.php — Blocks search indexing and disables WP Remote Users Sync outbound calls on staging

Untracked support tickets (drafts):

support-tickets/seopress-llmstxt-custom-post-types.md — Draft ticket to SEOPress requesting native CPT support in LLMs.txt generator
support-tickets/xcloud-staging-push-issues.md — Draft ticket to xCloud about staging push overwriting production wp-config.php salts (broke FluentSMTP)

Untracked reference/analysis:

SEOPRESS_ELEMENTOR_NOTIFICATION.md — Analysis of a SEOPress notification triggered by Elementor being active

Untracked backups/configs:

sites/baseworks.com/backups/fluentmail-settings-production-backup.json — FluentSMTP production config backup
sites/baseworks.com/configs/robots.txt — robots.txt file
sites/baseworks.com/configs/seopress_redirects_from_slim_seo.csv — Redirect rules exported from Slim SEO

Untracked mockup:

sites/baseworks.com/mockups/winter-2026-closing-deck.html — Winter 2026 closing session HTML mockup (plus package.json, package-lock.json, node_modules/ — likely from a local dev build)

Requested action: Review each item and either commit to the repo or remove if no longer needed. The node_modules/ directory should be .gitignored regardless.

[ ] 12:30 ET | Participation terms — add interpreter availability clause

Added by Claude Code on Patrick’s Mac

Context: During today’s Study Group landing page copy session, you noted that the participation terms should mention interpreter availability where feasible. This applies broadly to all program terms.

What was done on the landing page: The language FAQ now frames English as the working language chosen for international accessibility, with French captions and forum communication noted for Montreal. Interpreters are intentionally not mentioned on the landing page.

Still needed: Add a clause to the participation terms (on the website) to the effect that “where feasible, interpreters may be available for certain programs.” Asia has a matching inbox item to draft the wording.

Requested action: Coordinate with Asia on the clause. Review and approve before it goes live.

2026-03-08

[ ] 17:30 ET | xCloud nginx config was reset — fix re-applied, contact xCloud needed

Added by Claude Code on VPS (asia)

Asia flagged the stale cache issue on page 46997 (smsg-spring-2026). Root cause identified and fixed.

What happened: The xCloud global_vars.conf fix from January 2026 was reverted — likely reset during a server update. The trailing-slash stripping rule is active again, so nginx-helper can’t find cache files on page save (exact same bug as Jan 2026, just silently back). The four-layer button kept working because it bypasses nginx-helper entirely.

What was fixed (2026-03-08): Added bw_fix_nginx_helper_cache_key() into cloudflare-auto-purge.php — same workaround logic as the old disabled fix-nginx-helper-cache-key.php, without the duplicate function conflict. Tested on page 46997: confirmed cache file is deleted correctly on save.

Action needed from you: Contact xCloud again (reference the January 2026 ticket) to report the config was reset and ask them to re-apply the global_vars.conf change. This is the exact scenario their support warned about. The full context for the email is in docs/XCLOUD-NGINX-CACHE-ISSUE.md in the changelog repo.

2026-03-04

[ ] 12:30 ET | Set up Canva MCP on VPS

Added by Claude Code on Patrick’s Mac

Goal: Give Claude Code on VPS the ability to work with Canva directly.

Status: Not yet set up — VPS settings.json has no Canva entry (checked 2026-03-05).

Canva is a built-in Claude.ai connector. To enable it on the VPS:

SSH into the VPS: ssh patrick@46.224.129.16
Start Claude Code in any tmux session
Type /mcp and look for Canva in the list
Follow the auth prompt — it will give you a URL to open in your browser
Authorize in your browser, and the VPS session picks it up

If Canva doesn’t appear in /mcp, go to claude.ai/settings/connectors and enable it there first.

Requested action: Quick setup — should take under 5 minutes.

[ ] 12:30 ET | Set up Google Workspace MCP on VPS

Added by Claude Code on Patrick’s Mac

Goal: Give Claude Code on VPS the ability to work with Google Docs, Sheets, Slides via the community google-workspace-mcp package (already available on VPS via npx). Needs OAuth credentials from Google Cloud Console.

Step 1: Create Google Cloud OAuth credentials (~5 min)

Go to console.cloud.google.com
Create a new project (or use an existing one) — e.g. “Baseworks MCP”
Go to APIs & Services > Library and enable these APIs:

Google Docs API
Google Sheets API
Google Slides API
Google Drive API

Go to APIs & Services > Credentials
Click Create Credentials > OAuth 2.0 Client ID

Application type: Desktop app
Name: “Baseworks Claude Code”

Download the JSON file (it will be named something like client_secret_*.json)

Step 2: Configure on VPS (~2 min)

SSH in: ssh patrick@46.224.129.16
Create the config directory: mkdir -p ~/.google-mcp
Copy the downloaded JSON to the VPS:

 scp ~/Downloads/client_secret_*.json patrick@46.224.129.16:~/.google-mcp/credentials.json

Add the account:

 npx -y google-workspace-mcp accounts add baseworks

This gives you a URL — open it in your browser, authorize with the Baseworks Google account, paste the code back.

Step 3: Register with Claude Code (~1 min)

claude mcp add --scope user -t stdio google-workspace -- npx -y google-workspace-mcp serve

Step 4: Verify Start a new Claude Code session and type /mcp — you should see google-workspace listed. Ask Claude to list your Google Docs to test.

Step 5: Set up for Asia too Once it works for your user, repeat steps 2 and 4 for Asia’s user (ssh asia@46.224.129.16). The same credentials.json can be shared, but she’ll need to authenticate her own Google account.

Requested action: Do this when you have ~15 minutes. The Google Cloud setup is the longest part. Tell Claude to assist once you have the credentials.json.

2026-04-10

[ ] 03:45 ET | Daily Infrastructure Update Report

Added automatically by daily-infra-updates.sh on baseworks-agents VPS

Date: 2026-04-10

Claude Code updated: 2.1.97 (Claude Code) → 2.1.98 (Claude Code)
baseworks-agents system packages: 13 packages updated
n8n — UPDATE NEEDS ATTENTION: health=unknown, version=unknown
PostgreSQL — UPDATE NEEDS ATTENTION: health=unknown

Backup health:

Site	Schedule	Last Success	Size	Status

| n8n | Daily | 2026-04-04 | 15MB | STALE (6 days) | | baseworks.com | Weekly | 2026-04-05 | DB=544MB, Files=143MB | OK | | staging | Weekly | 2026-04-05 | DB=254MB, Files=141MB | OK | | practice | Weekly | 2026-04-09 | DB=509MB, Files=183MB | OK | | crm | Weekly | 2026-04-05 | DB=38MB, Files=16MB | OK |

Needs your attention:

Warning: n8n update may have failed — health status: unknown
Warning: PostgreSQL update may have failed — health: unknown
Warning: n8n daily backup is 6 days old (last: 2026-04-04)
Warning: Claude CLI authentication failed — vault captures will not work. Check CLAUDE_CODE_OAUTH_TOKEN in ~/.bashrc (must be before the interactive guard)
Warning: n8n cannot SSH to baseworks-agents — vault capture pipeline is broken. Check SSH key at /opt/n8n-ssh/ on baseworks-n8n

Updates applied: 2

Requested action: Review any items flagged above. Auto-updates have already been applied and verified.

2026-04-11

[ ] 03:45 ET | Daily Infrastructure Update Report

Added automatically by daily-infra-updates.sh on baseworks-agents VPS

Date: 2026-04-11

Claude Code updated: 2.1.98 (Claude Code) → 2.1.101 (Claude Code)
baseworks-agents system packages: 15 packages updated
n8n — UPDATE NEEDS ATTENTION: health=unknown, version=unknown
PostgreSQL — UPDATE NEEDS ATTENTION: health=unknown

Backup health:

Site	Schedule	Last Success	Size	Status

| n8n | Daily | 2026-04-04 | 15MB | STALE (7 days) | | baseworks.com | Weekly | 2026-04-05 | DB=544MB, Files=143MB | OK | | staging | Weekly | 2026-04-05 | DB=254MB, Files=141MB | OK | | practice | Weekly | 2026-04-09 | DB=509MB, Files=183MB | OK | | crm | Weekly | 2026-04-05 | DB=38MB, Files=16MB | OK |

Needs your attention:

Warning: n8n update may have failed — health status: unknown
Warning: PostgreSQL update may have failed — health: unknown
Warning: n8n daily backup is 7 days old (last: 2026-04-04)
Warning: Claude CLI authentication failed — vault captures will not work. Check CLAUDE_CODE_OAUTH_TOKEN in ~/.bashrc (must be before the interactive guard)
Warning: n8n cannot SSH to baseworks-agents — vault capture pipeline is broken. Check SSH key at /opt/n8n-ssh/ on baseworks-n8n

Updates applied: 2

Requested action: Review any items flagged above. Auto-updates have already been applied and verified.

2026-04-12

[ ] 03:45 ET | Daily Infrastructure Update Report

Added automatically by daily-infra-updates.sh on baseworks-agents VPS

Date: 2026-04-12

baseworks-agents system packages: 2 packages updated
n8n — UPDATE NEEDS ATTENTION: health=unknown, version=unknown
PostgreSQL — UPDATE NEEDS ATTENTION: health=unknown
FileBrowser — UPDATE NEEDS ATTENTION: health=starting

Backup health:

Site	Schedule	Last Success	Size	Status

| n8n | Daily | 2026-04-04 | 15MB | STALE (8 days) | | baseworks.com | Weekly | 2026-04-05 | DB=544MB, Files=143MB | OK | | staging | Weekly | 2026-04-05 | DB=254MB, Files=141MB | OK | | practice | Weekly | 2026-04-09 | DB=509MB, Files=183MB | OK | | crm | Weekly | 2026-04-05 | DB=38MB, Files=16MB | OK |

Needs your attention:

Warning: n8n update may have failed — health status: unknown
Warning: PostgreSQL update may have failed — health: unknown
Warning: FileBrowser update may have failed — health: starting
Warning: n8n daily backup is 8 days old (last: 2026-04-04)
Warning: Claude CLI authentication failed — vault captures will not work. Check CLAUDE_CODE_OAUTH_TOKEN in ~/.bashrc (must be before the interactive guard)
Warning: n8n cannot SSH to baseworks-agents — vault capture pipeline is broken. Check SSH key at /opt/n8n-ssh/ on baseworks-n8n

Updates applied: 1

Requested action: Review any items flagged above. Auto-updates have already been applied and verified.

2026-04-13

[ ] 03:45 ET | Daily Infrastructure Update Report

Added automatically by daily-infra-updates.sh on baseworks-agents VPS

Date: 2026-04-13

Claude Code updated: 2.1.101 (Claude Code) → 2.1.104 (Claude Code)
baseworks-agents system packages: 2 packages updated
n8n — UPDATE NEEDS ATTENTION: health=unknown, version=unknown
PostgreSQL — UPDATE NEEDS ATTENTION: health=unknown

Backup health:

Site	Schedule	Last Success	Size	Status

| n8n | Daily | 2026-04-04 | 15MB | STALE (9 days) | | baseworks.com | Weekly | 2026-04-12 | DB=547MB, Files=143MB | OK | | staging | Weekly | 2026-04-12 | DB=254MB, Files=141MB | OK | | practice | Weekly | 2026-04-12 | DB=510MB, Files=183MB | OK | | crm | Weekly | 2026-04-12 | DB=36MB, Files=16MB | OK |

Needs your attention:

Warning: n8n update may have failed — health status: unknown
Warning: PostgreSQL update may have failed — health: unknown
Warning: n8n daily backup is 9 days old (last: 2026-04-04)
Warning: Claude CLI authentication failed — vault captures will not work. Check CLAUDE_CODE_OAUTH_TOKEN in ~/.bashrc (must be before the interactive guard)
Warning: n8n cannot SSH to baseworks-agents — vault capture pipeline is broken. Check SSH key at /opt/n8n-ssh/ on baseworks-n8n

Updates applied: 2

Requested action: Review any items flagged above. Auto-updates have already been applied and verified.

2026-04-14

[ ] 16:15 ET | Daily Infrastructure Update Report

Added automatically by daily-infra-updates.sh on baseworks-agents VPS

Date: 2026-04-14

Claude Code updated: 2.1.105 (Claude Code) → 2.1.107 (Claude Code)
baseworks-agents system packages: 7 packages updated
baseworks-n8n system packages: 26 packages updated
n8n updated: 2.10.3 → 2.10.3 (health check: passed)

Backup health:

Site	Schedule	Last Success	Size	Status

| n8n | Daily | 2026-04-14 | 15MB | OK | | baseworks.com | Weekly | 2026-04-12 | DB=547MB, Files=143MB | OK | | staging | Weekly | 2026-04-12 | DB=254MB, Files=141MB | OK | | practice | Weekly | 2026-04-12 | DB=510MB, Files=183MB | OK | | crm | Weekly | 2026-04-12 | DB=36MB, Files=16MB | OK |

Updates applied: 4

Requested action: Review any items flagged above. Auto-updates have already been applied and verified.

[ ] 03:45 ET | Daily Infrastructure Update Report

Added automatically by daily-infra-updates.sh on baseworks-agents VPS

Date: 2026-04-14

Claude Code updated: 2.1.104 (Claude Code) → 2.1.105 (Claude Code)
baseworks-agents system packages: 3 packages updated
n8n — UPDATE NEEDS ATTENTION: health=unknown, version=unknown
PostgreSQL — UPDATE NEEDS ATTENTION: health=unknown

Backup health:

Site	Schedule	Last Success	Size	Status

| n8n | Daily | 2026-04-04 | 15MB | STALE (10 days) | | baseworks.com | Weekly | 2026-04-12 | DB=547MB, Files=143MB | OK | | staging | Weekly | 2026-04-12 | DB=254MB, Files=141MB | OK | | practice | Weekly | 2026-04-12 | DB=510MB, Files=183MB | OK | | crm | Weekly | 2026-04-12 | DB=36MB, Files=16MB | OK |

Needs your attention:

Warning: n8n update may have failed — health status: unknown
Warning: PostgreSQL update may have failed — health: unknown
Warning: n8n daily backup is 10 days old (last: 2026-04-04)
Warning: Claude CLI authentication failed — vault captures will not work. Check CLAUDE_CODE_OAUTH_TOKEN in ~/.bashrc (must be before the interactive guard)
Warning: n8n cannot SSH to baseworks-agents — vault capture pipeline is broken. Check SSH key at /opt/n8n-ssh/ on baseworks-n8n

Updates applied: 2

Requested action: Review any items flagged above. Auto-updates have already been applied and verified.

2026-04-15

[ ] 03:45 ET | Daily Infrastructure Update Report

Added automatically by daily-infra-updates.sh on baseworks-agents VPS

Date: 2026-04-15

Claude Code updated: 2.1.107 (Claude Code) → 2.1.108 (Claude Code)
baseworks-agents system packages: 4 packages updated
baseworks-n8n system packages: 4 packages updated

Backup health:

Site	Schedule	Last Success	Size	Status

| n8n | Daily | 2026-04-15 | 15MB | OK | | baseworks.com | Weekly | 2026-04-12 | DB=547MB, Files=143MB | OK | | staging | Weekly | 2026-04-12 | DB=254MB, Files=141MB | OK | | practice | Weekly | 2026-04-12 | DB=510MB, Files=183MB | OK | | crm | Weekly | 2026-04-12 | DB=36MB, Files=16MB | OK |

Updates applied: 3

Requested action: Review any items flagged above. Auto-updates have already been applied and verified.

2026-04-16

[ ] 03:45 ET | Daily Infrastructure Update Report

Added automatically by daily-infra-updates.sh on baseworks-agents VPS

Date: 2026-04-16

Claude Code updated: 2.1.108 (Claude Code) → 2.1.110 (Claude Code)
baseworks-agents system packages: 3 packages updated
baseworks-n8n system packages: 3 packages updated
n8n updated: 2.10.3 → 2.10.3 (health check: passed)
PostgreSQL updated: 16.12 → 16.12 (health check: passed)

Backup health:

Site	Schedule	Last Success	Size	Status

| n8n | Daily | 2026-04-16 | 15MB | OK | | baseworks.com | Weekly | 2026-04-12 | DB=547MB, Files=143MB | OK | | staging | Weekly | 2026-04-12 | DB=254MB, Files=141MB | OK | | practice | Weekly | 2026-04-12 | DB=510MB, Files=183MB | OK | | crm | Weekly | 2026-04-12 | DB=36MB, Files=16MB | OK |

Updates applied: 5

Requested action: Review any items flagged above. Auto-updates have already been applied and verified.

2026-04-17

[ ] 03:45 ET | Daily Infrastructure Update Report

Added automatically by daily-infra-updates.sh on baseworks-agents VPS

Date: 2026-04-17

Claude Code updated: 2.1.110 (Claude Code) → 2.1.112 (Claude Code)
baseworks-agents system packages: 2 packages updated
baseworks-n8n system packages: 2 packages updated

Backup health:

Site	Schedule	Last Success	Size	Status

| n8n | Daily | 2026-04-17 | 15MB | OK | | baseworks.com | Weekly | 2026-04-12 | DB=547MB, Files=143MB | OK | | staging | Weekly | 2026-04-12 | DB=254MB, Files=141MB | OK | | practice | Weekly | 2026-04-12 | DB=510MB, Files=183MB | OK | | crm | Weekly | 2026-04-12 | DB=36MB, Files=16MB | OK |

Updates applied: 3

Requested action: Review any items flagged above. Auto-updates have already been applied and verified.

2026-04-18

[ ] 03:45 ET | Daily Infrastructure Update Report

Added automatically by daily-infra-updates.sh on baseworks-agents VPS

Date: 2026-04-18

Claude Code updated: 2.1.112 (Claude Code) → 2.1.114 (Claude Code)
baseworks-agents system packages: 2 packages updated
baseworks-n8n system packages: 3 packages updated

Backup health:

Site	Schedule	Last Success	Size	Status

| n8n | Daily | 2026-04-18 | 15MB | OK | | baseworks.com | Weekly | 2026-04-12 | DB=547MB, Files=143MB | OK | | staging | Weekly | 2026-04-12 | DB=254MB, Files=141MB | OK | | practice | Weekly | 2026-04-12 | DB=510MB, Files=183MB | OK | | crm | Weekly | 2026-04-12 | DB=36MB, Files=16MB | OK |

Updates applied: 3

Requested action: Review any items flagged above. Auto-updates have already been applied and verified.

2026-04-19

[ ] 03:45 ET | Daily Infrastructure Update Report

Added automatically by daily-infra-updates.sh on baseworks-agents VPS

Date: 2026-04-19

Backup health:

Site	Schedule	Last Success	Size	Status

| n8n | Daily | 2026-04-19 | 15MB | OK | | baseworks.com | Weekly | 2026-04-12 | DB=547MB, Files=143MB | OK | | staging | Weekly | 2026-04-12 | DB=254MB, Files=141MB | OK | | practice | Weekly | 2026-04-12 | DB=510MB, Files=183MB | OK | | crm | Weekly | 2026-04-12 | DB=36MB, Files=16MB | OK |

Updates applied: None

Requested action: Review any items flagged above. Auto-updates have already been applied and verified.

2026-04-20

[ ] 03:45 ET | Daily Infrastructure Update Report

Added automatically by daily-infra-updates.sh on baseworks-agents VPS

Date: 2026-04-20

Backup health:

Site	Schedule	Last Success	Size	Status

| n8n | Daily | 2026-04-20 | 15MB | OK | | baseworks.com | Weekly | 2026-04-19 | DB=548MB, Files=144MB | OK | | staging | Weekly | 2026-04-19 | DB=255MB, Files=141MB | OK | | practice | Weekly | 2026-04-19 | DB=513MB, Files=183MB | OK | | crm | Weekly | 2026-04-19 | DB=28MB, Files=16MB | OK |

Updates applied: None

Requested action: Review any items flagged above. Auto-updates have already been applied and verified.

2026-04-21

[ ] 03:45 ET | Daily Infrastructure Update Report

Added automatically by daily-infra-updates.sh on baseworks-agents VPS

Date: 2026-04-21

Claude Code updated: 2.1.114 (Claude Code) → 2.1.116 (Claude Code)
baseworks-agents system packages: 3 packages updated
baseworks-n8n system packages: 3 packages updated
n8n updated: 2.10.3 → 2.10.3 (health check: passed)

Backup health:

Site	Schedule	Last Success	Size	Status

| n8n | Daily | 2026-04-21 | 15MB | OK | | baseworks.com | Weekly | 2026-04-19 | DB=548MB, Files=144MB | OK | | staging | Weekly | 2026-04-19 | DB=255MB, Files=141MB | OK | | practice | Weekly | 2026-04-19 | DB=513MB, Files=183MB | OK | | crm | Weekly | 2026-04-19 | DB=28MB, Files=16MB | OK |

Updates applied: 4

Requested action: Review any items flagged above. Auto-updates have already been applied and verified.

Completed

2026-04-09

CSS icon backslash issue — RESOLVED same session

2026-03-25

Blog Feedback Workflow Optimization — responded with tooling fix: AI Generation Warning in unified guide, WRITING-PROCESS.md, updated skills. Asia’s inbox updated with full explanation.

Voice guide v1.9 — Ksenia’s “Baseworks Practice” lowercase expansion confirmed by Patrick

Blog Post Feedback — “From Three Forms to Twenty-One” — all 10 points reviewed and applied

2026-03-19

baseworks-changelog repo — branch divergence merged, master deleted, all repos standardized on main

2026-03-17

KB deploy failures — Cloudflare timeouts and GitHub auth errors

Daily Infrastructure Update Report

Daily Infrastructure Update Report

Daily Infrastructure Update Report

Daily Infrastructure Update Report

2026-03-13

Stale cache monitor deployed — running every 30 min

Daily Infrastructure Update Report

2026-03-12

QMD no_embed exclusion — done on Mac + VPS

New marketing folder — Meta Ads reference note

Daily Infrastructure Update Report (2026-03-12)

Daily Infrastructure Update Report (2026-03-11)

Quebec compliance — Study Group + Practice Sessions proposal

2026-03-11

Daily Infrastructure Update Report

2026-03-10

Daily Infrastructure Update Report (2026-03-10)

Daily Infrastructure Update Report (2026-03-07) — FileBrowser fix

Spring Study Group page — Asia’s edits reviewed

Practice Sessions event widget links confirmed

Daily Infrastructure Update Report (2026-03-08)

Daily Infrastructure Update Report (2026-03-06)

Practice Sessions page — taken over in Elementor

2026-03-09

Fathom Analytics in Privacy Policy — confirm still in use

2026-03-05

Session 7 Summary: Asia’s responses to verification items

Daily Infrastructure Update Report

Session 7 Summary (EN): Ready for review

Inbox notification test

SAIFA acronym: confirm for general use?

Inbox check system — for your CLAUDE.md

Patrick's Inbox

Open Items

[ ] 2026-04-20 | Form 67 → FluentCRM custom-field sync complete

What was done

Useful capability to know about

Related

[ ] 2026-04-19 14:00 ET | Session 3 Summary — Round 1 revision complete, ready for your review

[ ] 2026-04-17 12:00 ET | WPRUS security fix deployed — admin accounts now properly protected + username decision needed

What happened

What was fixed

One decision needed from you — username alignment

Where to find the full record

[ ] 2026-04-17 11:30 ET | Asia’s comments on People Profiles Aggregation Plan — review requested

[ ] 2026-04-17 | Bot registrations on baseworks.com — CAPTCHA plugin installed, needs Cloudflare API setup

[ ] 2026-04-17 09:49 ET | ✅ Done — questionnaire exports now emit user_login + new anti-drift rules in place

What was shipped

Anti-drift rules added (per your request)

Forks question (your earlier ask)

Scan result

Backups

Commits (main, baseworks-changelog)

Suggested next

[ ] 2026-04-13 22:20 ET | Community forums consolidation — paused mid-migration, resume tomorrow

[ ] 2026-04-13 09:27 ET | Add user_login to questionnaire export — enables forum @mentions in session summaries

What’s missing

Implementation idea (smallest viable change)

Edge cases to think about

Skill-side change (after the plugin is updated)

Suggested order of operations

Reference

[ ] 2026-04-10 | Proprioceptive Awareness campaign — social posts live, your Facebook post pending

[ ] 2026-04-10 12:00 ET | ImageMagick stroke-state bug — consider adding to carousel skill

[ ] 2026-04-10 | Inbox cleanup agent deleted an open item — needs investigation

2026-04-09

[ ] 11:45 ET | Site updates: article tagline tag + Last Updated field implemented

1. Article tagline changed from H2 to styled P tag

2. ACF field article_last_updated implemented

2026-04-08

[ ] 03:45 ET | Daily Infrastructure Update Report

[ ] 2026-04-07 22:51 ET | Vault health: 149 broken wikilinks + 244 backtick path warnings — cleanup needed

Broken wikilinks (149 total)

Backtick path warnings (244 total)

Recommended approach

2026-04-07

[ ] 22:45 ET | Google Workspace CLI setup — wrong tool installed, needs clarification

[ ] 22:00 ET | Forum sync + moderation plan — Asia’s review complete, decisions needed

[ ] 21:35 ET | Next session: instruction consolidation audit across CLAUDE.md, READMEs, skills, and shared context

[ ] 13:30 ET | Vault infrastructure optimization — session summary

[ ] 03:45 ET | Daily Infrastructure Update Report

[ ] 2026-04-06 12:30 ET | Pracstage staging checklist updated — Automator throttling + post-push cleanup

What we confirmed

What was updated

[ ] 2026-04-06 11:00 ET | CRM site: SQL injection probe detected and blocked

2026-04-06

[ ] 03:45 ET | Daily Infrastructure Update Report

[ ] 2026-04-05 21:30 ET | Karpathy Auto-Research Pattern — Explore for Baseworks

[ ] 2026-04-05 12:00 ET | Session 1 review complete — Asia’s feedback and action items

[ ] 2026-04-05 11:00 ET | Voice guide draft — Established Teaching Vocabulary (needs your confirmation)

2026-04-05

[ ] 03:45 ET | Daily Infrastructure Update Report

[ ] 2026-04-05 | New feature: lesson title auto-tagged on discussion creation

2026-04-04

[ ] 03:45 ET | Daily Infrastructure Update Report

2026-04-03

[ ] 03:45 ET | Daily Infrastructure Update Report

[ ] 2026-04-03 22:45 ET | Primer assignments widget configured for Spring 2026 group (group 5)

[ ] 2026-04-03 22:30 ET | Background tab — redirect guard + form ID fixed (v1.3.0)

[ ] 2026-04-02 23:30 ET | Auto-syncing iCal files — explore dynamic .ics generation

[ ] 2026-04-02 11:45 ET | upcoming_event_filter snippet — glitch explained, now resolved

2026-04-02

[ ] 03:45 ET | Daily Infrastructure Update Report

[ ] 2026-04-02 00:30 ET | Resume: Calendar setup + Preparation Guide page + Welcome email

[ ] 2026-04-01 22:55 ET | Questionnaire system deployed — Phase 2 plan

Remaining items for you:

Phase 2 plan:

2026-04-01

[ ] 03:45 ET | Daily Infrastructure Update Report

[ ] 2026-03-31 | “Mystery of Proprioceptive Awareness” — Japanese translation needs updating

[ ] 2026-03-31 23:30 ET | Open a session in baseworks-changelog to investigate forum auto-tagging from Primer lessons

[ ] 2026-03-30 20:40 ET | New inquiry: James Murray — Spring Cohort (Session 2 logistics)

[ ] 2026-04-17 09:49 ET | ✅ Done — questionnaire exports now emit `user_login` + new anti-drift rules in place

Commits (main, `baseworks-changelog`)

[ ] 2026-04-13 09:27 ET | Add `user_login` to questionnaire export — enables forum @mentions in session summaries

2. ACF field `article_last_updated` implemented