Skip to content

[dashboards] Link wiki evidence chips to thought pages#408

Open
alanshurafa wants to merge 11 commits into
NateBJones-Projects:mainfrom
alanshurafa:upstream/dash-evidence-links
Open

[dashboards] Link wiki evidence chips to thought pages#408
alanshurafa wants to merge 11 commits into
NateBJones-Projects:mainfrom
alanshurafa:upstream/dash-evidence-links

Conversation

@alanshurafa

Copy link
Copy Markdown
Collaborator

Links UUID-shaped wiki evidence chips to their /thoughts/{id} pages in open-brain-dashboard-pro.

Depends on #407 (stacked; diff includes ancestors until they merge).

alanshurafa and others added 3 commits June 13, 2026 14:38
The integration was ported from a bigint-id codebase and parsed thought
and job ids as numbers. On Open Brain (UUID primary keys) that breaks at
runtime: upsert_thought returns a UUID that extractThoughtId rejects as
"no thought_id", /execute 400s on a UUID job_id, and the pro dashboard's
ingest routes reject every UUID with a positive-integer guard.

Convert every ingestion id field (integration + both dashboards) from
number to string, validate job ids as UUIDs, and replace the 0 "no id"
sentinel with an empty string. Pairs with the smart-ingest-tables schema
so a job completes end to end on a fresh UUID install.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Post-UUID conversion, the integer job_id examples return 400 ("must be a UUID"). Align the docs with the handler's UUID_RE check.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@github-actions github-actions Bot added dashboard Contribution: frontend template integration Contribution: MCP extension or capture source recipe Contribution: step-by-step recipe labels Jul 6, 2026
@github-actions

github-actions Bot commented Jul 6, 2026

Copy link
Copy Markdown

OB1 PR Gate

Folder structure — All files are in allowed directories
Required files — README.md and metadata.json found in all contribution folders
Metadata valid — All metadata.json files passed JSON Schema validation
No credentials — No API keys, tokens, or secrets detected
SQL safety — No destructive SQL or core table modifications
Category artifacts — Required file types present for each category
PR format — Title follows [category] Description format
No binary blobs — No oversized or binary files
README completeness — All READMEs include Prerequisites, Steps, and Expected Outcome
Contribution dependencies — All declared skill and primitive dependencies exist and are linked in README
LLM clarity review — Covered by Claude PR Review workflow
Remote MCP pattern — No local MCP server patterns detected — uses remote MCP correctly
Tool audit link — Extensions/integrations link to the MCP Tool Audit guide
Scope check — All changes are within the contribution folder(s)
Internal links — All relative links in READMEs resolve to existing files

Result: All 15 checks passed! Ready for human review.


Post-Merge Tasks

These don't block merge — they're reminders for admins after this PR lands.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 39d3bde4cf

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

label: "typed-reasoning-edges (thought_edges; needs entity edges)",
},
wikiPages: {
file: "schemas/wiki-pages/schema.sql",

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P1 Badge Point the default bootstrap bundle at checked-in schemas

The default wiki-crm bundle includes wikiPages, so readSchemaSql immediately tries to read schemas/wiki-pages/schema.sql; that file is not present in this checkout, and the same is true for the CRM schema paths referenced just below (schemas/crm-core and schemas/crm-engagement). As a result the advertised one-command installer exits with Schema file not found before applying any SQL unless the user manually switches to --bundle core.

Useful? React with 👍 / 👎.

}

const meta = person.metadata || {};
const contact = await gateway("POST", "/crm/contacts", {

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P1 Badge Wire the CRM quick-start to routes the gateway serves

The default --demo path posts to /crm/contacts, but the checked-in integrations/open-brain-rest gateway this recipe tells users to deploy does not define any /crm/* routes (repo-wide search of that integration finds none). After the initial /health succeeds, the first contact creation therefore returns 404 and the quick-start cannot demonstrate the CRM flow.

Useful? React with 👍 / 👎.

Comment on lines +904 to +906
const jobId = typeof body.job_id === "string" && UUID_RE.test(body.job_id.trim())
? body.job_id.trim()
: "";

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Badge Keep smart-ingest execute IDs compatible with the schema

This new UUID-only check rejects the job IDs produced by the current smart-ingest schema: schemas/smart-ingest/schema.sql still declares ingestion_jobs.id bigserial, and the REST proxy path for job execution is numeric. Any dry-run job created by the existing tables is sent back as a numeric ID, so /smart-ingest/execute now returns job_id is required (must be a UUID) instead of executing it.

Useful? React with 👍 / 👎.

@alanshurafa alanshurafa force-pushed the upstream/dash-evidence-links branch from 39d3bde to 50640bd Compare July 6, 2026 01:31
@alanshurafa alanshurafa force-pushed the upstream/dash-evidence-links branch from 50640bd to bf929f1 Compare July 6, 2026 16:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dashboard Contribution: frontend template integration Contribution: MCP extension or capture source recipe Contribution: step-by-step recipe

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant