ticket_id: "tkt_pmem_project_scoped_writes" title: "Project memory writes consistently target the configured project namespace" agent: "codex" done: false goal: "Durable project knowledge is written under one stable project namespace instead of leaking into global memory."

Tasks

Set one stable project slug and use that exact value everywhere for this integration.
Update the project memory write flow so durable repo facts are written with scope: "project" and project: "<stable-project-slug>".
Ensure project memory writes use the categories called out in the source: project, instruction, fact, or note.
Ensure project memory writes include useful tags.

A single stable project slug is defined for the integration and used consistently.
Durable project memory writes target project scope for that slug.
The write flow supports the source categories and tags for project memories.

Create a manual durable memory for the configured project and verify it is stored under project scope for the configured slug.
Retrieve memories for the configured project and verify the created entry appears there rather than only as global memory.

Source: "Set one stable project slug", "Force all project writes into project scope", and use scope: "project" with project: "socratic-orchestrator".
Constraints:
- Do not invent automatic repo crawling behavior.
- Prefer distilled reusable facts over raw text when storing project knowledge.
Evidence:
- The source states the plugin supports global, project, and session scopes.
- The source states the Remember tool already supports scope="project" and requires a project name.
Dependencies: Not provided
Unknowns:
- Exact configured project slug to use outside the example socratic-orchestrator.