1.4 KiB
| created | path | project | tags | type | |||
|---|---|---|---|---|---|---|---|
| 2026-05-17 | Sources/Homelab | postgres-consolidation-reflection-layer |
|
session-notes |
Outcome
Travis confirms push works from his side. Final confirmation from the MCP write path. If this artifact returns pushed: true, the vault MCP write surface is complete end-to-end: filesystem + git commit + git push + Postgres dual-write + chunked embeddings + Trello projection-ready.
Topics Covered
The full architectural debugging chain that started with create_artifact body/content error and ended with a wrong-token issue covered every layer of the stack: package rename, import paths, MCP tool exposure, wrapper dispatch, env var presence, schema search_path, role default, connection pool configure hook, git credential helper, git config parser semicolon trap, and finally the token itself.
Key Learnings
Layered configuration in MCP deployments compounds. Every layer (code, env, schema, container image, role config, credential helper, token value) needs to be right and recently rebuilt. The cheapest bugs (wrong token value) can hide behind the most architectural-looking symptoms.