fix(mcp): require confirmation before forgetting similar memories

[DisturbedCrow]

Stops forget from immediately deleting a semantic near-match. It now previews the candidate and requires a short-lived signed confirmation.

Focused tests and the Worker dry-run build pass.

[graphite-app]

The rule 'Avoid unnecessary type assertions' and 'Use type annotations instead of assertions for object literals' is violated here. The code uses as Record<string, unknown> to cast the result of JSON.parse(...). While JSON.parse returns any, the preferred approach is to use a type annotation on the variable rather than a type assertion:

const confirmation: Record<string, unknown> = JSON.parse(
  textDecoder.decode(this.fromBase64Url(payload)),
)

Suggested change

	const confirmation = JSON.parse(
	textDecoder.decode(this.fromBase64Url(payload)),
	) as Record<string, unknown>
	const confirmation: Record<string, unknown> = JSON.parse(
	textDecoder.decode(this.fromBase64Url(payload)),
	)

Spotted by Graphite (based on custom rule: TypeScript style guide (Google))



Is this helpful? React 👍 or 👎 to let us know.

[graphite-app]

The rule 'Use type annotations instead of assertions for object literals' is violated. The code uses as { documentId?: string } as a type assertion on the result of created.json(). Instead, a type annotation should be used:

const body: { documentId?: string } = await created.json()
documentId = body.documentId

Suggested change

	documentId = ((await created.json()) as { documentId?: string })
	.documentId
	const body: { documentId?: string } = await created.json()
	documentId = body.documentId

Spotted by Graphite (based on custom rule: TypeScript style guide (Google))



Is this helpful? React 👍 or 👎 to let us know.