sync: auto-sync from GURU-5070 at 2026-06-15 09:41:53

Author: Mike Swanson
Machine: GURU-5070
Timestamp: 2026-06-15 09:41:53

projects/acg-website-showcase/session-logs/2026-06/2026-06-14-mike-acg-website-multi-skin-build.md

@@ -213,3 +213,53 @@ still computes $952/mo; `node --check js/app.js` clean.
 State: multipage 4-skin switcher (Paper / Midnight / Verdigris / Bold) at :4328, all in
 light+dark. Bold is the dialed-back-then-premium-softened radical. Open: Mike to confirm
 Bold is the keeper, or pick among the four skins for the real azcomputerguru.com redesign.
+
+## Update: 09:41 PT (2026-06-15) — logo mark, errorlog skill fixes, Graphifyy eval
+
+Three workstreams after the Bold-skin softening.
+
+**1. Official ACG logo (partial).** Mike supplied the official wordmark ("Arizona ComputerGuru",
+the "G" = an askew power symbol) and noted the short logo is just that stylized G. Hand-built the
+short mark as a faithful SVG (`multipage/assets/logo/acg-mark.svg`, askew power symbol), wired it
+as the header brand mark (tints to each skin's accent via currentColor) + favicon across all 6
+multipage pages + radical.html. NOT done: the full wordmark — it's an exact brand asset with
+custom type; can't save Mike's pasted raster from here and AI-recreation would be off-brand, so
+the real file needs to be dropped into `multipage/assets/logo/` (color + a white/knockout for dark
+skins). Open design choice for Mike: official fixed wordmark sitewide vs. keep the per-skin
+adaptive lockup.
+
+**2. errorlog review -> skill hardening.** 4 entries: #2 (py-on-Linux) + #3 ($CLAUDETOOLS_ROOT)
+already resolved on this machine; #4 (sync.sh submodule abort) fixed upstream by the GURU-BEAST-ROG
+coord broadcast (resolve_submodule_collisions; lands on next pull here). #1 (mailbox/FABB) was the
+open one: app `fabb3421` is DELETED (AADSTS700016), and it held the only Mail.Send/ReadWrite/
+Contacts scopes -> `/mailbox` + M365 contacts blocked, and the 3 legacy "old app only" tenants
+(Valleywide/Dataforth/Cascades) now have NO working remediation app. Hardened the docs:
+`gotchas.md` (DELETED + blast radius + URGENT migration), `mailbox.md` (BLOCKED/AADSTS700016
+banner), `errorlog.md`. **Mike's decision:** Mail.Send belongs in the SUITE (real use = IR
+victim-notification during box takeovers) -> add Mail.Send to the **Exchange Operator** tier;
+implementation NOT executed (production multi-tenant app change, needs go + admin-consent). Also
+surfaced 2 stale for-mike.md items: Intune Manager needs signInAudience->AzureADMultipleOrgs PATCH
+(unblocks Cascades MDM); Mike's per-user Syncro key.
+
+**3. Graphifyy vs GrepAI evaluation (`projects/graphifyy-eval/`).** Question: adopt Graphifyy
+(getzep-style code+doc knowledge graph, `safishamsi/graphify`, PyPI `graphifyy`) for day-to-day?
+Built a 3-arm protocol (A=GrepAI, B=Graphifyy, C=control) with a 10-query test set + rubric.
+- Arm A (GrepAI): 18/20, ~3k ctx tokens/query, already indexed. 2 misses: phrasing-sensitivity
+  (C1) and stale-duplicate retrieval (D2 pulled superseded kittle-design).
+- Arm B (Graphifyy): code extraction = AST (instant/free/local, but redundant with GrepAI).
+  Doc/non-code = generative LLM per chunk. Local ollama (apples-to-apples, since GrepAI uses
+  ollama embeddings) was IMPRACTICAL: qwen3:8b DNF 20 files/10min ("too small for JSON"),
+  codestral:22b got 1 of 2 chunks on 3 files/6min. Claude backend (vault gururmm anthropic key,
+  ~$0.20 real spend) WORKED: 3 docs in 120s, but graphify reported ~$0.068/doc (recurring on an
+  active repo), and the decisive finding: `graphify query` returns the concept/relationship MAP,
+  NOT the content values (the prices were absent) -> you still Read the file for facts. GrepAI
+  returns content directly.
+- **Verdict: keep GrepAI, do not adopt Graphifyy.** Cheap part duplicates GrepAI; unique part
+  (doc/relationship graph) is impractical local / costs recurring $ cloud / hands a map not facts.
+  Revisit only with GPU+fast local generative model, or a recurring architecture-relationship
+  need worth a metered ingest budget. Full writeup: `projects/graphifyy-eval/FINDINGS.md`.
+- Cleanup done: GrepAI re-enabled in settings.local.json; graphifyy + openai uninstalled
+  (anthropic kept); scratch graphs deleted; PROTOCOL/results/FINDINGS retained.
+
+Note: untracked discord-dm skill/command/scripts + 2 feedback memories present in the tree are
+fleet additions (not this session's work); auto-sync sweeps them.