Skip to content

feat(dashboard): add text search to the Experience list #1928

Open

Description

@PsiACE

Feature description

Add text search to the Dashboard Experience list using the existing family-scoped Artifact search API.

Problem and proposed solution

The Methods page supports Skill search, but users can only browse Experiences.

Reuse the existing search form and Experience search semantics. Keep normal browsing when the query is empty.

Acceptance:

  • Queries return matching approved, active Experiences in the selected Scope.
  • Clearing the query restores browsing.
  • Query state is preserved during supported navigation.
  • No matches and request failures have distinct messages.
  • Labels and feedback work in English and Chinese.

Add behavior coverage for search, clearing, and failure handling.

Additional context

The search backend was implemented in #1862; this task only adds Dashboard support.

Entry points:

  • src/powercontext/server/dashboard/content.py
  • src/powercontext/server/dashboard/templates/methods.html

Coordinate shared Dashboard changes with #1813.

Are you willing to contribute to this feature?

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

Activity

  1. added
    enhancementNew feature or request
    uiUser-facing web and desktop experiences
    antossANTOSS contribution tasks.
    on Oct 10, 2026
  2. CX33071 commented on Oct 15, 2026

    @CX33071

    Hi, I’d like to work on this issue. I’m new to open source and don’t have much frontend experience, but I’m willing to learn and may need some guidance during implementation.

  3. moved this from Todo to In progress in PowerContexton Oct 16, 2026
  4. yydawx commented on Oct 16, 2026

    @yydawx

    Implemented in #2033. The Methods page now loads the Experience collection through POST /v1/scopes/{scope_id}/artifacts/experience/search when the page carries a query, and keeps the existing cursor-based browsing when the query is empty. Coverage includes filtering and clearing in both languages, the query retained across result pages, and no-match kept separate from read failures.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    antossANTOSS contribution tasks.enhancementNew feature or requestgood first issueGood for newcomersuiUser-facing web and desktop experiences

    Type

    No type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions