chore: commit after each task and run graphify update at session end

Co-authored-by: Cursor <cursoragent@cursor.com>
This commit is contained in:
john kevin asprec
2026-09-04 07:36:03 +08:00
parent 03ad49f523
commit e87fddc707
11 changed files with 62 additions and 9 deletions

View File

@@ -22,6 +22,16 @@ Add an entry when a choice is hard to reverse, shapes future work, or a future m
## Log
### D-2026-09-04-01 — Commit each landed task; graphify update at session end
- **Status:** accepted
- **Context:** Graph and git lagged behind work (SEO sat uncommitted; graph needed a manual deep rebuild).
- **Decision:** After every completed task, commit landed files (never secrets or `graphify-out/`). Do not push unless asked. At session end, run `graphify update .`.
- **Alternatives considered:** Commit only when asked (lost work); full `/graphify --mode deep` every session (too expensive).
- **Consequences:** More small commits on `dev`. Graph stays AST-current; docs/images still need an occasional deep extract.
- **Verification:** Session-start hook reminds the workflow; `graphify-out/` stays gitignored.
- **Owner / date:** John Kevin, 2026-09-04
### D-2026-09-03-01 — Website path URLs for Google indexing
- **Status:** accepted

View File

@@ -4,6 +4,7 @@
## Current state
- **Outcome:** Sitemap accepted in GSC. SEO pass: intent titles, home FAQ + FAQPage JSON-LD, breadcrumbs, lastmod sitemap, 5-min cache on robots/sitemap.
- **Verified:** `website:typecheck` + `website:build` OK (inject wrote route HTML + sitemap.xml).
- **Next smallest action:** Merge/deploy this to `main`, purge Cloudflare `/robots.txt`, then in GSC request indexing for `/` and `/docs`.
- **Outcome:** Standing workflow: commit after each landed task; session end `graphify update .`.
- **Shipped:** `AGENTS.md` / `CLAUDE.md` lessons + state continuity; `.cursor/rules/graphify.mdc`; session-start reminder; `D-2026-09-04-01`.
- **Verified:** docs/rules updated; graphify-out gitignored.
- **Next smallest action:** Continue product work; this session will commit this change and run `graphify update .`.

View File

@@ -6,6 +6,16 @@ This is the project’s shared, evidence-backed memory of mistakes worth prevent
`AGENTS.md` → `## Lessons` is the canonical active rule list loaded every session. Keep supporting evidence here; mirror an active rule here only when its detail is useful for maintenance. Keep at most 12 active rules, each short and imperative.
### L-2026-09-04-01 — Commit each landed task; session end `graphify update .`
- **Status:** active
- **Trigger:** Owner asked to stop leaving finished work uncommitted and the knowledge graph stale.
- **Root cause / failure boundary:** Commit-on-request plus no session-end graph refresh.
- **Prevention:** Commit after each landed task (no secrets). Session end: `graphify update .`.
- **Evidence:** Owner instruction 2026-09-04; graphify CLI `update`.
- **Eval:** manual guardrail — git status + graphify-out mtime
- **Owner / review:** lead / if auto-commit becomes noisy
### L-2026-08-17-01 — Serve website `dist/` on `0.0.0.0:$PORT`; do not use Vite preview in production
- **Status:** active

View File

@@ -18,6 +18,7 @@
- Prefer encrypted Chrome key path; keep plaintext `apiKey` fallback until migration.
- VS Code / CLI must not import `@lib/crypto` or `@lib/messaging`.
- Root scripts: `install:all`, `chrome:*`, `vscode:*`, `cli:*`, `website:*`.
- After each landed task: git commit (no secrets; `graphify-out/` ignored). Session end: `graphify update .`. Do not push unless asked.
## Environment quirks

View File

@@ -2,7 +2,7 @@
> For the owner. What works, how to see it, and what's waiting on you — plain language.
**Updated:** 2026-09-04 · **Overall:** Search Console sitemap is success; next deploy the SEO copy/FAQ pass
**Updated:** 2026-09-04 · **Overall:** Search Console is live; agents now commit after each task and refresh the code graph at session end
## What works now