Skip to content

chore(issue-90): preserve graphiti artifact cleanup stash#107

Draft
hugocool wants to merge 2 commits into
mainfrom
issue/90-graphiti-neo4j-cutover
Draft

chore(issue-90): preserve graphiti artifact cleanup stash#107
hugocool wants to merge 2 commits into
mainfrom
issue/90-graphiti-neo4j-cutover

Conversation

@hugocool
Copy link
Copy Markdown
Owner

Linked issue

  • GitHub issue:
  • Issue branch:

Acceptance criteria

  • Criterion 1:
  • Criterion 2:
  • Criterion 3:

Notebook -> artifact mapping (required for notebook-driven work)

  • Primary notebook path:
  • Notebook lifecycle status (WIP / Extraction complete / DONE / Reference / Archived):
  • Extracted implementation files (src/...):
  • Extracted test files (tests/...):
  • Extracted docs (README.md / docs/...):
  • Intentionally retained notebook-only content (and why):

Verification performed

  • Start-of-work cleanliness check recorded (git status --porcelain)
  • Pre-PR-close cleanliness check recorded (git status --porcelain)
  • Relevant automated tests passed
  • Notebook checkpoint passed (clean-kernel rerun or CI notebook check)

Commands run:

# paste commands used for verification

System-of-record sync

  • Issue status updated
  • PR description reflects current implementation status
  • Temporary /tickets/ markdown removed or explicitly retained as durable documentation

- Added a new implementation plan for aligning VS Code Slack bot debug configurations with the Graphiti+Neo4j stack.
- Created a new Docker Compose file to define the necessary services including `calendar-mcp`, `neo4j`, and `graphiti-mcp`.
- Introduced a script to manage the local debug infrastructure for the Slack bot.
- Developed a new module for shared durable constraint memory contract.
- Added VS Code tasks for starting the development server.
- Implemented unit tests for the Graphiti constraint memory client and the VS Code debug stack.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant