Skip to content
FSS Knowledge Base

web-deploy-sdc-focus — Session Log

Section titled “web-deploy-sdc-focus — Session Log”

What changed:

  1. KB deploy stale-content bug, root-caused and fixed. Two Core/Misc/Clippings/*.md notes had a duplicate rating: frontmatter key (a stale letter grade left after /triage-inbox wrote the numeric score under the same key), and Routines.md had an unquoted colon inside last-updated: — all three invalid YAML. js-yaml rejected them during Astro’s content sync, so every Cloudflare Pages build for kb-online-site had been failing silently since 2026-07-13 — git kept accepting pushes, but production never advanced past that commit. Fixed at the vault source, verified a clean local build (1131 pages), pushed (kb-business commit 80fc906), polled the Cloudflare deployment through build+deploy success, confirmed kb-online-site.pages.dev/sdc/strategy/strategic-plan/ serves “Strategic Plan v2.0” live.
  2. KB SDC split into its own standalone Cloudflare Pages project, not a rename/overwrite of kb-mbr. Business focus moved MBR → SDC; first pass retargeted kb-mbr’s pipeline in place, but Talbot’s later reply (“leave as is, add new kb-sdc project”) reversed that — kb-mbr was restored via fresh clone (untouched, still live serving MBR), and kb-sdc was detached from kb-mbr’s git remote and rebuilt as a standalone project: astro.config.mjs/package.json/README.md retargeted, deploy.sh rewritten to deploy directly via wrangler pages deploy (no GitHub remote to push to — same pattern as ts-site/sdc-site). Talbot ran the actual wrangler pages project create + deploy himself (classifier-blocked from running autonomously — new production infra); confirmed live: kb-sdc.pages.dev returns 200, “SDC Knowledge Base”, 291 files.
  3. New sdc-site config.yaml project (monorepo/sites/sdc, port 4327) + deploy.sh modeled on ts-site/mbr-site’s wrangler pattern. Not yet deployed to Cloudflare for real (optional, no rush) — local build verified only (127 pages, / and /focus.html both 200).
  4. Deploy menu reordered twice per Talbot’s evolving asks — final order: a KB, b KB SDC, c KB MBR, d Template, e TS site, f SDC site, g mBR site, h SDC Focus, i mBR Focus, j Accounting. Confirmed menu lettering is config.yaml key-insertion order (web_deploy.py:910), no code change needed for reordering.
  5. Removed a stray PowerShell startup banner (C:\Users\Admin\Documents\WindowsPowerShell\Microsoft.PowerShell_profile.ps1 — global shell profile, unrelated to web-deploy code) that printed ”==> Warp AI Terminal Ready” / “Navigation: …” before every web-deploy menu.

Commits: kb-business 80fc906 (frontmatter fix) · kb-mbr fresh-cloned (no new commits, restored to origin/main) · kb-sdc 7712d1a→2865729 (local history only, no remote) · web-deploy 15de7a6, 8651612 (config.yaml + .gitignore).

Gotcha (see web-deploy/LESSONS.md Lesson 10): Cloudflare build failures are invisible from deploy.sh — it prints “Push complete!” on a successful git push regardless of whether the actual Cloudflare build succeeds. This is the third confirmed recurrence of the same class of bug (2026-06-26 head: collision, 2026-07-13 unrecorded cause, this task). The 2026-06-26 fix was advisory-only (“check the dashboard”) and never stuck. Not fixed this round — flagged as a real gap in kb-business/kb-mbr’s deploy.sh for whoever next touches them: add a post-push Cloudflare API poll that fails loudly on build failure.

Terminal: all 4 original ## Tasks items + Success Criteria met. No successor — the one optional item (a real sdc-site deploy) is no-rush and doesn’t warrant a dedicated task.