feat(dashboard): profile reading and exact handoff Markdown export - #1630
Merged
Merged
Conversation
Zxf-xufeng
marked this pull request as ready for review
September 17, 2026 09:55
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Which issue or RFC does this PR close?
Implements the proposal in #1629. Both branches start independently from master at
534460e068ef733ec22a672b838734635fa1677e.Rationale for this change
Dashboard already has Prompts and Topic Memory. Users still need to read saved Profiles and export the precise Handoff revision they are viewing, including after a newer revision is committed.
What changes are included in this PR?
markdown-it-pydependency in the server extra.Are there any user-facing changes?
Profile appears in Dashboard navigation. Handoff entries and details expose Export Markdown. Existing Prompt and Topic Memory pages, public
/v1contracts, persisted schemas, and Handoff Report selection/digest behavior remain compatible. Dashboard stays opt-in under its existing static-token configuration.How was this change tested?
Tests used temporary databases and an isolated
POWERCONTEXT_HOMEwith inherited service settings cleared.make checkand finaluv run prek run -a.tests/e2e/test_access_control_http.pyandtests/e2e/test_profile_api.py.python -m pytest -q tests/test_dashboard.py tests/test_dashboard_profile_handoff.py tests/test_dashboard_markdown.py— 37 passed.make docs-test— verified 806 exported public pages.scripts/dashboard_browser.cjsagainst an isolated running server — 24 scope-page visits and 9 responsive page types, actual attachment downloads, exact post-login return, source reading, navigation, locales, and themes.The paginated Handoff return test supplies a two-page collection response while retaining real exact-record reads and authorization, because new Handoff writes use the current singleton identity. Browser acceptance exercises the real collection available in the test server.
AI usage statement
Implemented and validated with OpenAI Codex, including code, documentation, regression tests, and browser automation. Maintainer review is requested through this draft PR.