Repository navigation
feat(dashboard): explain processing and always capture recall diagnostics - #2664
happy-v587 wants to merge 15 commits into
Conversation
… stages Remove the context diagnostics switch so the Server always writes the prepare diagnostic store, and rework the detail page: - group exact selected references by family - show each stage duration in its heading and drop the stage table - keep only Receipt-selected candidates in the assembly text column - report the retrieval-stage count from the same-execution snapshot - move the Receipt ID into the query card footer - explain that the byte budget counts UTF-8 bytes, not characters - clarify omission wording and drop the placeholder count for not_retrieved Sync en/zh docs and RFC 1435.
Revision v1_5_0_007 only added pc_context_prepare_diagnostics.query_text, and both revisions are unmerged. Fold the column into the v1_5_0_006 create statement so the diagnostic store is one additive revision. Delete the v1_5_0_007 schemas, scripts and state layouts, refresh the manifest, the MySQL history and the release upgrade-support digest, and update the tests that asserted the removed revision.
…-diagnostics # Conflicts: # release/upgrade-support.json # tests/native/test_oceanbase_engine_recovery.py # tests/native/test_personal_service_lifecycle.py
a3e9309 to
28745f6
Compare
…-diagnostics # Conflicts: # docs/en/docs/operate/database-migrations.md # docs/zh/docs/operate/database-migrations.md # release/upgrade-support.json
hidb4ai
left a comment
There was a problem hiding this comment.
One non-blocking design note on the retention policy; this is not a request for changes.
PR oceanbase#2674 registers the same v1_5_0_006 ID and adds identically named migration files; two linear chains cannot share a revision ID. Renumber the prepare diagnostics revision, its schema resources, manifest registrations, docs and target-revision assertions, and refresh the compatibility review digest. Co-Authored-By: Claude Code <noreply@anthropic.com>
|
The renumbered revision run (44080115039) completed with one failure: |
…-diagnostics # Conflicts: # docs/en/docs/operate/database-migrations.md # docs/zh/docs/operate/database-migrations.md # release/upgrade-support.json
|
Follow-up on run 44101725008: |
…-diagnostics # Conflicts: # release/upgrade-support.json
|
Follow-up on run 44136372151: |
|
Root cause found for the |
hireview001
left a comment
There was a problem hiding this comment.
- CI failed: CI result (failure).
- CI failed: dsh-package (failure).
- CI failed: Main (failure). Failed steps: dsh-package / Test DSH package; CI result / Require successful selected checks.
The fixed five-family list in selected_by_family, final_candidates and the assembly text snapshots dropped plugin-family selections (for example a 'notes' section), so the Dashboard budget table omitted a family the Receipt cited. Seed the family counts with the requested plugin sections, count their hits in final_candidates, and capture their same-execution assembly text snapshot. Co-Authored-By: Claude Code <noreply@anthropic.com>
…-diagnostics # Conflicts: # release/upgrade-support.json
|
The old queued CI run was cancelled while migrating eligible Linux checks to the internal runner pools in #2711. At head
Please sync the branch with master, resolve the conflicts, and push the update. GitHub cannot start a new |
…-diagnostics # Conflicts: # docs/en/docs/operate/database-migrations.md # docs/en/docs/operate/troubleshoot.md # docs/zh/docs/operate/database-migrations.md # docs/zh/docs/operate/troubleshoot.md # release/upgrade-support.json # src/powercontext/builtin/persistence/migrations/server_resources/manifest.json # src/powercontext/builtin/persistence/migrations/server_sources/1.4.0/manifest.json # tests/builtin/persistence/test_atomic_description_vector_layout.py # tests/builtin/persistence/test_atomic_evidence_upgrade_history.py # tests/builtin/persistence/test_full_server_migrations.py # tests/builtin/persistence/test_mysql_initialization_preflight.py # tests/builtin/persistence/test_mysql_migration_runner.py # tests/builtin/persistence/test_plugin_storage_migration.py # tests/builtin/persistence/test_portable_storage_migration.py # tests/builtin/persistence/test_release140_server_migrations.py # tests/e2e/test_atomic_memory_description_upgrade.py # tests/e2e/test_source_citation_locators.py # tests/e2e/test_source_write.py # tests/native/test_oceanbase_engine_recovery.py # tests/native/test_personal_service_lifecycle.py # tests/test_managed_atomic_maintenance.py # tests/test_managed_processing_maintenance.py # tests/test_migration_revision_names.py # tests/test_registered_source_maintenance_cli.py
|
Re-review of 2cee427: the previous migration-chain issue is fixed against current master: the tail is v1_5_0_005 -> v1_5_2_pr2639 -> v1_5_0_007, with a single head. The migration upgrade and plugin-family capture regressions pass locally, and the persistence review digest matches. No new blocking correctness finding from this incremental review. CI is still a merge-readiness blocker: run 44279936034 timed out in CI preflight / Check License Header ( |


Which issue or RFC does this PR close?
Refs #1984, #1980 and #1356. Integrates RFC 1435 without changing the public Receipt schema.
Rationale for this change
Operators need to see where accepted Sources stop processing and why retrieved memories do or do not reach a prepared context. Separate logs, counters and Receipts require manual reconstruction and do not retain the actual candidate text for relevance checks.
What changes are included in this PR?
v1_5_0_006, whose create statement already includes the nullable UTF-8query_textcolumn. Preserve the published plugin revisionv1_5_0_005and all earlier resources. Register both source bridges and SQLite/MySQL layouts.Are there any user-facing changes?
A new recall diagnostics page and additional source-processing details are available in Dashboard. Capture always runs on the Server and retains query and candidate/final text permanently; this change adds no expiry or cleanup action. Standalone SDK use does not write this Server store. Reads preserve current Scope/Artifact authorization, completed audit and no-store responses.
Existing managed databases require explicit migration before startup. The additive revision does not rewrite existing domain data. The public prepare response and reuse behavior remain unchanged. Prepared context does not prove host injection, model use or task benefit.
How was this change tested?
uv run pytest tests/builtin/persistence tests/test_migration_revision_names.py tests/test_managed_atomic_maintenance.py tests/test_managed_processing_maintenance.py tests/test_registered_source_maintenance_cli.py -q— 1023 passed, 135 skipped. The skipped cases are seekDB and OceanBase probes that were not enabled; no live native-backend upgrade acceptance is claimed.uv run pytest tests/test_dashboard_context_capture.py tests/test_dashboard_context_diagnostics.py tests/test_dashboard_processing_status.py tests/test_migration_revision_names.py tests/builtin/persistence/test_diagnostic_query_migration.py tests/e2e/test_dashboard_business_diagnostics.py -q— 43 passed.make check— passed, including the lock file, all pre-commit hooks andty check.make docs-test— passed, including the bilingual build and verification of 1,114 exported public pages.AI usage statement
Implemented with OpenAI Codex. Changes were inspected against repository contracts and exercised with local automated checks and controlled browser fixtures.