Skip to content

Add Protocol Diagnostics page#229

Merged
smithaldon1 merged 1 commit into
mainfrom
feat/issue-215-protocol-diagnostics-page
May 25, 2026
Merged

Add Protocol Diagnostics page#229
smithaldon1 merged 1 commit into
mainfrom
feat/issue-215-protocol-diagnostics-page

Conversation

@smithaldon1
Copy link
Copy Markdown
Member

Closes #215

Summary

  • Add a /protocol-diagnostics Workbench route and navigation entry for protocol operations.
  • Show API-backed health cards for OPC-UA, MQTT, BACnet, the FIP API, and ingestion using existing FIP health, connection profile, read-only test, and process-signal endpoints.
  • Show configured connection status, latest read-only test result, checked timestamp, and readable error/next-step messages.
  • Add a searchable source mapping table derived from configured profile source identifiers and mapping_reference values.
  • Include local Demo-Factory validation next-step commands without reading or hardcoding Demo-Factory runtime state.
  • Extend Playwright config with optional API/web port overrides so e2e validation can run when default ports are already occupied.

Test Evidence

  • cd apps/web && npm test - passed, 17 tests.
  • cd apps/web && npm run lint - passed.
  • cd apps/web && npm run typecheck - passed.
  • cd apps/web && npm run build - passed; /protocol-diagnostics built as a dynamic route.
  • cd apps/web && npm run test:e2e - default run first failed because http://127.0.0.1:8000/health was already occupied by an existing Docker listener.
  • cd apps/web && PLAYWRIGHT_API_PORT=8001 PLAYWRIGHT_WEB_PORT=3001 PLAYWRIGHT_BASE_URL=http://127.0.0.1:3001 npm run test:e2e - passed, 1 test.
  • make lint - passed; Ruff reported all checks passed.
  • make typecheck - passed; compileall completed across packages and services.
  • make test - passed, 266 tests.
  • make docs - passed; docs are Markdown-only and no checker is configured yet.
  • git diff --check and git diff --cached --check - passed.

Docs Impact

  • Updated docs/LEARNING_LOG.md with what changed, why it matters, how the page loads FIP API data, how to run it, how to test it, and the next learning step.

Follow-up Work

  • Add the dedicated Tag/Source Browser with explicit mapping records instead of deriving rows from connection profile source identifiers.
  • Persist historical connection test results if operators need a true audit/history view rather than the current read-only diagnostics snapshot.

@smithaldon1 smithaldon1 force-pushed the feat/issue-215-protocol-diagnostics-page branch from d79934e to a9d16c5 Compare May 25, 2026 17:45
@smithaldon1 smithaldon1 force-pushed the feat/issue-215-protocol-diagnostics-page branch from a9d16c5 to d06002a Compare May 25, 2026 17:55
Copy link
Copy Markdown
Member Author

@smithaldon1 smithaldon1 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewed and approved for merge

@smithaldon1 smithaldon1 merged commit d1f135d into main May 25, 2026
3 checks passed
@smithaldon1 smithaldon1 deleted the feat/issue-215-protocol-diagnostics-page branch May 25, 2026 17:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

10. Feature: Add Protocol Diagnostics page

1 participant