fix(brain): remediate hive privacy findings

[djm204]

Summary

• preserve stable Hive publisher ownership across durable brain restarts so right-to-forget can revoke previously published rows
• revoke revised, rejected, episodically forgotten, and never-store lesson publications precisely while securely purging deleted SQLite payloads
• keep encrypted brains able to read peer lessons without publishing local plaintext, and enforce the Hive confidence floor on approval

Verification

• npm test --workspace @franken/brain — 486/486 passed
• npm run typecheck --workspace @franken/brain — passed
• npm run lint --workspace @franken/brain — passed
• npm run build --workspace @franken/brain — passed
• npm run lint — passed
• root npm test has 3 pre-existing franken-orchestrator failures unrelated to this diff
• root npm run typecheck and npm run build remain blocked by pre-existing franken-web errors

Remediation chain

Follow-up to merged PR #3775 for issue #3689. This consolidates fixes for the seven unresolved Codex review findings on the merged head, including right-to-forget and secure-deletion defects.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 20d0e9c7a2

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[djm204]

@codex review

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: ec1367b5bf

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".