feat(web): add a read-only Memory entry viewer

Feature description

Add a small, read-only Memory viewer to the web console so users can inspect an individual Memory entry without using the CLI or raw HTTP API.

This is a focused first step toward the broader web-console management UI in #1341 and should also provide a reusable web workflow for the desktop control center tracked in #1428.

Problem and proposed solution

The current Dashboard shows only aggregate Memory counts. The Server API already exposes POST /v1/memory/entries/list and POST /v1/memory/entries/get, but there is no web page that lets a user view the actual content of a Memory entry.

Add a read-only Memory page or panel that:

1. uses the existing Dashboard authentication and Scope selection;
2. lists active Memory entries for the selected Scope;
3. lets the user select an entry;
4. displays its text, kind, state, version, and citation;
5. handles loading, empty, authentication, and error states clearly.

The implementation should use the existing server-rendered Jinja + vanilla ES module stack and the public HTTP API contract. It must not add editing, retiring, search, pagination, or desktop-specific behavior in this first slice.

Acceptance criteria

• A user can open the Memory view from the existing web console navigation.
• The view follows the selected Scope and existing authentication behavior.
• Active Memory entries are loaded through the existing API and shown in a readable list.
• Selecting an entry shows its complete current content and citation metadata.
• Empty, loading, unauthorized, unavailable, and malformed-response states are handled with actionable UI messages.
• English and Chinese translations, keyboard navigation, and basic responsive layout are included.
• Existing Dashboard and Handoff Report behavior does not regress.
• Tests cover the route, API integration behavior, and the main UI states.

Out of scope

• Memory search
• Revise or retire actions
• Revision history and change audit timeline
• Artifact or Candidate management
• New API endpoints or database changes
• Native desktop implementation

Related issues

• #1341 — expand web console with memory and artifact management
• #1428 — deliver a secure PowerContext desktop control center

Contribution

• I am willing to contribute code, docs, or design feedback.