Repository navigation
Release/1.7.7 - #49
Merged
Merged
Conversation
added 13 commits
October 16, 2026 14:12
When reasoning runs, the play button (▶/▶) is replaced by a stop button (■) in both TopBar and ReasoningIndicator. Clicking stop sends a stopReasoning command to the worker, which calls resetDlReasoner() to terminate the Konclude/WASM inner reasoner. The pending runReasoning promise rejects, the finally block resets isReasoning=false, and the play button reappears. RDF graph data in the outer worker is unaffected. New worker command: stopReasoning (protocol + runtime + workerClient + impl). New handler: handleStopReasoning in ReactodiaCanvas.
…eout Two bugs fixed: 1. resetCallTimeout() was called on every vg-ping, including the relay popup's own 10 s heartbeat (no sessionId). When Ontosphere stops responding, these heartbeats endlessly reset the 30 s deadline → isProcessing stays true forever → idlePoll never scans for new calls. Fix: only extend the deadline on Ontosphere-sourced pings (sessionId present), i.e. when the app is provably still alive. 2. When a per-call or batch timeout fires, callQueue = [] discarded remaining calls whose signatures were already in dispatchedSigs, making them invisible to idlePoll forever. Fix: un-mark those sigs before clearing the queue so the next idlePoll cycle can re-extract them from the page. Same cleanup applied when the popup fails to open. Also adds pendingSig tracking so the currently-dispatched call's sig is also removed from dispatchedSigs on timeout, allowing the AI to retry an identical call. Also stages relay-mock-chat.html (Claude.ai TipTap mock mode) which was modified but not committed in the 1.7.6 release.
Two fixes for the scenario where an AI retries a failing tool call: 1. Hard max deadline (CALL_HARD_MAX_MS = 90 s): even when Ontosphere keeps pinging with sessionId (tool is hung on network), resetCallTimeout now caps the next timer at (hardMax - elapsed) so the call always times out within 90 s from dispatch, not infinitely. 2. Duplicate-call toast: when idlePoll finds tool calls in the page but all are already in dispatchedSigs (AI retried identical id+params), a visible warning toast now fires at most once per 10 s explaining that the relay ignored them and asking the AI to change the call. Previously this was silent, leaving the user with no feedback. extractAllToolCalls now returns null sentinels for already-seen calls (counted separately), and idlePoll uses filterNew/countSkipped helpers so the dispatch path only sees genuinely new calls.
The previous toast used a 10 s time debounce which still fired repeatedly because idlePoll scans the full page on every cycle and old chat-history calls are permanently visible. Replaced with a notifiedDupSigs Set: a toast fires at most once per unique duplicate sig for the lifetime of the bookmarklet instance. Pre-seed also absorbs existing dups silently so no spurious toast fires on load.
The previous pre-seed called newDupSigs() on _preSeed, but _preSeed contains fresh call objects (isDup is unset) because dispatchedSigs was empty at that point. So notifiedDupSigs stayed empty, and the very first idlePoll cycle would find all history calls as fresh dups and fire the toast for them all. Fix: directly add each pre-seed call's sig to notifiedDupSigs so history calls are silently absorbed. Toast only fires for sigs that appear for the first time AFTER the bookmarklet loads.
… breaking
A JSON-RPC call with an unquoted key (e.g. {Jsiirpc"...}) phase-shifts
the string-boundary tracker in extractJsonObjects: the inner { chars get
absorbed as phantom-string content, depth never reaches 0, and the
function returns complete=false → break, silently discarding every valid
tool call that follows on the same page.
Change the break to i = start + 1; continue so the scanner skips the
bad opening brace and picks up the next { — the AI's corrected retry call
is then extracted and dispatched normally.
Regression test added: malformed call followed by valid retry now yields
exactly one dispatched call.
…t after delete Two bugs caused SPARQL DELETE/INSERT via queryGraph to appear to succeed but leave the canvas unchanged: 1. Graph targeting: Comunica follows the SPARQL 1.1 spec — bare patterns in DELETE/INSERT/WHERE without an explicit GRAPH clause target the default graph (empty in our N3 store), not urn:vg:data. Fix: after parsing, BGP patterns in update operations that have no GRAPH wrapper are automatically scoped to GRAPH <urn:vg:data>. Explicit GRAPH clauses are left untouched. 2. Empty canvas refresh: after a complete DELETE the subject set is empty, so the if (emission.subjects.length > 0) guard suppressed emitSubjects, leaving all nodes on the canvas. Fix: always call emitSubjects after a SPARQL update so the canvas clears correctly.
… reasoner across runs 0.8.0 digests store content on every call and rebuilds only on change, so the per-run terminate/recreate workaround and the reset on graph removal are gone. Entailment cache is now keyed on the reasoning input generation.
… graph removed Inferred quads outlive the axioms they came from; their orphaned subjects reappeared on the canvas after unloading an ontology.
The unload emission lists the removed subjects, which the incremental sync treated as new and created elements for. Drop them from the emission and from knownSubjects, and never create elements on unload.
Also restores the Table 2 benchmark runner, updated for the current MCP tool exposure, with a repeated-run mode.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Changelog
[1.7.7] — 2026-10-16
Reasoning
owl:AsymmetricPropertyself-loop gap.Bug fixes
urn:vg:inferred: inferences no longer outlive the axioms they came from.UPDATEpatterns are scoped tourn:vg:data, and a delete always refreshes the canvas.isProcessingdeadlock or lost batch calls on timeout; hard maximum call deadline with duplicate-call visibility; no duplicate-call toast for chat history entries;notifiedDupSigsseeded correctly from page history; JSON extraction restarts after a malformed{instead of aborting.New features
WebMCP support (document.modelContext)
document.modelContextpolyfill, object-formregisterTool,toolchangeevents, and signal-based unregistrationAI Relay Bridge — Gemini support
rich-textareacontenteditable componentaria-label="Send message"with visibility guard (Gemini hides the send button with a CSShiddenclass during generation instead of usingdisabled)"Stop generating"and"Stop response"button label variantsAI Relay Bridge — reliability improvements
getGraphStatescoped by graph list; unified with canvas summarySHACL violations
rdfs:labelvalues for human-readable property and class namesBug fixes
Deletekey and halo delete button now route through the authoring state machine; nodes no longer reappear after save when deleted via keyboardisAiStreaming()guard after stability regression; added two-poll idle streak requirement before injection to prevent the UUID-echo bug on OWUIBreaking changes
None. The WebMCP polyfill is opt-in and backwards-compatible with the existing
window.__mcpToolsregistration path.