Operations Memory

Operations and Claude memory

Back to Home. Related: Deployment-and-Security, Development-Workflow.

This page indexes durable knowledge found in Claude's per-project memory at ~/.claude/projects/-Users-Workspaces-acm-altinity-sql-browser/memory/. That directory remains the detailed source; this wiki records the actionable map.

Development and verification

• bash-grep-intercepted: prefer rg; old Claude shell hooks made piped grep unreliable.
• playwright-e2e-ci-only: full Playwright engines may not launch locally; CI is authoritative for the three-browser gate.
• e2e-harness-bare-imports: raw-ESM harnesses need import maps for bundled deps.
• extraction-drops-perfile-coverage: extraction can reveal previously hidden uncovered functions; inspect lcov FN/FNDA rather than weakening the gate.
• local-ui-harness-verify: a throwaway import-map harness can verify UI without ClickHouse; screenshots must stay inside the workspace.
• node25-localstorage-test-flake: the historical Node 25 flake was fixed; treat new failures as regressions.
• ui-snapshot-capture: the canonical 30-shot review set is specified by docs/ui-snapshots/CAPTURE-SPEC.md.
• safari-zoom-divergence and scrollbar-zoom-resolution: real Safari differs from Chromium/Playwright WebKit for CSS zoom; runtime viewport calibration is intentional and standard scrollbar styling caused regressions.
• safari-mcp-selenium-setup: real-Safari testing uses the selenium-safari MCP, which only binds in a fresh Claude session (needs ~/.claude.json entry, warm npx cache, safaridriver --enable); Chrome/Firefox MCPs load normally.

Shipping and planning

• forward-work-tracking-model: roadmap #68 and GitHub issues own forward work; docs/ is public, not an internal tracker.
• ship-branch-off-diverged-main: branch from origin/main when local main has diverged rather than destructively reconciling it.
• ship-background-finalization and ship-phase-run-learnings: concurrent ship agents can mutate git state; use isolated worktrees, explicit read-only review boundaries, and verify diff/log/PR state after every batch.
• editor-roadmap: CM6/EditorPort migration is settled; no SQL on keystrokes and no second UI framework.
• dashboard-epic-phase-numbering-and-filter-design: records the current typed parameter, optional-block, panel registry, and dashboard issue dependencies.

ClickHouse and demos

• deploy-sql-browser-demo-clusters: upload built HTML into user_files; known demo paths differ by cluster.
• deploy-mechanics-acm-settings: apply managed config.d through ACM settings, not Kubernetes ConfigMaps.
• acmctl-gotchas-and-instability: bodyless raw calls historically required closed stdin; delete-only pushes can be lazy until a real change occurs.
• cl-wrapper-stdin: feed local SQL to ~/bin/cl <cluster> through stdin; a local --queries-file path does not exist inside the pod.
• clickhouse-param-path-grammar: live 26.3 grammar probes are the basis for parameter serialization; consult the full memory before parser changes.
• clickhouse-datalake-catalog-hidden-from-system-tables: catalog tables need show_data_lake_catalogs_in_system_tables = 1.
• library-demo-generator-gotchas: documents client parameter binding, schema key extraction, permissions, and browser upload traps.
• github-demo-sql-browser-and-backup-landmine: a revoked backup S3 key can make ClickHouse restart fail; inspect this memory before operating github.demo.
• antalya-two-idp-bearer-plus-basic: the two-IdP experiment was reverted to Google-only, but its username-collision lesson remains valid.
• antalya-oauth-demo-role-grants: demo privileges come through replicated roles; the shared role includes temporary-table creation for multiquery sessions.

Design source

sql-browser-design-source: the design/product source of truth is now DESIGN.md and PRODUCT.md at the repo root (committed on main). The former external Claude Design (DesignSync) project is deprecated and slated for deletion — do not use it as the spec.

Memory is historical and can stale. Re-verify live infrastructure and GitHub state before mutation, especially pages that include dates, versions, or cluster IDs.