fix(server): refuse memory writes for a workspace that does not exist (UF-039)

POST /api/memory/frames, /api/quick-capture and the Memory Center's
POST /api/memory saved a memory meant for an unknown workspace into
personal memory, which every workspace reads. They now answer 404
workspace_not_found and write nothing; a request without a workspace
still goes to personal memory.
This commit is contained in:
shumeiko.it
2026-10-24 18:09:43 +02:00
parent 4dbab2cb8b
commit 8a9ba09ad9
6 changed files with 61 additions and 10 deletions

View File

@@ -90,12 +90,16 @@ describe('Memory Center routes', () => {
expect(typeof mem.id).toBe('string');
});
it('POST /api/memory writes into a known workspace and falls back to personal for an unknown one', async () => {
it('POST /api/memory writes into a known workspace and refuses an unknown one (UF-039)', async () => {
const ws = await createMemory({ content: 'Alpha uses Postgres.', workspaceId: WS });
expect(ws).toMatchObject({ scope: 'workspace', workspaceId: WS });
const unknown = await createMemory({ content: 'Unknown workspace note.', workspaceId: 'nope' });
expect(unknown.scope).toBe('personal');
expect(unknown.workspaceId).toBeUndefined();
const unknown = await server.inject({
method: 'POST',
url: '/api/memory',
payload: { content: 'Unknown workspace note.', workspaceId: 'nope' },
});
expect(unknown.statusCode).toBe(404);
expect(await allMemories()).toHaveLength(1);
});
it('blocks unsafe create content, titles and tags without writing anything', async () => {