Add Hindsight integration evaluation and recommendation (docs)

[esafwan]

Motivation

• Provide a thorough architecture-level evaluation of integrating Hindsight as a long-term agent memory system with HUF and recommend a pragmatic integration path.
• Capture comparative analysis, risks, and a concrete Phase-1 implementation plan to guide engineers and product owners.

Description

• Add docs/HINDSIGHT_EVALUATION.md, a comprehensive 400+ line report that studies Hindsight, audits HUF's existing knowledge/memory architecture, compares capabilities, and recommends an integration approach.
• Recommend and detail Option B: embed Hindsight as an opt-in sidecar per agent, including identity mapping, API client hooks (retain/recall/reflect), runtime orchestration points (pre-response recall, post-turn retain, optional reflect), fail-open behavior, telemetry, and UI/agent config fields to add.
• Provide phased rollout plan (two-week Phase-1), architecture sketch, risk register, pilot success criteria, and example pseudocode for integration.
• Document migration/alternative options (knowledge-porting and full-replacement) and rationale for choosing the sidecar approach.

Relationship to scoped memory/data management

This PR should be read together with #274, which proposes the bridge between conversation data management, scoped Memory/Data Records, Knowledge Sources, Agno-style retrieval architecture, and Hindsight-style long-term memory.

In that combined model, Hindsight-style memory is the learning/consolidation half of the bridge:

Conversation / Tool Events / Agent Runs
        ↓
Hindsight-style retain/reflect pipeline
        ↓
Memory/Data Records or external memory bank
        ↓
Optional Knowledge Projection

This PR should not replace HUF Knowledge Sources. Instead, it should define how HUF can learn from repeated interactions over time through retain/recall/reflect while preserving Knowledge Sources as the curated/static/reference retrieval layer.

Related:

• docs: add scoped memory and knowledge bridge RFC #274 — scoped memory/data management and knowledge bridge RFC
• docs: RFC for adapting Agno's knowledge/vectordb architecture into HUF #178 — Agno-style knowledge/vector architecture RFC

Testing

This change is documentation-only and did not modify runtime code, so no automated code tests were required or executed for functional verification.

No unit/integration tests were run as part of this PR because the update only adds a design/evaluation document.

---

Codex Task