SyslogSolution/ra-h-os
7
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat: sync open-source context and capsule removal

Browse Source 
- remove legacy contexts surfaces from the app, MCP bridge, standalone server, and docs
- keep getContext and retrieveQueryContext while aligning the simplified graph-only contract
- harden dev startup migration behavior and disable the accidental chat surface in open source

Generated with Codex
This commit is contained in:
“BeeRad”
2026-04-17 12:34:51 +10:00
parent 97eeb0789f
commit 07754f5030
87 changed files with 2688 additions and 4861 deletions
Download Patch File Download Diff File Expand all files Collapse all files
apps/mcp-server-standalone/skills/node-context-enrichment.md
+16 -22
View File
@@ -1,13 +1,13 @@
---
name: Node Context Enrichment
description: "Use to rewrite thin node descriptions into natural prose that still makes what, why, and status clear, with context review and edge suggestions."
description: "Use to rewrite thin node descriptions into natural prose that still makes what, why, and status clear, with graph review and edge suggestions."
---
# Node Context Enrichment
Use this when a node already exists but its description is thin, generic, or missing personal context.
Use this when a node already exists but its description is thin, generic, or missing useful graph framing.
This skill should not silently rewrite and move on when contextual framing is inferred. If the enrichment depends on interpretation, update the node and then explicitly invite the user to correct or refine the contextual framing.
This skill should not silently rewrite and move on when framing is inferred. If the enrichment depends on interpretation, update the node and then explicitly invite the user to correct or refine that framing.
## Goal
@@ -17,24 +17,19 @@ Replace weak descriptions with a single clean natural description that captures:
2. Why it is in Brad's graph
3. Status in Brad's workflow
Also review whether the node needs context cleanup or obvious edge suggestions.
Also review whether the node needs obvious edge suggestions.
## Workflow
1. Load the node and inspect title, description, source, link, metadata, context, and nearby edges.
2. Search for adjacent context before rewriting:
- the node's primary context and its anchor node when present
1. Load the node and inspect title, description, source, link, metadata, and nearby edges.
2. Search for adjacent graph context before rewriting:
- recently connected project or belief nodes
- related nodes with overlapping titles, creators, or neighboring context
3. Infer the best available "why" from that context.
- related nodes with overlapping titles, creators, or neighboring structure
3. Infer the best available "why" from that graph context.
4. Rewrite the full description from scratch in natural prose. Do not append to the old text or use labels like WHAT:, WHY:, or STATUS:.
5. Review context fit:
- keep the current context when it is clearly the primary scope
- suggest clearing context when it is weak or misleading
- suggest a different context only when the primary scope is explicit
6. Suggest 1-3 high-signal edges when obvious.
7. Update the node once the description is strong enough to be useful.
8. After the update, tell the user what changed and ask whether they want to refine the important framing:
5. Suggest 1-3 high-signal edges when obvious.
6. Update the node once the description is strong enough to be useful.
7. After the update, tell the user what changed and ask whether they want to refine the important framing:
- what it is
- why it belongs in the graph
- status / current relevance / workflow position
@@ -52,7 +47,7 @@ Every rewritten description must naturally cover:
2. Why
- why Brad saved it
- what project, belief, question, or theme it connects to
- if genuinely unknown, say that naturally without inventing context
- if genuinely unknown, say that naturally without inventing graph framing
3. Status
- queued, in progress, processed, not yet reviewed, saved for later, etc.
- if unknown, say naturally that it has not been reviewed yet
@@ -71,14 +66,13 @@ Use batch enrichment when cleaning up many nodes with the same failure mode.
3. Enrich each node individually. Do not reuse boilerplate "why" text across unrelated nodes.
4. Return a compact summary of:
- nodes updated
- context assignments to review
- edge suggestions not yet created
- edge suggestions not yet created
## Quality Bar
- No filler phrases like `insightful for understanding`, `relevant to`, or `important for`.
- No generic summaries that only restate the topic.
- No invented certainty. If context is weak, say so explicitly.
- No invented certainty. If graph evidence is weak, say so explicitly.
- Prefer one compact 3-sentence description over bloated prose.
## Output Pattern
@@ -86,6 +80,6 @@ Use batch enrichment when cleaning up many nodes with the same failure mode.
For each node:
- New description
- Context change: keep / change / clear
- Framing note: what graph context influenced the rewrite, if any
- Edge suggestions: source -> target with explicit explanation
- One short invitation for user feedback when contextual framing was inferred
- One short invitation for user feedback when framing was inferred