@qvac/core 1.0.0-rc.1 → 1.0.0-rc.11
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +1205 -1
- package/README.md +56 -45
- package/dist-lib/index.d.ts +3 -2
- package/dist-lib/index.js +1 -1
- package/dist-lib/lib/api/agent-folders.d.ts +22 -0
- package/dist-lib/lib/api/agent-folders.js +115 -0
- package/dist-lib/lib/api/agents.d.ts +20 -2
- package/dist-lib/lib/api/agents.js +128 -24
- package/dist-lib/lib/api/app-config.d.ts +7 -1
- package/dist-lib/lib/api/app-config.js +37 -6
- package/dist-lib/lib/api/approval-rules.d.ts +1 -1
- package/dist-lib/lib/api/approval-rules.js +12 -5
- package/dist-lib/lib/api/attachments.d.ts +1 -1
- package/dist-lib/lib/api/attachments.js +14 -2
- package/dist-lib/lib/api/chat-move.d.ts +4 -0
- package/dist-lib/lib/api/chat-move.js +7 -0
- package/dist-lib/lib/api/chat.d.ts +12 -2
- package/dist-lib/lib/api/chat.js +100 -9
- package/dist-lib/lib/api/chunk-delta.d.ts +12 -0
- package/dist-lib/lib/api/chunk-delta.js +115 -0
- package/dist-lib/lib/api/chunks.d.ts +19 -2
- package/dist-lib/lib/api/chunks.js +73 -13
- package/dist-lib/lib/api/config.d.ts +11 -3
- package/dist-lib/lib/api/config.js +51 -5
- package/dist-lib/lib/api/current-mesh.d.ts +13 -5
- package/dist-lib/lib/api/current-mesh.js +15 -11
- package/dist-lib/lib/api/custom-models.d.ts +7 -1
- package/dist-lib/lib/api/custom-models.js +12 -12
- package/dist-lib/lib/api/device-routes.d.ts +14 -0
- package/dist-lib/lib/api/device-routes.js +144 -0
- package/dist-lib/lib/api/devices.d.ts +3 -2
- package/dist-lib/lib/api/devices.js +28 -28
- package/dist-lib/lib/api/diagnostics.d.ts +2 -1
- package/dist-lib/lib/api/diagnostics.js +2 -2
- package/dist-lib/lib/api/execution.d.ts +16 -1
- package/dist-lib/lib/api/execution.js +72 -16
- package/dist-lib/lib/api/files.d.ts +1 -1
- package/dist-lib/lib/api/files.js +65 -8
- package/dist-lib/lib/api/host-run-log.d.ts +2 -41
- package/dist-lib/lib/api/host-run-log.js +35 -83
- package/dist-lib/lib/api/index.d.ts +39 -7
- package/dist-lib/lib/api/index.js +116 -36
- package/dist-lib/lib/api/instrument.d.ts +2 -2
- package/dist-lib/lib/api/instrument.js +24 -48
- package/dist-lib/lib/api/knowledge.d.ts +4 -1
- package/dist-lib/lib/api/knowledge.js +25 -7
- package/dist-lib/lib/api/local-files.d.ts +5 -1
- package/dist-lib/lib/api/local-files.js +9 -5
- package/dist-lib/lib/api/logs.js +3 -3
- package/dist-lib/lib/api/members.d.ts +10 -1
- package/dist-lib/lib/api/members.js +69 -44
- package/dist-lib/lib/api/mesh.d.ts +15 -6
- package/dist-lib/lib/api/mesh.js +13 -9
- package/dist-lib/lib/api/model-download.d.ts +2 -1
- package/dist-lib/lib/api/model-download.js +2 -2
- package/dist-lib/lib/api/network.d.ts +10 -2
- package/dist-lib/lib/api/network.js +8 -2
- package/dist-lib/lib/api/notifications.d.ts +3 -1
- package/dist-lib/lib/api/notifications.js +14 -9
- package/dist-lib/lib/api/projects.d.ts +20 -0
- package/dist-lib/lib/api/projects.js +172 -0
- package/dist-lib/lib/api/rag-plugin.d.ts +17 -0
- package/dist-lib/lib/api/rag-plugin.js +44 -0
- package/dist-lib/lib/api/rag.d.ts +0 -1
- package/dist-lib/lib/api/rag.js +106 -33
- package/dist-lib/lib/api/served.d.ts +17 -0
- package/dist-lib/lib/api/served.js +65 -0
- package/dist-lib/lib/api/sync.d.ts +2 -1
- package/dist-lib/lib/api/sync.js +13 -3
- package/dist-lib/lib/api/tool-activity.d.ts +2 -1
- package/dist-lib/lib/api/tool-activity.js +4 -3
- package/dist-lib/lib/api/tool-configs.d.ts +2 -1
- package/dist-lib/lib/api/tool-configs.js +6 -9
- package/dist-lib/lib/api/upload-frames.d.ts +0 -1
- package/dist-lib/lib/api/upload-frames.js +0 -1
- package/dist-lib/lib/api/watchable.d.ts +3 -2
- package/dist-lib/lib/api/watchable.js +2 -3
- package/dist-lib/lib/api/workspace.d.ts +12 -0
- package/dist-lib/lib/api/workspace.js +61 -0
- package/dist-lib/lib/assistant/fake-models.d.ts +20 -0
- package/dist-lib/lib/assistant/fake-models.js +112 -0
- package/dist-lib/lib/assistant/harness.d.ts +48 -31
- package/dist-lib/lib/assistant/harness.js +51 -10
- package/dist-lib/lib/assistant/history.d.ts +37 -17
- package/dist-lib/lib/assistant/history.js +212 -87
- package/dist-lib/lib/assistant/host-run-log.d.ts +6 -1
- package/dist-lib/lib/assistant/host-run-log.js +24 -36
- package/dist-lib/lib/assistant/media-round.d.ts +61 -0
- package/dist-lib/lib/assistant/media-round.js +111 -0
- package/dist-lib/lib/assistant/message.d.ts +28 -1
- package/dist-lib/lib/assistant/message.js +65 -2
- package/dist-lib/lib/assistant/model-round.d.ts +118 -0
- package/dist-lib/lib/assistant/model-round.js +706 -0
- package/dist-lib/lib/assistant/pdf-budget.d.ts +11 -0
- package/dist-lib/lib/assistant/pdf-budget.js +12 -0
- package/dist-lib/lib/assistant/pdf-pages.d.ts +25 -0
- package/dist-lib/lib/assistant/pdf-pages.js +75 -0
- package/dist-lib/lib/assistant/round-host.d.ts +65 -0
- package/dist-lib/lib/assistant/round-host.js +332 -0
- package/dist-lib/lib/assistant/skill-encode.d.ts +2 -1
- package/dist-lib/lib/assistant/skill-encode.js +2 -1
- package/dist-lib/lib/assistant/upload.d.ts +12 -0
- package/dist-lib/lib/assistant/upload.js +36 -0
- package/dist-lib/lib/assistant/video-budget.d.ts +13 -0
- package/dist-lib/lib/assistant/video-budget.js +29 -0
- package/dist-lib/lib/assistant-client.d.ts +5 -1
- package/dist-lib/lib/assistant-client.js +54 -14
- package/dist-lib/lib/assistant-tree.d.ts +14 -3
- package/dist-lib/lib/assistant-tree.js +113 -21
- package/dist-lib/lib/assistant.d.ts +115 -25
- package/dist-lib/lib/assistant.js +2409 -1245
- package/dist-lib/lib/audio-format.js +1 -1
- package/dist-lib/lib/chat-suggestion.d.ts +3 -0
- package/dist-lib/lib/chat-suggestion.js +47 -0
- package/dist-lib/lib/client.d.ts +3 -2
- package/dist-lib/lib/client.js +18 -3
- package/dist-lib/lib/compaction.d.ts +3 -1
- package/dist-lib/lib/compaction.js +20 -6
- package/dist-lib/lib/constants.d.ts +10 -0
- package/dist-lib/lib/constants.js +10 -0
- package/dist-lib/lib/core/agent-copies.d.ts +9 -0
- package/dist-lib/lib/core/agent-copies.js +47 -0
- package/dist-lib/lib/core/agent-hosting.d.ts +25 -0
- package/dist-lib/lib/core/agent-hosting.js +76 -0
- package/dist-lib/lib/core/agent.d.ts +9 -1
- package/dist-lib/lib/core/agent.js +58 -63
- package/dist-lib/lib/core/approval-rules.d.ts +5 -1
- package/dist-lib/lib/core/approval-rules.js +17 -9
- package/dist-lib/lib/core/archived-mesh.d.ts +14 -7
- package/dist-lib/lib/core/archived-mesh.js +75 -59
- package/dist-lib/lib/core/async-iterable.js +1 -1
- package/dist-lib/lib/core/blind-peers.d.ts +1 -0
- package/dist-lib/lib/core/blind-peers.js +1 -0
- package/dist-lib/lib/core/chat-activity.d.ts +1 -1
- package/dist-lib/lib/core/chat-activity.js +45 -34
- package/dist-lib/lib/core/chat-copy.d.ts +42 -0
- package/dist-lib/lib/core/chat-copy.js +404 -0
- package/dist-lib/lib/core/chat-fork.d.ts +16 -0
- package/dist-lib/lib/core/chat-fork.js +246 -0
- package/dist-lib/lib/core/chat-group.js +10 -22
- package/dist-lib/lib/core/chat-move.d.ts +77 -0
- package/dist-lib/lib/core/chat-move.js +601 -0
- package/dist-lib/lib/core/chat-order.d.ts +2 -1
- package/dist-lib/lib/core/chat-order.js +28 -19
- package/dist-lib/lib/core/chat-read.d.ts +4 -0
- package/dist-lib/lib/core/chat-read.js +49 -0
- package/dist-lib/lib/core/chat-search.js +14 -12
- package/dist-lib/lib/core/chat.d.ts +32 -4
- package/dist-lib/lib/core/chat.js +135 -61
- package/dist-lib/lib/core/chunk.d.ts +35 -7
- package/dist-lib/lib/core/chunk.js +271 -72
- package/dist-lib/lib/core/collections.d.ts +41 -1
- package/dist-lib/lib/core/collections.js +41 -1
- package/dist-lib/lib/core/config-value.d.ts +7 -0
- package/dist-lib/lib/core/config-value.js +15 -0
- package/dist-lib/lib/core/contract/activity.d.ts +7 -2
- package/dist-lib/lib/core/contract/activity.js +71 -23
- package/dist-lib/lib/core/contract/agent-join.d.ts +10 -0
- package/dist-lib/lib/core/contract/agent-join.js +104 -0
- package/dist-lib/lib/core/contract/agents.d.ts +5 -0
- package/dist-lib/lib/core/contract/agents.js +142 -3
- package/dist-lib/lib/core/contract/chat.d.ts +4 -0
- package/dist-lib/lib/core/contract/chat.js +53 -3
- package/dist-lib/lib/core/contract/chunks.d.ts +7 -0
- package/dist-lib/lib/core/contract/chunks.js +125 -38
- package/dist-lib/lib/core/contract/devices.js +6 -4
- package/dist-lib/lib/core/contract/index.d.ts +2 -3
- package/dist-lib/lib/core/contract/index.js +38 -11
- package/dist-lib/lib/core/contract/indexing.d.ts +1 -0
- package/dist-lib/lib/core/contract/indexing.js +51 -7
- package/dist-lib/lib/core/contract/invites.d.ts +3 -14
- package/dist-lib/lib/core/contract/invites.js +26 -36
- package/dist-lib/lib/core/contract/joined-meshes.js +4 -1
- package/dist-lib/lib/core/contract/knowledge.d.ts +1 -0
- package/dist-lib/lib/core/contract/knowledge.js +57 -6
- package/dist-lib/lib/core/contract/members.d.ts +3 -1
- package/dist-lib/lib/core/contract/members.js +48 -12
- package/dist-lib/lib/core/contract/mesh-kind.d.ts +3 -3
- package/dist-lib/lib/core/contract/mesh-kind.js +20 -16
- package/dist-lib/lib/core/contract/mesh-name.d.ts +3 -0
- package/dist-lib/lib/core/contract/mesh-name.js +31 -0
- package/dist-lib/lib/core/contract/mesh-rules.d.ts +8 -0
- package/dist-lib/lib/core/contract/mesh-rules.js +35 -0
- package/dist-lib/lib/core/contract/mesh-seeds.d.ts +2 -0
- package/dist-lib/lib/core/contract/mesh-seeds.js +26 -0
- package/dist-lib/lib/core/contract/model-requests.d.ts +26 -0
- package/dist-lib/lib/core/contract/model-requests.js +280 -0
- package/dist-lib/lib/core/contract/oldest-version.d.ts +9 -0
- package/dist-lib/lib/core/contract/oldest-version.js +20 -0
- package/dist-lib/lib/core/contract/open-join.d.ts +2 -0
- package/dist-lib/lib/core/contract/open-join.js +77 -0
- package/dist-lib/lib/core/contract/project-device-keys.d.ts +9 -0
- package/dist-lib/lib/core/contract/project-device-keys.js +38 -0
- package/dist-lib/lib/core/contract/project-host-keys.d.ts +9 -0
- package/dist-lib/lib/core/contract/project-host-keys.js +52 -0
- package/dist-lib/lib/core/contract/project-order.d.ts +2 -0
- package/dist-lib/lib/core/contract/project-order.js +25 -0
- package/dist-lib/lib/core/contract/projects.d.ts +23 -0
- package/dist-lib/lib/core/contract/projects.js +339 -0
- package/dist-lib/lib/core/contract/public-mesh.d.ts +3 -0
- package/dist-lib/lib/core/contract/public-mesh.js +31 -0
- package/dist-lib/lib/core/contract/public-seeds.d.ts +9 -0
- package/dist-lib/lib/core/contract/public-seeds.js +43 -0
- package/dist-lib/lib/core/contract/roles.d.ts +10 -0
- package/dist-lib/lib/core/contract/roles.js +123 -0
- package/dist-lib/lib/core/contract/run-requests.d.ts +11 -0
- package/dist-lib/lib/core/contract/run-requests.js +114 -0
- package/dist-lib/lib/core/contract/seed-defaults.d.ts +3 -1
- package/dist-lib/lib/core/contract/seed-defaults.js +17 -4
- package/dist-lib/lib/core/contract/shipped-rows.d.ts +2 -0
- package/dist-lib/lib/core/contract/shipped-rows.js +22 -0
- package/dist-lib/lib/core/contract/skill-secrets.d.ts +3 -0
- package/dist-lib/lib/core/contract/skill-secrets.js +32 -0
- package/dist-lib/lib/core/contract/tool-activity.js +12 -1
- package/dist-lib/lib/core/contract/tool-configs.js +2 -1
- package/dist-lib/lib/core/contract/types.d.ts +2 -2
- package/dist-lib/lib/core/contract/workspace.d.ts +31 -0
- package/dist-lib/lib/core/contract/workspace.js +311 -0
- package/dist-lib/lib/core/contract/writers.js +100 -16
- package/dist-lib/lib/core/deleted-agent-runs.d.ts +8 -0
- package/dist-lib/lib/core/deleted-agent-runs.js +57 -0
- package/dist-lib/lib/core/departures.d.ts +18 -5
- package/dist-lib/lib/core/departures.js +82 -6
- package/dist-lib/lib/core/device-control.d.ts +21 -0
- package/dist-lib/lib/core/device-control.js +91 -0
- package/dist-lib/lib/core/device-seal.d.ts +4 -0
- package/dist-lib/lib/core/device-seal.js +22 -0
- package/dist-lib/lib/core/devices.d.ts +2 -1
- package/dist-lib/lib/core/devices.js +6 -11
- package/dist-lib/lib/core/document-attachment.d.ts +10 -0
- package/dist-lib/lib/core/document-attachment.js +14 -0
- package/dist-lib/lib/core/files/attachments.d.ts +2 -0
- package/dist-lib/lib/core/files/attachments.js +23 -7
- package/dist-lib/lib/core/files/index.d.ts +28 -15
- package/dist-lib/lib/core/files/index.js +222 -43
- package/dist-lib/lib/core/files/knowledge.d.ts +10 -1
- package/dist-lib/lib/core/files/knowledge.js +77 -5
- package/dist-lib/lib/core/files/preview/index.js +6 -2
- package/dist-lib/lib/core/files/processing/claims.d.ts +7 -0
- package/dist-lib/lib/core/files/processing/claims.js +33 -7
- package/dist-lib/lib/core/files/processing/document.d.ts +8 -0
- package/dist-lib/lib/core/files/processing/document.js +26 -2
- package/dist-lib/lib/core/files/processing/index.d.ts +12 -3
- package/dist-lib/lib/core/files/processing/index.js +122 -73
- package/dist-lib/lib/core/files/processing/protocol.d.ts +7 -1
- package/dist-lib/lib/core/files/processing/protocol.js +27 -37
- package/dist-lib/lib/core/files/processing/source.d.ts +4 -0
- package/dist-lib/lib/core/files/processing/source.js +12 -4
- package/dist-lib/lib/core/files/processing/state.d.ts +5 -1
- package/dist-lib/lib/core/files/processing/state.js +9 -1
- package/dist-lib/lib/core/files/rag/build.d.ts +15 -2
- package/dist-lib/lib/core/files/rag/build.js +119 -21
- package/dist-lib/lib/core/files/rag/failure.d.ts +20 -0
- package/dist-lib/lib/core/files/rag/failure.js +58 -0
- package/dist-lib/lib/core/files/rag/index.d.ts +21 -5
- package/dist-lib/lib/core/files/rag/index.js +38 -9
- package/dist-lib/lib/core/files/rag/joined-index.d.ts +6 -0
- package/dist-lib/lib/core/files/rag/joined-index.js +35 -0
- package/dist-lib/lib/core/files/rag/limits.d.ts +1 -0
- package/dist-lib/lib/core/files/rag/limits.js +1 -0
- package/dist-lib/lib/core/files/rag/load.d.ts +3 -3
- package/dist-lib/lib/core/files/rag/load.js +6 -3
- package/dist-lib/lib/core/files/rag/plugin-index.d.ts +32 -0
- package/dist-lib/lib/core/files/rag/plugin-index.js +120 -0
- package/dist-lib/lib/core/files/rag/policy.d.ts +10 -1
- package/dist-lib/lib/core/files/rag/policy.js +23 -2
- package/dist-lib/lib/core/files/rag/produce.d.ts +3 -4
- package/dist-lib/lib/core/files/rag/produce.js +31 -18
- package/dist-lib/lib/core/files/rag/retrieval/full-text.d.ts +2 -0
- package/dist-lib/lib/core/files/rag/retrieval/full-text.js +8 -2
- package/dist-lib/lib/core/files/rag/similarity.d.ts +2 -2
- package/dist-lib/lib/core/files/rag/similarity.js +2 -3
- package/dist-lib/lib/core/files/records/chunks.js +22 -1
- package/dist-lib/lib/core/files/records/index.d.ts +1 -1
- package/dist-lib/lib/core/files/records/index.js +1 -1
- package/dist-lib/lib/core/files/records/knowledge.d.ts +12 -4
- package/dist-lib/lib/core/files/records/knowledge.js +34 -30
- package/dist-lib/lib/core/files/records/purge.js +13 -8
- package/dist-lib/lib/core/files/records/reclaim.js +21 -55
- package/dist-lib/lib/core/files/records/routing.d.ts +1 -1
- package/dist-lib/lib/core/files/records/routing.js +6 -2
- package/dist-lib/lib/core/files/records/source.js +3 -5
- package/dist-lib/lib/core/files/records/sweep.d.ts +3 -0
- package/dist-lib/lib/core/files/records/sweep.js +9 -3
- package/dist-lib/lib/core/files/store/blob.d.ts +2 -0
- package/dist-lib/lib/core/files/store/blob.js +2 -2
- package/dist-lib/lib/core/files/store/index.d.ts +3 -1
- package/dist-lib/lib/core/files/store/index.js +4 -1
- package/dist-lib/lib/core/files/store/reference.d.ts +3 -0
- package/dist-lib/lib/core/files/store/reference.js +12 -2
- package/dist-lib/lib/core/files/store/sweep.js +3 -1
- package/dist-lib/lib/core/files/upload.d.ts +5 -1
- package/dist-lib/lib/core/files/upload.js +117 -51
- package/dist-lib/lib/core/first-event.d.ts +6 -0
- package/dist-lib/lib/core/first-event.js +13 -0
- package/dist-lib/lib/core/fs-drives.d.ts +6 -3
- package/dist-lib/lib/core/fs-drives.js +35 -35
- package/dist-lib/lib/core/helpers/index.d.ts +1 -1
- package/dist-lib/lib/core/helpers/index.js +2 -2
- package/dist-lib/lib/core/id.d.ts +1 -0
- package/dist-lib/lib/core/id.js +3 -0
- package/dist-lib/lib/core/identity.d.ts +3 -1
- package/dist-lib/lib/core/identity.js +25 -4
- package/dist-lib/lib/core/invite.d.ts +6 -2
- package/dist-lib/lib/core/invite.js +22 -8
- package/dist-lib/lib/core/local/files.d.ts +2 -1
- package/dist-lib/lib/core/local/files.js +5 -7
- package/dist-lib/lib/core/local/index.d.ts +93 -8
- package/dist-lib/lib/core/local/index.js +327 -28
- package/dist-lib/lib/core/local/run-logs.d.ts +38 -0
- package/dist-lib/lib/core/local/run-logs.js +132 -0
- package/dist-lib/lib/core/member-key.d.ts +7 -0
- package/dist-lib/lib/core/member-key.js +24 -0
- package/dist-lib/lib/core/membership.d.ts +3 -14
- package/dist-lib/lib/core/membership.js +3 -96
- package/dist-lib/lib/core/mesh.d.ts +132 -29
- package/dist-lib/lib/core/mesh.js +775 -215
- package/dist-lib/lib/core/migrations/agent-catalog.js +2 -8
- package/dist-lib/lib/core/migrations/agent-tools-scope.d.ts +2 -0
- package/dist-lib/lib/core/migrations/agent-tools-scope.js +18 -0
- package/dist-lib/lib/core/migrations/chat-chunks.d.ts +4 -0
- package/dist-lib/lib/core/migrations/chat-chunks.js +47 -0
- package/dist-lib/lib/core/migrations/file-index.d.ts +1 -1
- package/dist-lib/lib/core/migrations/file-index.js +8 -6
- package/dist-lib/lib/core/migrations/index.d.ts +2 -1
- package/dist-lib/lib/core/migrations/index.js +69 -8
- package/dist-lib/lib/core/migrations/writer-links.d.ts +3 -0
- package/dist-lib/lib/core/migrations/writer-links.js +30 -0
- package/dist-lib/lib/core/model-requests.d.ts +13 -0
- package/dist-lib/lib/core/model-requests.js +65 -0
- package/dist-lib/lib/core/next-frame.js +2 -1
- package/dist-lib/lib/core/notification.js +100 -25
- package/dist-lib/lib/core/pdf/figure.d.ts +22 -0
- package/dist-lib/lib/core/pdf/figure.js +64 -0
- package/dist-lib/lib/core/pdf/rasterize.d.ts +12 -3
- package/dist-lib/lib/core/pdf/rasterize.js +77 -28
- package/dist-lib/lib/core/peer-duplex.d.ts +34 -0
- package/dist-lib/lib/core/{harness-loan.js → peer-duplex.js} +104 -45
- package/dist-lib/lib/core/project-keys.d.ts +16 -0
- package/dist-lib/lib/core/project-keys.js +65 -0
- package/dist-lib/lib/core/prompt-history.js +4 -4
- package/dist-lib/lib/core/protocol-pairing.d.ts +11 -0
- package/dist-lib/lib/core/protocol-pairing.js +22 -0
- package/dist-lib/lib/core/public-mesh.d.ts +25 -0
- package/dist-lib/lib/core/public-mesh.js +81 -0
- package/dist-lib/lib/core/purge.d.ts +3 -0
- package/dist-lib/lib/core/purge.js +7 -0
- package/dist-lib/lib/core/run-driver.d.ts +17 -0
- package/dist-lib/lib/core/run-driver.js +20 -0
- package/dist-lib/lib/core/run-requests.d.ts +14 -0
- package/dist-lib/lib/core/run-requests.js +78 -0
- package/dist-lib/lib/core/send.d.ts +2 -0
- package/dist-lib/lib/core/send.js +17 -4
- package/dist-lib/lib/core/senders.d.ts +19 -0
- package/dist-lib/lib/core/senders.js +45 -0
- package/dist-lib/lib/core/shared-agents.d.ts +40 -0
- package/dist-lib/lib/core/shared-agents.js +283 -0
- package/dist-lib/lib/core/skill-availability.d.ts +33 -0
- package/dist-lib/lib/core/skill-availability.js +67 -0
- package/dist-lib/lib/core/skill-secrets.d.ts +13 -18
- package/dist-lib/lib/core/skill-secrets.js +93 -72
- package/dist-lib/lib/core/sync/background.d.ts +34 -0
- package/dist-lib/lib/core/sync/background.js +86 -0
- package/dist-lib/lib/core/sync/changed.d.ts +20 -0
- package/dist-lib/lib/core/sync/changed.js +7 -0
- package/dist-lib/lib/core/sync/devices.js +6 -3
- package/dist-lib/lib/core/sync/files.d.ts +1 -0
- package/dist-lib/lib/core/sync/files.js +50 -72
- package/dist-lib/lib/core/sync/index.d.ts +1 -1
- package/dist-lib/lib/core/sync/index.js +193 -81
- package/dist-lib/lib/core/sync/view-updates.d.ts +39 -0
- package/dist-lib/lib/core/sync/view-updates.js +124 -0
- package/dist-lib/lib/core/sync-status.js +99 -43
- package/dist-lib/lib/core/system-info.d.ts +2 -2
- package/dist-lib/lib/core/system-info.js +10 -11
- package/dist-lib/lib/core/tool-activity.js +6 -12
- package/dist-lib/lib/core/tool-configs.d.ts +5 -3
- package/dist-lib/lib/core/tool-configs.js +27 -39
- package/dist-lib/lib/core/transcript-visibility.d.ts +5 -5
- package/dist-lib/lib/core/transcript-visibility.js +27 -31
- package/dist-lib/lib/core/upgrade-agents.d.ts +11 -0
- package/dist-lib/lib/core/upgrade-agents.js +78 -0
- package/dist-lib/lib/core/upgrade-summary.d.ts +19 -0
- package/dist-lib/lib/core/upgrade-summary.js +67 -0
- package/dist-lib/lib/core/vault-managed-skills.d.ts +18 -0
- package/dist-lib/lib/core/vault-managed-skills.js +105 -0
- package/dist-lib/lib/core/video/attachment.d.ts +1 -0
- package/dist-lib/lib/core/video/attachment.js +7 -0
- package/dist-lib/lib/core/video/digest.d.ts +16 -0
- package/dist-lib/lib/core/video/digest.js +57 -0
- package/dist-lib/lib/core/video/frames.d.ts +32 -0
- package/dist-lib/lib/core/video/frames.js +224 -0
- package/dist-lib/lib/core/view-read.d.ts +4 -0
- package/dist-lib/lib/core/view-read.js +23 -0
- package/dist-lib/lib/core/workspace-upgrade.d.ts +23 -0
- package/dist-lib/lib/core/workspace-upgrade.js +51 -0
- package/dist-lib/lib/core.d.ts +345 -88
- package/dist-lib/lib/core.js +4275 -1513
- package/dist-lib/lib/credential-pusher.d.ts +17 -7
- package/dist-lib/lib/credential-pusher.js +111 -62
- package/dist-lib/lib/custom-model-pusher.d.ts +2 -4
- package/dist-lib/lib/custom-model-task.d.ts +2 -1
- package/dist-lib/lib/custom-model-task.js +2 -2
- package/dist-lib/lib/device-tree.d.ts +18 -0
- package/dist-lib/lib/device-tree.js +32 -0
- package/dist-lib/lib/diagnostics.d.ts +7 -0
- package/dist-lib/lib/diagnostics.js +22 -0
- package/dist-lib/lib/doctor/checks.d.ts +15 -0
- package/dist-lib/lib/doctor/checks.js +272 -0
- package/dist-lib/lib/doctor/redact.d.ts +4 -0
- package/dist-lib/lib/doctor/redact.js +31 -0
- package/dist-lib/lib/doctor/render.d.ts +8 -0
- package/dist-lib/lib/doctor/render.js +83 -0
- package/dist-lib/lib/doctor/tree.d.ts +5 -0
- package/dist-lib/lib/doctor/tree.js +167 -0
- package/dist-lib/lib/downloads-allowed-pusher.d.ts +8 -0
- package/dist-lib/lib/downloads-allowed-pusher.js +37 -0
- package/dist-lib/lib/errors.d.ts +814 -0
- package/dist-lib/lib/errors.js +748 -0
- package/dist-lib/lib/fs-drive-bridge.d.ts +8 -1
- package/dist-lib/lib/fs-drive-bridge.js +312 -31
- package/dist-lib/lib/guards.d.ts +1 -0
- package/dist-lib/lib/guards.js +4 -0
- package/dist-lib/lib/inference-calls.d.ts +1 -2
- package/dist-lib/lib/inference-calls.js +2 -10
- package/dist-lib/lib/integrations/setup-routes.js +7 -5
- package/dist-lib/lib/knowledge-search.d.ts +1 -1
- package/dist-lib/lib/knowledge-search.js +5 -51
- package/dist-lib/lib/kv-cache-ledger.d.ts +22 -0
- package/dist-lib/lib/kv-cache-ledger.js +72 -0
- package/dist-lib/lib/kv-cache-reclaim.d.ts +2 -1
- package/dist-lib/lib/kv-cache-reclaim.js +30 -0
- package/dist-lib/lib/kv-cache-retention.d.ts +36 -0
- package/dist-lib/lib/kv-cache-retention.js +101 -0
- package/dist-lib/lib/latest-frame.d.ts +10 -0
- package/dist-lib/lib/latest-frame.js +48 -0
- package/dist-lib/lib/llm-model-names.d.ts +1 -1
- package/dist-lib/lib/llm-model-names.js +1 -1
- package/dist-lib/lib/log.d.ts +7 -6
- package/dist-lib/lib/log.js +14 -7
- package/dist-lib/lib/logger-type.d.ts +2 -5
- package/dist-lib/lib/mesh-scoped-engine.js +47 -2
- package/dist-lib/lib/model-context.js +1 -2
- package/dist-lib/lib/model-download-status.d.ts +3 -3
- package/dist-lib/lib/model-download.d.ts +22 -13
- package/dist-lib/lib/model-download.js +106 -37
- package/dist-lib/lib/model-idle-pusher.d.ts +2 -4
- package/dist-lib/lib/model-memory-cap.d.ts +30 -0
- package/dist-lib/lib/model-memory-cap.js +78 -0
- package/dist-lib/lib/models-watch.d.ts +1 -1
- package/dist-lib/lib/models-watch.js +4 -4
- package/dist-lib/lib/oauth/browser-connect.js +3 -2
- package/dist-lib/lib/oauth/flow-core.js +5 -3
- package/dist-lib/lib/oauth/flow.js +1 -1
- package/dist-lib/lib/oauth/loopback.d.ts +1 -0
- package/dist-lib/lib/oauth/loopback.js +57 -12
- package/dist-lib/lib/oauth/providers.js +4 -2
- package/dist-lib/lib/oauth/redirect-types.d.ts +1 -0
- package/dist-lib/lib/oauth/register.js +35 -19
- package/dist-lib/lib/oauth/request.d.ts +10 -0
- package/dist-lib/lib/oauth/request.js +22 -0
- package/dist-lib/lib/oauth/resolve.js +42 -13
- package/dist-lib/lib/oauth/token-exchange-core.js +40 -31
- package/dist-lib/lib/oauth/types.d.ts +3 -0
- package/dist-lib/lib/oauth.d.ts +2 -1
- package/dist-lib/lib/oauth.js +1 -0
- package/dist-lib/lib/persistent-dir.d.ts +1 -0
- package/dist-lib/lib/persistent-dir.js +9 -0
- package/dist-lib/lib/probe-rounds.d.ts +8 -0
- package/dist-lib/lib/probe-rounds.js +10 -0
- package/dist-lib/lib/reconnecting-watch.js +19 -11
- package/dist-lib/lib/run-input.d.ts +14 -0
- package/dist-lib/lib/run-input.js +33 -0
- package/dist-lib/lib/run-notices.d.ts +5 -0
- package/dist-lib/lib/run-notices.js +13 -2
- package/dist-lib/lib/run-replay.d.ts +45 -0
- package/dist-lib/lib/run-replay.js +169 -0
- package/dist-lib/lib/run-transcript.d.ts +13 -12
- package/dist-lib/lib/run-transcript.js +20 -19
- package/dist-lib/lib/suspend-lifecycle.js +15 -5
- package/dist-lib/lib/task.js +6 -4
- package/dist-lib/lib/test-env.d.ts +1 -0
- package/dist-lib/lib/test-env.js +4 -0
- package/dist-lib/schema/build.js +66 -55
- package/dist-lib/schema/config.d.ts +1 -1
- package/dist-lib/schema/config.js +1 -1
- package/dist-lib/schema/content.d.ts +5 -1
- package/dist-lib/schema/content.js +60 -12
- package/dist-lib/schema/engine.d.ts +1 -0
- package/dist-lib/schema/engine.js +941 -152
- package/dist-lib/schema/field-order.js +8 -1
- package/dist-lib/schema/indexes.d.ts +10 -0
- package/dist-lib/schema/indexes.js +53 -3
- package/dist-lib/schema/local.js +83 -5
- package/dist-lib/schema/qvac.d.ts +4 -1
- package/dist-lib/schema/qvac.js +558 -16
- package/dist-lib/spec/bind.js +261 -48
- package/dist-lib/spec/calls.js +56 -5
- package/dist-lib/spec/capabilities.d.ts +129 -20
- package/dist-lib/spec/config/hyperconf/index.js +1 -1
- package/dist-lib/spec/hrpc/hrpc.json +870 -207
- package/dist-lib/spec/hrpc/index.js +969 -347
- package/dist-lib/spec/hrpc/messages.js +7590 -4896
- package/dist-lib/spec/hyperschema/index.js +7590 -4896
- package/dist-lib/spec/hyperschema/schema.json +5316 -3224
- package/dist-lib/spec/hyperschema/types.d.ts +576 -62
- package/dist-lib/spec/local/hyperdb/db.json +95 -1
- package/dist-lib/spec/local/hyperdb/index.js +459 -2
- package/dist-lib/spec/local/hyperdb/messages.js +1588 -488
- package/dist-lib/spec/local/hyperschema/index.js +584 -16
- package/dist-lib/spec/local/hyperschema/schema.json +369 -1
- package/dist-lib/spec/local/hyperschema/types.d.ts +88 -2
- package/dist-lib/spec/mesh/hyperdb/db.json +711 -9
- package/dist-lib/spec/mesh/hyperdb/index.js +2769 -7
- package/dist-lib/spec/mesh/hyperdb/messages.js +7140 -1298
- package/dist-lib/spec/mesh/hyperdispatch/dispatch.json +205 -1
- package/dist-lib/spec/mesh/hyperdispatch/index.js +579 -1
- package/dist-lib/spec/mesh/hyperdispatch/messages.js +4017 -267
- package/dist-lib/spec/mesh/hyperschema/index.js +4017 -267
- package/dist-lib/spec/mesh/hyperschema/schema.json +2193 -19
- package/dist-lib/spec/mesh/hyperschema/types.d.ts +550 -6
- package/package.json +136 -90
- package/tui/README.md +119 -20
- package/tui/app.mjs +2000 -621
- package/tui/boot.mjs +76 -9
- package/tui/cli.mjs +93 -0
- package/tui/index.mjs +2 -51
- package/tui/lib/connect-sheet.mjs +350 -0
- package/tui/lib/device-target.mjs +64 -0
- package/tui/lib/folders-command.mjs +84 -0
- package/tui/lib/fork-command.mjs +43 -0
- package/tui/lib/knowledge-import.mjs +3 -21
- package/tui/lib/local-path.mjs +21 -0
- package/tui/lib/move-command.mjs +17 -0
- package/tui/lib/render.mjs +30 -1
- package/tui/lib/setup.mjs +59 -25
- package/tui/lib/skill-connect.mjs +145 -0
- package/tui/lib/updater.mjs +86 -0
- package/tui/main.mjs +44 -18
- package/tui/plugins.mjs +158 -0
- package/worker/assistant-sidecar.mjs +28 -4
- package/worker/stow-entry.mjs +3 -50
- package/dist-lib/lib/core/contract/compute.d.ts +0 -11
- package/dist-lib/lib/core/contract/compute.js +0 -48
- package/dist-lib/lib/core/device-invites.d.ts +0 -11
- package/dist-lib/lib/core/device-invites.js +0 -63
- package/dist-lib/lib/core/files/processing/settle.d.ts +0 -13
- package/dist-lib/lib/core/files/processing/settle.js +0 -86
- package/dist-lib/lib/core/grant-expiry.d.ts +0 -11
- package/dist-lib/lib/core/grant-expiry.js +0 -66
- package/dist-lib/lib/core/handoff-channel.d.ts +0 -47
- package/dist-lib/lib/core/handoff-channel.js +0 -123
- package/dist-lib/lib/core/harness-loan.d.ts +0 -29
- package/dist-lib/lib/core/host-run-log-store.d.ts +0 -114
- package/dist-lib/lib/core/host-run-log-store.js +0 -976
- package/dist-lib/lib/core/hosted-agents.d.ts +0 -38
- package/dist-lib/lib/core/hosted-agents.js +0 -140
- package/dist-lib/lib/core/inference-calls-handoff.d.ts +0 -20
- package/dist-lib/lib/core/inference-calls-handoff.js +0 -37
- package/dist-lib/lib/core/inference-calls-receiver.d.ts +0 -14
- package/dist-lib/lib/core/inference-calls-receiver.js +0 -42
- package/dist-lib/lib/core/mesh-seed-handoff.d.ts +0 -25
- package/dist-lib/lib/core/mesh-seed-handoff.js +0 -52
- package/dist-lib/lib/core/migrations/device-indexes.d.ts +0 -2
- package/dist-lib/lib/core/migrations/device-indexes.js +0 -7
- package/dist-lib/lib/core/secret-handoff.d.ts +0 -17
- package/dist-lib/lib/core/secret-handoff.js +0 -29
- package/dist-lib/lib/core/skill-overlay-handoff.d.ts +0 -25
- package/dist-lib/lib/core/skill-overlay-handoff.js +0 -50
- package/dist-lib/lib/core/skill-overlay-receiver.d.ts +0 -8
- package/dist-lib/lib/core/skill-overlay-receiver.js +0 -23
- package/dist-lib/lib/image-cache-dir.d.ts +0 -1
- package/dist-lib/lib/image-cache-dir.js +0 -5
- package/dist-lib/lib/log-levels.d.ts +0 -7
- package/dist-lib/lib/log-levels.js +0 -1
- package/dist-lib/lib/logger.d.ts +0 -5
- package/dist-lib/lib/logger.js +0 -18
- package/dist-lib/lib/oauth/loopback.stub.d.ts +0 -3
- package/dist-lib/lib/oauth/loopback.stub.js +0 -6
package/CHANGELOG.md
CHANGED
|
@@ -13,6 +13,1188 @@ release.
|
|
|
13
13
|
|
|
14
14
|
## [Unreleased]
|
|
15
15
|
|
|
16
|
+
### Added
|
|
17
|
+
|
|
18
|
+
- `continueRunHere({ meshId, chunkId })`: the device a run was sent from takes back a run another
|
|
19
|
+
of your devices holds, and picks it up from its last round. Refused with `RUN_REQUEST_OFFLINE`
|
|
20
|
+
while this device is offline. `examples/run-continue-here.mjs` shows it; see
|
|
21
|
+
[chunks](docs/api/chunks.md#continuerunhere).
|
|
22
|
+
|
|
23
|
+
- `workspaceUpgradeSummary` says what the upgrade from 0.20 converted on this device, so the app
|
|
24
|
+
can tell the person once: each workspace the mesh list shows that this device minted a project
|
|
25
|
+
for or merged chats into, whether one of its groups is still pending, whether it had chat-groups
|
|
26
|
+
at all, the project its ungrouped chats went to, and the workspace this device copied the 0.20
|
|
27
|
+
private chats into, with `privateChatsPending` until that copy finishes. See
|
|
28
|
+
[workspace](docs/api/workspace.md#workspaceupgradesummary).
|
|
29
|
+
|
|
30
|
+
```js
|
|
31
|
+
const { workspaces, privateChatsWorkspaceId } = await engine.workspaceUpgradeSummary()
|
|
32
|
+
```
|
|
33
|
+
|
|
34
|
+
- Image and music generation for a remote agent runs on the chat's model host. The tools stay on
|
|
35
|
+
the device driving the run and ask the host with a probe round; the host waits for its model,
|
|
36
|
+
generates, and names the output by blob (`putBlob`); the driver's attachment names that blob. An
|
|
37
|
+
edit's sources go by the chat's attachment ids and the host fits them. A host that will never hold
|
|
38
|
+
the model settles `model-missing` and the driver uses its own. An agent this device serves
|
|
39
|
+
generates in process, with its step progress. Needs harness 1.0.0-rc.20, and this Core on both
|
|
40
|
+
devices: a host on an earlier 1.0 prerelease never takes the round, so the tool waits until the run
|
|
41
|
+
is stopped or the host leaves. (#755)
|
|
42
|
+
|
|
43
|
+
- A vision model sees an image a tool attaches during a run, such as a PNG `http_request` downloads
|
|
44
|
+
from Google Drive. The assistant gives the harness the image from its own image cache, as it does
|
|
45
|
+
a user's image, and the harness shows it on the turn that closes the tool round. Later runs show
|
|
46
|
+
it again on the same turn. Video stays an attachment for now. Needs a harness with `showImage`.
|
|
47
|
+
|
|
48
|
+
- A completed run that primed the chat cache after Core deleted it says so on its
|
|
49
|
+
`run-status.metrics`: `cacheRebuild` carries Core's deletion reason and the prompt tokens of the
|
|
50
|
+
run's first round on the key, as its `metrics.rounds` counts them, null when that round has no
|
|
51
|
+
count. A run whose first round was taken on another device reports nothing, since that device
|
|
52
|
+
keeps its own cache. A run that reused the cache carries no key.
|
|
53
|
+
|
|
54
|
+
```js
|
|
55
|
+
const { runStatus } = chunk
|
|
56
|
+
if (runStatus.state === 'completed' && runStatus.metrics?.cacheRebuild) {
|
|
57
|
+
const { reason, tokens } = runStatus.metrics.cacheRebuild
|
|
58
|
+
}
|
|
59
|
+
```
|
|
60
|
+
|
|
61
|
+
- The last agent to stop running a loaded model on a device — deleted, moved to another device or
|
|
62
|
+
switched to another model — unloads it there, so the memory is freed without waiting for the idle
|
|
63
|
+
sweep. A model loaded by hand that no agent runs stays loaded.
|
|
64
|
+
|
|
65
|
+
- `@qvac/core/sidecar-entry` names the script a host spawns as Core's sidecar, so a host
|
|
66
|
+
resolves it by name instead of a path into the package. `test/basic/entry-weight.ts` holds
|
|
67
|
+
every named entry to a ceiling on the files importing it loads, so an app that imports a
|
|
68
|
+
constant never parses the engine.
|
|
69
|
+
|
|
70
|
+
- After a completed run, on a host that asks for it, the assistant suggests the user's likely next message
|
|
71
|
+
and stores it on the chat, so a client can offer it to accept with one key:
|
|
72
|
+
|
|
73
|
+
```js
|
|
74
|
+
const chat = await engine.getChat({ meshId, chatId })
|
|
75
|
+
if (chat.suggestion?.runId === latestRunId) offer(chat.suggestion.text)
|
|
76
|
+
```
|
|
77
|
+
|
|
78
|
+
It is one short tool-less call after the title, cancelled by the chat's next
|
|
79
|
+
run, and off until the model host sets the device config key
|
|
80
|
+
`assistant.suggestPrompts` to `on`.
|
|
81
|
+
([chat.md](docs/api/chat.md#setchatsuggestion))
|
|
82
|
+
|
|
83
|
+
- A message sent while the chat's run is still going steers it: the model host
|
|
84
|
+
hands it to that run, which takes it at its next tool call and answers it there,
|
|
85
|
+
instead of queueing a separate run behind it. Its own run then ends at once:
|
|
86
|
+
|
|
87
|
+
```js
|
|
88
|
+
// { state: 'completed', reason: 'steered', metrics: { steeredInto: runId } }
|
|
89
|
+
```
|
|
90
|
+
|
|
91
|
+
A run that never takes it leaves the message its own run, as before, and a
|
|
92
|
+
harness without steering ignores the offer.
|
|
93
|
+
([execution.md](docs/api/execution.md#sendmessage))
|
|
94
|
+
|
|
95
|
+
- `worker/assistant-sidecar.mjs` takes `autoDownloadModels` from the host and
|
|
96
|
+
passes it to `Core`. Unset keeps today's behaviour; `false` starts a host
|
|
97
|
+
without fetching the default models. A sidecar that fails to start also writes
|
|
98
|
+
the reason to stderr, since the host may not be listening yet.
|
|
99
|
+
- `duck plugins list|install|enable|disable` manages the userland harness
|
|
100
|
+
plugins in `~/.config/qv-ac` without booting an engine. Install clones a git
|
|
101
|
+
URL or copies a `hyper://` drive, and does not enable what it installs.
|
|
102
|
+
- `npm i -g bare @qvac/core` runs `duck`: the model addons the harness's stock entry loads are
|
|
103
|
+
optional dependencies of the package, so an install brings them, and `bare-thread` is pinned to
|
|
104
|
+
`~1.2.7` in `dependencies`, since 1.4 fails to load the stowed harness worker.
|
|
105
|
+
|
|
106
|
+
- `chatSkillAvailability` and `chatSkillAvailabilityWatch`: on a phone, which of a chat's skills
|
|
107
|
+
cannot run right now, `{ name, available, reason: 'platform' }`. (#733)
|
|
108
|
+
- `CoreOptions.onerror(err, { meshId })` receives every error caught on the autobee path. Without
|
|
109
|
+
one, Core logs it under the `errors` scope. (#785)
|
|
110
|
+
|
|
111
|
+
### Changed
|
|
112
|
+
|
|
113
|
+
- **Breaking for a host:** `engines.bare` is `>=1.35.0`. Core runs on Bare 1.36 with the current
|
|
114
|
+
Holepunch packages, and `bare-worker` 4.5.3 and `bare-sidecar` 0.5.15 need Bare 1.35 to start a
|
|
115
|
+
worker or a sidecar. Core depends on `@qvac/harness` 1.0.0-rc.19, whose Python plugin has the
|
|
116
|
+
same floor.
|
|
117
|
+
([decision](docs/decisions/2026-09-25-workers-run-on-bare-worker-and-bare-is-pinned.md))
|
|
118
|
+
|
|
119
|
+
- `uploadAttachment` and `uploadKnowledge` hold at most 16 MiB a stream is yet to read. A client
|
|
120
|
+
that keeps writing after `write` returns `false` past that is cut off with `STREAM_OVERFLOW`,
|
|
121
|
+
which ends its whole connection to Core. Wait for the stream to drain between frames, as the
|
|
122
|
+
example in [attachments](docs/api/attachments.md) does.
|
|
123
|
+
|
|
124
|
+
- A peer that sends nothing for 10 s is dropped, so a frozen device leaves `peerDeviceIds` in
|
|
125
|
+
seconds rather than staying listed. See [mesh](docs/api/mesh.md).
|
|
126
|
+
|
|
127
|
+
- A streaming reply lands in its chat about once a second instead of every 250 ms: `RunTranscript`
|
|
128
|
+
flushes buffered text on a 1 s tick (and still at 8,192 chars, on a type or round change and at the
|
|
129
|
+
end). A client watching the chat gets a quarter of the frames, so it should pace its own text
|
|
130
|
+
animation by how often text arrives rather than assume a fixed cadence. On a Pixel 8 this cut
|
|
131
|
+
app CPU per generated token by about 30% and skin heating per token by 20–40%, with decode speed
|
|
132
|
+
unchanged.
|
|
133
|
+
([decision](docs/decisions/2026-11-05-a-streaming-reply-lands-once-a-second.md))
|
|
134
|
+
|
|
135
|
+
- A private chat linked to a project no longer reads the project's knowledge base: `ragSearch` and
|
|
136
|
+
the runs it feeds rank the knowledge base only for a chat in the project. ([rag.md](docs/api/rag.md))
|
|
137
|
+
|
|
138
|
+
- The KV cache retention sweep runs every 12 hours instead of every hour, besides when a mesh opens
|
|
139
|
+
and when `kvCache.retentionDays` changes, so a cache can outlive its retention by up to 12 hours
|
|
140
|
+
on a host that stays up. ([config.md](docs/api/config.md#kv-cache-retention))
|
|
141
|
+
|
|
142
|
+
- Core depends on `@qvac/harness` 1.0.0-rc.20 from npm instead of a git commit, so a consumer installs
|
|
143
|
+
the published harness with its named entries. Qwen3.6-27B left the harness catalog in rc.20, so it
|
|
144
|
+
leaves Core's context table too: an agent saved on it sizes its window as an uncurated model.
|
|
145
|
+
|
|
146
|
+
- Wipe a store written by 1.0.0-rc.0 to rc.2 before running this build. The collection, route and
|
|
147
|
+
field ids those prereleases gave the 1.0 additions moved up by one to keep 0.11.1's in place, so
|
|
148
|
+
this build misreads their rows without an error. A store from 0.11.1 or earlier upgrades as is.
|
|
149
|
+
Nor does the wipe carry over a mesh an rc wrote to, minted there or a 0.11 mesh an rc device
|
|
150
|
+
held writable, since an rc raises the rules on each: other peers and the blind peers still hold
|
|
151
|
+
its rc-numbered ops, so a device that rejoins it, by a recovery from the phrase too, misreads
|
|
152
|
+
them again. Start a new account on this build instead.
|
|
153
|
+
|
|
154
|
+
- The baked version floor is `>=0.22.0`: one build per mesh, since this release
|
|
155
|
+
changes what apply admits and app 0.22 is the first to ship it. Each mesh now
|
|
156
|
+
holds a rules row, `@qvac/mesh-rules`, first in a new mesh's genesis and
|
|
157
|
+
appended once when this build first holds an existing mesh writable, and apply
|
|
158
|
+
holds new rules to ops after it only. A 0.7.x or 0.11.x replica that applies
|
|
159
|
+
the row halts into its update prompt.
|
|
160
|
+
|
|
161
|
+
**Operator step:** publish `>=0.22.0` with `qvac-app → scripts/ota-config.mjs`
|
|
162
|
+
on each lane (dev, staging, prod) only once app 0.22 is live on that lane, and
|
|
163
|
+
never before: a floor above the installed release withholds every device on
|
|
164
|
+
the lane. Not `>=0.21.0`, which admits app 0.21 and its core 0.11.1, from
|
|
165
|
+
before the row. Until it is published, an old replica that fast-forwards past
|
|
166
|
+
the row applies later ops under the old rules.
|
|
167
|
+
|
|
168
|
+
- A rules row raised above the rules this build knows halts apply into its
|
|
169
|
+
update prompt with the code `MESH_RULES_FROM_A_NEWER_BUILD`, instead of being
|
|
170
|
+
applied.
|
|
171
|
+
|
|
172
|
+
- `harnessKnowledge` defaults to `true` in `worker/assistant-sidecar.mjs`: desktop and `duck` index
|
|
173
|
+
knowledge with the harness plugin, fed core's stored vectors on first start. Pass `false` to keep
|
|
174
|
+
core's index. (#806)
|
|
175
|
+
- Identical chunk text in a knowledge file is embedded once. (#804)
|
|
176
|
+
|
|
177
|
+
### Removed
|
|
178
|
+
|
|
179
|
+
- `duck`'s `/agent borrow` and `/mesh new compute`, now that Core 1.0 retires
|
|
180
|
+
model loans and compute meshes.
|
|
181
|
+
|
|
182
|
+
### Fixed
|
|
183
|
+
|
|
184
|
+
- A mesh still opening when Core closes is closed with it, and its open refuses with
|
|
185
|
+
`CORE_CLOSING`. It used to outlive the store it read.
|
|
186
|
+
|
|
187
|
+
- A generated file over 16 MiB uploads: the assistant waits for the upload stream to drain
|
|
188
|
+
instead of writing the whole file at once.
|
|
189
|
+
|
|
190
|
+
- An app that depends on Core installs the speech addon its harness asks for. `@qvac/asr-ggml` was
|
|
191
|
+
pinned to 0.4.2, outside the `^0.11.1` the harness's Speech plugin declares. It now follows the
|
|
192
|
+
harness range, and a test checks every optional peer of a plugin the harness entry loads against
|
|
193
|
+
Core's dependencies.
|
|
194
|
+
- `AssistantClient.close()` lets the sidecar close its Core before it returns. It used to
|
|
195
|
+
destroy the sidecar's pipe at once, which killed the child a few milliseconds into its close,
|
|
196
|
+
so every reopen recovered its meshes as after a crash. `close()` now asks the sidecar to stop,
|
|
197
|
+
waits for it to exit, and so takes a few seconds while Core's swarm closes.
|
|
198
|
+
- A video attachment with neither a video nor an audio stream is no longer sent to transcription
|
|
199
|
+
as a voice memo; the run's model is told it could not be read on this device.
|
|
200
|
+
- A reply served by another device no longer repeats parts of itself. The run owner skips the text
|
|
201
|
+
the host already wrote when its harness streams it back, but matched that text chunk by chunk,
|
|
202
|
+
and the harness wire joins chunks that arrive together, so a delta frame carrying two of the
|
|
203
|
+
host's chunks was written a second time by the owner. The echo is now matched as text.
|
|
204
|
+
- A run that restarts mid-reply no longer has its host write the abandoned round's answer a second
|
|
205
|
+
time beside the new attempt's: the run cancels the model rounds its earlier attempt left open
|
|
206
|
+
before it starts again.
|
|
207
|
+
- A resume whose announce reached no DHT node retries that topic within
|
|
208
|
+
seconds, instead of leaving the device unfindable for ten minutes.
|
|
209
|
+
- A chat cache whose workspace this device no longer sees is deleted: left while the device was
|
|
210
|
+
closed, before it heard of the leave, or a member's chats it served. The assistant records which
|
|
211
|
+
chats it built a cache for and, at boot and whenever a mesh leaves the list, deletes those no open
|
|
212
|
+
mesh lists. A host keeps that record beside the run replays, through the new `kvCacheChatsDir`
|
|
213
|
+
option, so a data reset takes both; retention Never turns the sweep off too.
|
|
214
|
+
|
|
215
|
+
```js
|
|
216
|
+
assistantTree({ runReplayDir: `${root}/run-replay`, kvCacheChatsDir: `${root}/kv-cache-chats` })
|
|
217
|
+
```
|
|
218
|
+
|
|
219
|
+
- A device that hosts another member's agent sweeps its chat caches too: KV cache retention and the
|
|
220
|
+
orphaned cache sweep read a hosted mesh through `listChats`, which the assistant's connection now
|
|
221
|
+
answers there with the chats it serves, instead of failing the whole sweep. A host restart keeps
|
|
222
|
+
the caches it serves until hosting resumes, instead of deleting them at boot.
|
|
223
|
+
- Upgrading from app 0.21 no longer reruns a send that was still unanswered in a private chat. The
|
|
224
|
+
private chats copied into your own workspace now end an open run as failed, as the chats copied
|
|
225
|
+
into a project already did, instead of leaving a request for the assistant to take. An approval
|
|
226
|
+
that run was holding is denied in the copy in both places, so none stays pending on a failed run.
|
|
227
|
+
|
|
228
|
+
- Mesh sync and close no longer wedge: a failed fast-forward warmup rejects, a failed sync pass is
|
|
229
|
+
delivered again, a close with unserved blocks finishes and flushes queued ops, a joined mesh
|
|
230
|
+
announces its own writer to every new peer, a workspace's name is kept on the device and answered
|
|
231
|
+
offline, and reads answer from what the device holds instead of waiting on a timeout or reporting
|
|
232
|
+
a caught read error as missing data. (#779, #791, #795, #796, #798, #800, #801, #802, #805, #814)
|
|
233
|
+
- The view walk reads 16 nodes at a time instead of 1024. (#782)
|
|
234
|
+
- A served round loads at its agent's window, survives another mesh's rounds changing, and stops
|
|
235
|
+
when its mesh closes or is left. (#783, #790, #793)
|
|
236
|
+
- A chat rename made while its title is generated is kept. (#780)
|
|
237
|
+
- Copying tool activity keeps the seq placeholder. (#810)
|
|
238
|
+
- `duck`'s launcher no longer bundles a second copy of the harness's model addons, which on
|
|
239
|
+
linux-x64 ran its build out of room. (#832)
|
|
240
|
+
|
|
241
|
+
## [0.11.4] - 2026-10-30
|
|
242
|
+
|
|
243
|
+
### Changed
|
|
244
|
+
|
|
245
|
+
- A `mesh write` or `mesh drain` stall now keeps reporting while it lasts (#649). Each `… still pending`
|
|
246
|
+
line carries `reports` (1, 2, 3 …), and the wait doubles between reports. It also names:
|
|
247
|
+
- `fastForwarding`: the head a fast-forward is booting onto, with how much of that core this
|
|
248
|
+
device and its peers hold, or `null`.
|
|
249
|
+
- `peerLength` and `peerHeld` on every `missing` core: how far the furthest connected peer
|
|
250
|
+
knows that core, and how much of it that peer holds from block 0.
|
|
251
|
+
- `writers` on a mesh still joining: each writer it knows, with the same holdings.
|
|
252
|
+
- The logs now name the build and what an open did to an older mesh (#650):
|
|
253
|
+
- `core opening` is the first line of a launch. It names the app's `version`, `build` and
|
|
254
|
+
`channel`, and the mesh `schema` this core applies. A mesh's own `opening` line names the
|
|
255
|
+
`schema` too.
|
|
256
|
+
- `migrations ran` follows each pass on open. It lists the steps that wrote, each step's `ms`,
|
|
257
|
+
and the step that threw as `failed`. A pass still going after 15 s logs
|
|
258
|
+
`migrations still running` with its current step, again after 30 s, 60 s, and so on.
|
|
259
|
+
- `copied chats into chat-chunks` and `recorded the files the mesh already held` give each
|
|
260
|
+
backfill's count and `ms`.
|
|
261
|
+
|
|
262
|
+
### Fixed
|
|
263
|
+
|
|
264
|
+
- The assistant no longer logs `saveDeviceCapabilities failed` while the account mesh is still
|
|
265
|
+
joining. Core refuses the report with `MESH_STILL_JOINING` until this device is a writer, and the
|
|
266
|
+
assistant already reports again once the account turns writable, so the refusal was never a
|
|
267
|
+
failure. (#648)
|
|
268
|
+
|
|
269
|
+
## [0.11.3] - 2026-10-28
|
|
270
|
+
|
|
271
|
+
### Added
|
|
272
|
+
|
|
273
|
+
- The first run to complete stores which pictures of a PDF it sent, as an attachment chunk whose
|
|
274
|
+
`sourceId` is the PDF's attachment id, so later turns and other devices send the same ones. Do
|
|
275
|
+
not render an attachment chunk that carries a `sourceId`. (#640)
|
|
276
|
+
|
|
277
|
+
### Changed
|
|
278
|
+
|
|
279
|
+
- A PDF's pictures reach a vision model cut to each figure and its caption, named by page and
|
|
280
|
+
figure, instead of as whole pages, and white pages are no longer sent. The PDF's text and its
|
|
281
|
+
pictures now share half the context window, less what the chat already holds, where each took
|
|
282
|
+
half before: a PDF whose whole text fit filled the window and compacted on the next message.
|
|
283
|
+
(#640)
|
|
284
|
+
- `bare-pdfium` is required at `^1.8.0`, for `imageBounds` and `pageBox`; a host that packages the
|
|
285
|
+
addon ships that version. (#640)
|
|
286
|
+
|
|
287
|
+
## [0.11.2] - 2026-10-28
|
|
288
|
+
|
|
289
|
+
### Added
|
|
290
|
+
|
|
291
|
+
- A chat's KV cache is deleted once the chat has been idle for the retention, so a device no
|
|
292
|
+
longer keeps the cache of every chat it ever ran. The chat itself is untouched; its next message
|
|
293
|
+
primes from history. An app sets its default with `kvCacheRetentionMs` on `assistantChild` (14
|
|
294
|
+
days without it, `0` for Never), and a device overrides it with `kvCache.retentionDays`. (#589)
|
|
295
|
+
|
|
296
|
+
```js
|
|
297
|
+
import { assistantChild } from '@qvac/core'
|
|
298
|
+
import { KV_CACHE_RETENTION_KEY } from '@qvac/core/constants'
|
|
299
|
+
|
|
300
|
+
assistantChild({ harness, kvCacheRetentionMs: 30 * 24 * 60 * 60_000 })
|
|
301
|
+
await engine.configSet({ key: KV_CACHE_RETENTION_KEY, value: 7 })
|
|
302
|
+
```
|
|
303
|
+
|
|
304
|
+
- Every credential a skill declares is pushed to the harness, not only the built-in keys and
|
|
305
|
+
OAuth tokens, so a skill with its own key no longer reads needs-setup for good and needs no core
|
|
306
|
+
release. Where a value may be sent is unchanged, and an overlay skill gets no credential. (#596)
|
|
307
|
+
- A credential with no setup block and no token provider gets a one-field token route named after
|
|
308
|
+
its key, so any setup UI can set it. (#591)
|
|
309
|
+
- `duck` sets a skill up through one sheet, opened by `/skill <name>`. (#592)
|
|
310
|
+
|
|
311
|
+
### Changed
|
|
312
|
+
|
|
313
|
+
- `toolResult.result` is required on the wire, so a tool result of `false`, `0` or `''` reads
|
|
314
|
+
back as written from `listChunks` and `chunksWatch` instead of `null`. A device on 0.11.0 or
|
|
315
|
+
earlier, and a result one of those releases wrote, still read `null`. (#559)
|
|
316
|
+
|
|
317
|
+
```js
|
|
318
|
+
// 0.11.1
|
|
319
|
+
{ type: 'tool-result', toolResult: { name } }
|
|
320
|
+
// 0.11.2
|
|
321
|
+
{ type: 'tool-result', toolResult: { name, result: null } }
|
|
322
|
+
```
|
|
323
|
+
|
|
324
|
+
### Removed
|
|
325
|
+
|
|
326
|
+
- `duck`'s `/cred`: every value is set through its skill's sheet. (#593)
|
|
327
|
+
|
|
328
|
+
### Fixed
|
|
329
|
+
|
|
330
|
+
- Chat activity no longer diffs across a fast-forward it has not counted yet. It
|
|
331
|
+
dropped its cached view head only once `fastForwards` moved, which can be
|
|
332
|
+
after the view has landed on another core, and a diff from the old head read
|
|
333
|
+
every node of the new view. It now drops the head whenever the view is on
|
|
334
|
+
another core, as `chunksDeltaWatch` does. (#623)
|
|
335
|
+
- A device that does not hold a mesh no longer downloads most of it to show chat
|
|
336
|
+
activity and notifications. Both read a few chunk types per chat, each through
|
|
337
|
+
its type index and then row by row from `@qvac/chunks`; they now read the
|
|
338
|
+
chat's range of `@qvac/chat-chunks` once and keep those types, where that
|
|
339
|
+
range is whole. A member joining a 170-chat mesh with both open downloaded
|
|
340
|
+
about 39,000 blocks (155 MB) instead of 258,000 (640 MB), and on a device that
|
|
341
|
+
holds the mesh their first frames take 2.2 s and 3.7 s instead of 5.8 s and
|
|
342
|
+
9.8 s. (#624)
|
|
343
|
+
- `compactChat` folds whole turns, so a chat whose messages were queued no longer keeps answers
|
|
344
|
+
without their questions. (#607)
|
|
345
|
+
- A run whose injected excerpts overflow the model window, with no older turns to fold, is retried
|
|
346
|
+
with half the excerpts instead of failing. (#599)
|
|
347
|
+
- `ragSearch` on a remote agent host waits for an attached file still replicating to it instead of
|
|
348
|
+
answering that the file is still being indexed. (#562)
|
|
349
|
+
- A chat whose first message carries a document is titled from the words the user typed, not the
|
|
350
|
+
document text. (#516)
|
|
351
|
+
- A re-homed agent's skill values are retried until the new host takes them; a host that refused
|
|
352
|
+
before it replicated the re-home left them unset. (#478)
|
|
353
|
+
|
|
354
|
+
## [0.11.1] - 2026-10-26
|
|
355
|
+
|
|
356
|
+
### Added
|
|
357
|
+
|
|
358
|
+
- `deviceTree(transport, { core, assistant, office, logger })` boots Core and
|
|
359
|
+
the assistant under one supervisor, the way the app does. (#544)
|
|
360
|
+
- The `reindex-chat-chunks` op copies a chat written before this release into
|
|
361
|
+
`@qvac/chat-chunks`. A build older than this one halts on it, so a device
|
|
362
|
+
sends it only once the published version floor shuts out every app release
|
|
363
|
+
before 0.21.0, the first whose core applies it. A build under the floor opens
|
|
364
|
+
no mesh, so none can halt on it; publish `>=0.21.0` once that release is in
|
|
365
|
+
both stores. (#491)
|
|
366
|
+
- A device's row in the account carries `customModels`: the label, task type
|
|
367
|
+
and size of each custom model it has. A paired desktop showed a custom model
|
|
368
|
+
added on the phone by its `custom:…` id, as Other and of unknown size, and
|
|
369
|
+
counted it outside the phone's LLMs. `saveDeviceCapabilities` takes the field,
|
|
370
|
+
and the assistant reports it again when a custom model is renamed. (#556)
|
|
371
|
+
|
|
372
|
+
### Changed
|
|
373
|
+
|
|
374
|
+
- `chunksDeltaWatch` reads only the rows that changed after its opening reset,
|
|
375
|
+
so an update no longer costs the whole chat. Frames are unchanged; a
|
|
376
|
+
selection with `limit` is still read whole. (#538)
|
|
377
|
+
- Injection-mode `ragSearch` sizes its excerpts to a quarter of the agent's
|
|
378
|
+
context window, capped at the 3072-token default, so a small window gets
|
|
379
|
+
fewer excerpts instead of overflowing. (#588)
|
|
380
|
+
- `hypercore` 11.39 and `hypercore-storage` 3.4, for a working purge. (#539)
|
|
381
|
+
- `hypercore-blob-server` 1.15.1 keeps its socket listening across a suspend,
|
|
382
|
+
so resume keeps the port and every minted link, and replaces the local patch.
|
|
383
|
+
(#561)
|
|
384
|
+
|
|
385
|
+
### Fixed
|
|
386
|
+
|
|
387
|
+
- A member whose only device in a shared mesh comes back far behind
|
|
388
|
+
fast-forwards instead of replaying everything it missed (183 s to 3.9 s on a
|
|
389
|
+
mesh about 6,900 flushes ahead): a shared mesh trusts every member's live
|
|
390
|
+
devices, not only this member's own, and never a device admitted unlinked. A
|
|
391
|
+
compute mesh still trusts only its own member's devices. (#492)
|
|
392
|
+
- Opening a chat on a device that does not hold the mesh no longer downloads most
|
|
393
|
+
of the mesh. Each chunk is also kept in `@qvac/chat-chunks`, keyed by chat and
|
|
394
|
+
`seq`, and a chat read is one range of it: a 1,100-chunk chat fetched about
|
|
395
|
+
1,000 blocks instead of 100,000. Once the published floor is at app 0.21.0 or
|
|
396
|
+
later, the chats written before this release are copied in the background, one
|
|
397
|
+
op per chat; until then, or while an older build still writes to a chat, it
|
|
398
|
+
reads the way it did before. A chat an older build purged also loses the rows
|
|
399
|
+
that build left in `@qvac/chat-chunks`. (#490, #491)
|
|
400
|
+
- `configGet` and `configWatch` return a stored `false`, `0` or `''` as written
|
|
401
|
+
instead of `null`. A device on 0.11.0 or earlier, a value one of those
|
|
402
|
+
releases wrote, and a downgrade to one still read them as `null`. (#546)
|
|
403
|
+
- A message's audio attachment is presented to the model as a transcript of its
|
|
404
|
+
speech only, so a tool that reads the audio itself, such as music
|
|
405
|
+
transcription, is used again. (#337)
|
|
406
|
+
- The assistant reports an agent it hosts in a shared mesh as soon as this
|
|
407
|
+
device has joined it. A device still joining had its report refused and never
|
|
408
|
+
reported again. (#324)
|
|
409
|
+
- `removeDevice` on the account revokes the device in a shared mesh whose row
|
|
410
|
+
for it arrives after the removal. Before, it stayed a writer there. (#547)
|
|
411
|
+
- `inferenceCalls` and the skill routes (`pushSkillSecret`,
|
|
412
|
+
`listManagedSkills`, `readSkillFile`, `writeSkillFile`, `copySkillForEdit`,
|
|
413
|
+
`deleteOverlaySkill`) from a device that has just paired no longer fail with
|
|
414
|
+
`PEER_SENDER_REVOKED`: the host waits up to 30 s for the new device's row.
|
|
415
|
+
(#544)
|
|
416
|
+
- Core no longer dies of an unhandled `REQUEST_CANCELLED` when a fast-forward
|
|
417
|
+
cancels the read that follows a joined mesh's shared meshes. (#474)
|
|
418
|
+
- A device restarted while its `joinMesh` is still `joining` boots the mesh
|
|
419
|
+
from the head its invite carried, instead of replaying it from its first
|
|
420
|
+
block, which on a big mesh took minutes. (#515)
|
|
421
|
+
- `meshInvite` on a device that just recovered with `recoverAccount` waits for
|
|
422
|
+
its member link instead of failing with "This device cannot reach its account
|
|
423
|
+
to check". (#540)
|
|
424
|
+
- A question sent while the previous run was still answering is shown to the
|
|
425
|
+
model after that answer, not before it, once compaction folds the earlier
|
|
426
|
+
turns. The run's reply and its file turns were sorted behind the new question,
|
|
427
|
+
and the model answered as if they came later (QVAC-24502). A file a run
|
|
428
|
+
produced is now replayed right behind that run's answer instead of at the end
|
|
429
|
+
of the chat; an existing chat with such a turn re-reads once after the update.
|
|
430
|
+
(#584)
|
|
431
|
+
|
|
432
|
+
## [0.11.0] - 2026-10-23
|
|
433
|
+
|
|
434
|
+
### Added
|
|
435
|
+
|
|
436
|
+
- `OAuthFlowDeps.onStage` reports `awaiting-callback` and `exchanging-code`, so a
|
|
437
|
+
host can log where a connect flow stopped. (#550)
|
|
438
|
+
- `deliverOAuthCallback(address)` in `@qvac/core/oauth` settles a waiting
|
|
439
|
+
sign-in from a callback address the user pastes, for a browser that cannot
|
|
440
|
+
reach the loopback. (#551)
|
|
441
|
+
|
|
442
|
+
### Changed
|
|
443
|
+
|
|
444
|
+
- The OAuth loopback done page tells the user to return to QV.AC to finish
|
|
445
|
+
connecting. (#550)
|
|
446
|
+
- The PDF page-image cap scales with the run's context window, between 2 and
|
|
447
|
+
32 pages, instead of a fixed 10. (#526)
|
|
448
|
+
|
|
449
|
+
### Fixed
|
|
450
|
+
|
|
451
|
+
- An OAuth connect whose provider stops answering now fails after 30 s instead
|
|
452
|
+
of waiting forever: the code exchange after the browser hands back the code
|
|
453
|
+
with `OAUTH_TOKEN_EXCHANGE_TIMEOUT`, and dynamic client registration, before
|
|
454
|
+
the browser opens, with `OAUTH_REGISTRATION_TIMEOUT`.
|
|
455
|
+
`OAuthFlowDeps.requestTimeoutMs` sets the limit per request. (#555)
|
|
456
|
+
- A PDF cut at the page-image cap tells the model the last page shown. (#525)
|
|
457
|
+
- Each user turn renders the same bytes on every request, so the chat's KV
|
|
458
|
+
cache is reused. (#528)
|
|
459
|
+
- Two devices that take turns to leave the account and pair back can both still
|
|
460
|
+
`meshInvite`. Before, the fourth pairing left a device refused with
|
|
461
|
+
`DEVICE_INVITE_CHAIN_TOO_LONG`. (#513)
|
|
462
|
+
- `joinMesh` no longer hangs when a device pairs back right after it unpaired,
|
|
463
|
+
while the removal its leave left behind is still being delivered. (#513)
|
|
464
|
+
|
|
465
|
+
## [0.10.4] - 2026-10-22
|
|
466
|
+
|
|
467
|
+
### Added
|
|
468
|
+
|
|
469
|
+
- A video attachment reaches the chat's model as up to 32 frames, sized to the
|
|
470
|
+
context window, with their times and a transcript of its audio track. The
|
|
471
|
+
first run stores them as an attachment chunk carrying `sourceId`, the video's
|
|
472
|
+
attachment id, which later turns and other devices read instead of the video;
|
|
473
|
+
an app should not render a chunk with `sourceId`. `uploadAttachment` takes
|
|
474
|
+
`sourceId` on its first frame. Core now depends on `bare-ffmpeg`. See
|
|
475
|
+
[attachments](docs/api/attachments.md) and [chunks](docs/api/chunks.md).
|
|
476
|
+
(#496)
|
|
477
|
+
- A `ctxSize`, `kvCacheK` or `kvCacheV` change reloads the agent's model on its
|
|
478
|
+
host 2.5 seconds after the last edit, if it is loaded, instead of on the
|
|
479
|
+
agent's next message. (#495)
|
|
480
|
+
|
|
481
|
+
### Changed
|
|
482
|
+
|
|
483
|
+
- `fileStatusWatch` reads only the chat's attachments, not every message in the
|
|
484
|
+
chat, on each refresh. (#518)
|
|
485
|
+
|
|
486
|
+
### Fixed
|
|
487
|
+
|
|
488
|
+
- A device that unpairs itself hands the agents it hosted to its member's
|
|
489
|
+
earliest-paired live device, in the account and every shared mesh, instead of
|
|
490
|
+
leaving them orphaned. A leave from an earlier release is handed over on the
|
|
491
|
+
next boot. (#514)
|
|
492
|
+
- On a harness in its own process, an image sent to a model without a projector
|
|
493
|
+
is no longer dropped silently: the run asks the harness about the chat's
|
|
494
|
+
model, and the turn says the image is not visible to it. (#494)
|
|
495
|
+
- A token saved for an agent reaches `skills` and `skillCatalog` readiness as
|
|
496
|
+
soon as it is written, instead of after the ten-minute credential refresh.
|
|
497
|
+
(#523)
|
|
498
|
+
- `duck` reopens the meshes it had saved when it starts. (#519)
|
|
499
|
+
|
|
500
|
+
## [0.10.3] - 2026-10-21
|
|
501
|
+
|
|
502
|
+
### Added
|
|
503
|
+
|
|
504
|
+
- `listAgentFolders`, `addAgentFolder` and `removeAgentFolder` share a folder on
|
|
505
|
+
this device with an agent, read only or read and write, so its file tools have
|
|
506
|
+
somewhere to work. They keep the `fs.<agentId>.roots` and
|
|
507
|
+
`fs.<agentId>.writable` config keys the assistant already reads, so a grant
|
|
508
|
+
written before keeps working. See
|
|
509
|
+
[agent folders](docs/api/agent-folders.md). (#445)
|
|
510
|
+
|
|
511
|
+
### Changed
|
|
512
|
+
|
|
513
|
+
- The runs a `deleteAgent` with `keepChats` cancels carry
|
|
514
|
+
`reason: 'agent-deleted'`, so an app can tell them from a run its user took
|
|
515
|
+
back and keep the message they answered. (#486)
|
|
516
|
+
- `deleteAgent` forgets the folders shared with the agent on this device. (#445)
|
|
517
|
+
|
|
518
|
+
### Fixed
|
|
519
|
+
|
|
520
|
+
- A borrowed run (`lenderDeviceId`) no longer acts on the lender's machine. The
|
|
521
|
+
lender serves it with no shared folders, with the `files` and `exec` toolsets
|
|
522
|
+
off, as none of its own agents, and with its KV caches kept apart; a borrowed
|
|
523
|
+
run gets no image or attachment. (#477)
|
|
524
|
+
- A device-invite `joinMesh` no longer lists a mesh it is leaving as closed, so
|
|
525
|
+
the app no longer reopens it and reports `MESH_NOT_FOUND` after pairing.
|
|
526
|
+
(#489)
|
|
527
|
+
|
|
528
|
+
## [0.10.2] - 2026-10-20
|
|
529
|
+
|
|
530
|
+
### Added
|
|
531
|
+
|
|
532
|
+
- `deleteAgent` takes `keepChats`, so an app can take an agent off a space
|
|
533
|
+
without deleting the conversations it answered there. They stay readable, and
|
|
534
|
+
`setChatAgent` hands each to another agent. The agent's open runs in them are
|
|
535
|
+
canceled. (`AssistantDeleteAgentRequest`) (#469)
|
|
536
|
+
|
|
537
|
+
### Changed
|
|
538
|
+
|
|
539
|
+
- `sendMessage` and `runAgent` refuse an agent that is deleted with
|
|
540
|
+
`AGENT_NOT_FOUND` instead of writing a run no device would claim. (#469)
|
|
541
|
+
|
|
542
|
+
### Fixed
|
|
543
|
+
|
|
544
|
+
- A device that pairs onto another account no longer lists its old workspace
|
|
545
|
+
beside the new one. An `openMesh` sent during the pair waits for it and is
|
|
546
|
+
refused with `MESH_NOT_FOUND` for a workspace the pair left. (#482)
|
|
547
|
+
- A device that pairs onto another account no longer renames that account's user
|
|
548
|
+
to the name it had before; it takes the account's name. (#475)
|
|
549
|
+
- An edited or reverted skill reaches chats that had already loaded it. A
|
|
550
|
+
skill write or delete clears the hosting device's KV caches and run replay
|
|
551
|
+
records, so each chat's next turn reloads the skill from disk; that turn
|
|
552
|
+
prefills cold (QVAC-26561). (#473)
|
|
553
|
+
- `duck`: `/models add` keeps a vision model's projector, so its images are no
|
|
554
|
+
longer dropped. (#480)
|
|
555
|
+
- `duck`: `/models use <name>` refuses a name that is neither an added model's
|
|
556
|
+
label or id nor an exact catalog or registry name, instead of setting it and
|
|
557
|
+
letting the harness load whatever file the registry search hit first, which
|
|
558
|
+
could be a vision projector. A path or URL is still set as given. (#481)
|
|
559
|
+
|
|
560
|
+
## [0.10.1] - 2026-10-19
|
|
561
|
+
|
|
562
|
+
### Added
|
|
563
|
+
|
|
564
|
+
- `QvacAssistant` takes `runIdleTimeoutMs`, how long a run's harness may send
|
|
565
|
+
nothing before the run fails. It defaults to 15 minutes. (#468)
|
|
566
|
+
|
|
567
|
+
### Changed
|
|
568
|
+
|
|
569
|
+
- `@qvac/harness` is now `^0.8.11` and `@qvac/skills` `^0.1.16`. (#468)
|
|
570
|
+
|
|
571
|
+
### Fixed
|
|
572
|
+
|
|
573
|
+
- A run whose harness goes silent fails with "the agent stopped responding"
|
|
574
|
+
instead of showing busy forever. A run parked on an approval does not count
|
|
575
|
+
as silent. (#468)
|
|
576
|
+
|
|
577
|
+
## [0.10.0] - 2026-10-16
|
|
578
|
+
|
|
579
|
+
### Added
|
|
580
|
+
|
|
581
|
+
- Core's refusals carry a registered `@qvac/error` code, so a caller matches
|
|
582
|
+
them with `isCoreError` from `@qvac/core/errors` instead of their message,
|
|
583
|
+
which is unchanged. Every route family has its codes (`CHAT_*`, `MESH_*`,
|
|
584
|
+
`INVITE_*`, `MEMBER_*`, `DEVICE_*`, `AGENT_*`, `UPLOAD_*`, `MODEL_*`, `OAUTH_*`
|
|
585
|
+
and the rest, exported from `@qvac/core/errors`), and a refusal from a hosting device reaches the caller with
|
|
586
|
+
its code. An older host sends none, so its refusal arrives as its message
|
|
587
|
+
alone. Each module's codes are in its file under
|
|
588
|
+
[`docs/api/`](docs/api/README.md). (#382, #383, #384, #385, #386, #387, #388)
|
|
589
|
+
- `Logger` from `@qvac/core/log` implements `@qvac/logging`'s
|
|
590
|
+
`LoggerInterface`, has `getLevel()`, and takes `logLevel: 'off'`. `Client`,
|
|
591
|
+
`QvacAssistant`, the assistant children and the model pushers take any
|
|
592
|
+
`LoggerInterface`, so a `QvacLogger` can be passed. (#389)
|
|
593
|
+
- `duck` indexes office attachments with the harness extractor. (#457)
|
|
594
|
+
|
|
595
|
+
### Changed
|
|
596
|
+
|
|
597
|
+
- **Breaking:** each `Core` writes only to the logger it is given, and one
|
|
598
|
+
created without a `logger` writes nothing, where it used to fall back to the
|
|
599
|
+
process-wide logger. Pass the logger to `Core`, `Client` and `QvacAssistant`.
|
|
600
|
+
(#389)
|
|
601
|
+
- `logSimilarityScores` from `@qvac/core/rag/similarity` writes only to the
|
|
602
|
+
logger passed as its third argument. (#389)
|
|
603
|
+
|
|
604
|
+
```js
|
|
605
|
+
logSimilarityScores(candidates, kept) // 0.9
|
|
606
|
+
logSimilarityScores(candidates, kept, logger) // 0.10
|
|
607
|
+
```
|
|
608
|
+
|
|
609
|
+
- **Breaking:** a compute mesh's dropped write is named
|
|
610
|
+
`COMPUTE_ROUTE_DROPPED`, where it was `ComputeRouteDropped`, and has no
|
|
611
|
+
`route` field. Match it by code. (#382)
|
|
612
|
+
|
|
613
|
+
```js
|
|
614
|
+
err.name === 'ComputeRouteDropped' // 0.9
|
|
615
|
+
isCoreError(err, 'COMPUTE_ROUTE_DROPPED') // 0.10
|
|
616
|
+
```
|
|
617
|
+
|
|
618
|
+
### Removed
|
|
619
|
+
|
|
620
|
+
- **Breaking:** `setLogger` and the `globalThis.logger` it set. (#389)
|
|
621
|
+
|
|
622
|
+
```js
|
|
623
|
+
setLogger(logger) // 0.9, then new Core(options)
|
|
624
|
+
new Core({ ...options, logger }) // 0.10
|
|
625
|
+
```
|
|
626
|
+
|
|
627
|
+
- **Breaking:** `LEVELS` from `@qvac/core/log`. Use `LEVEL_PRIORITIES` from
|
|
628
|
+
`@qvac/logging/constants`, which ranks the other way round: `error` is 0.
|
|
629
|
+
(#389)
|
|
630
|
+
|
|
631
|
+
```js
|
|
632
|
+
LEVELS[level] >= LEVELS.warn // 0.9
|
|
633
|
+
LEVEL_PRIORITIES[level] <= LEVEL_PRIORITIES.warn // 0.10
|
|
634
|
+
```
|
|
635
|
+
|
|
636
|
+
### Fixed
|
|
637
|
+
|
|
638
|
+
- An office file the agent host cannot decode reads `failed` with
|
|
639
|
+
`extractor unavailable on this device` in `fileStatusWatch`, and `ragSearch`
|
|
640
|
+
lists it in `failedFiles`, instead of staying pending forever and holding up
|
|
641
|
+
the run waiting on it. (#456)
|
|
642
|
+
- `updateMember` or `removeMember` called right after a join no longer fails
|
|
643
|
+
with `this device is in no member of its account`; it waits for the join to
|
|
644
|
+
land. (#391)
|
|
645
|
+
- A device that fast-forwards back onto a mesh lands without reading the view
|
|
646
|
+
in the update hook, as a joiner does. It used to scan every device, chat and
|
|
647
|
+
purged chat first. Chats deleted while it was away are found by the chat
|
|
648
|
+
order rebuild, purges by the device's own file index, and its own kick by
|
|
649
|
+
its own device row. (#465)
|
|
650
|
+
- A fast-forward no longer downloads every version of the view, and the
|
|
651
|
+
move-to sweep reads attachments only in the chats this device holds files
|
|
652
|
+
for, and knowledge rows whole, not every chat and attachment in the mesh. (#465)
|
|
653
|
+
- A linear update reads at most one old row per change. A revoked device or a
|
|
654
|
+
re-homed chat no longer scans every agent or a chat's whole history to find
|
|
655
|
+
its files, and the membership tally runs after the update instead of inside
|
|
656
|
+
it. (#465)
|
|
657
|
+
- A joiner no longer walks every chunk of the mesh it joined to backfill its
|
|
658
|
+
file index, and the backfill, the orphan sweep at every open and the purged
|
|
659
|
+
file reclaim read attachments chat by chat off an index instead of every
|
|
660
|
+
message. (#465)
|
|
661
|
+
- The view update hook only queues the update. A background pass syncs what
|
|
662
|
+
the device derives from the view, and folds updates that land while it runs
|
|
663
|
+
into one diff, so a streamed reply or a catch-up no longer walks once per
|
|
664
|
+
append, and the drain never waits on a peer for a block a side effect reads. (#465)
|
|
665
|
+
- The oldest view head a device has not synced is kept in the device-local
|
|
666
|
+
`@local/mesh-updates`, so a pass a close or crash cuts short resumes on the
|
|
667
|
+
next open instead of losing what it would have raised. (#465)
|
|
668
|
+
|
|
669
|
+
## [0.9.0] - 2026-10-15
|
|
670
|
+
|
|
671
|
+
### Changed
|
|
672
|
+
|
|
673
|
+
- **Breaking:** `meshInvite` mints a member invite as `qvac://workspace/…` and
|
|
674
|
+
a device invite as `qvac://device/…`, instead of `qvac://mesh/…`
|
|
675
|
+
(QVAC-26926). `joinMesh`, `previewMeshInvite` and `decodeMeshInvite` read all
|
|
676
|
+
three, so a link shared before still works, but a release before this one
|
|
677
|
+
refuses the new links with `Invalid mesh invite`: both sides of a join need
|
|
678
|
+
this version. An app that matches the prefix itself has to accept all three
|
|
679
|
+
before it takes this release, as tetherto/qvac-app#2535 does. (#394)
|
|
680
|
+
|
|
681
|
+
```js
|
|
682
|
+
const { invite } = await engine.meshInvite({ meshId, member: true })
|
|
683
|
+
// 0.8: qvac://mesh/… 0.9: qvac://workspace/…
|
|
684
|
+
const { invite: pairing } = await engine.meshInvite({})
|
|
685
|
+
// 0.8: qvac://mesh/… 0.9: qvac://device/…
|
|
686
|
+
```
|
|
687
|
+
|
|
688
|
+
## [0.8.0] - 2026-10-15
|
|
689
|
+
|
|
690
|
+
### Added
|
|
691
|
+
|
|
692
|
+
- `skillCatalog` entries carry `displayName`, the user-facing name and `@`
|
|
693
|
+
handle a skill's manifest declares, so an app can show Documents and
|
|
694
|
+
Spreadsheets for the `word` and `excel` skills without renaming them. (#392)
|
|
695
|
+
|
|
696
|
+
```js
|
|
697
|
+
const { skills } = await engine.skillCatalog({ agentId: agent.id })
|
|
698
|
+
const handle = skills.map((skill) => skill.displayName ?? skill.name)
|
|
699
|
+
```
|
|
700
|
+
|
|
701
|
+
- `meshStatusWatch` frames carry `blindPeersConnected` and `blindPeersTotal`,
|
|
702
|
+
the device's blind peers holding a connection of those it dials; a blind
|
|
703
|
+
peer connecting or dropping makes a frame. (#403)
|
|
704
|
+
- Every mesh lifecycle line carries where the mesh stood: `opening` names the
|
|
705
|
+
head it boots from (`null` is a replay from genesis), `autobee opened`,
|
|
706
|
+
`landed on the view`, `joined` and `closing` carry the local, system and
|
|
707
|
+
view lengths, the flushes, autobee's counters and the time since the open;
|
|
708
|
+
Core logs `mesh opened` with why (`route`, `follow`, `readmit`) and how long,
|
|
709
|
+
`followed the joined meshes` with its tally, and names the mesh it announces.
|
|
710
|
+
`diagnostics` returns the same counters under `stats.mesh.stats`. The two
|
|
711
|
+
seed lines (`seeded default agent`, `seeded first chat`) are debug: a rebuilt
|
|
712
|
+
view re-applies the genesis seed, and they read as a second seeding. (#403)
|
|
713
|
+
|
|
714
|
+
### Changed
|
|
715
|
+
|
|
716
|
+
- Joining a mesh reports joined as soon as the fast-forward lands, instead of
|
|
717
|
+
after a read of the whole view over the network. On a mesh with a long
|
|
718
|
+
history that read took tens of seconds, whatever the invite's head. The
|
|
719
|
+
member tally, mesh name, chat order and file index fill in moments after the
|
|
720
|
+
landing; a chat list in that window waits for the rebuild. (#400)
|
|
721
|
+
- The mesh logs `landed on the view` and `joined` with their timings, applies
|
|
722
|
+
and undos, and `device admitted` is a debug line: a catch-up re-applies every
|
|
723
|
+
claim on each re-linearisation. (#400)
|
|
724
|
+
- The meshes an account names open once the account's own join has settled,
|
|
725
|
+
instead of the moment the account lands, so they no longer compete with the
|
|
726
|
+
account's catch-up for the same peers. (#407)
|
|
727
|
+
|
|
728
|
+
### Fixed
|
|
729
|
+
|
|
730
|
+
- A mesh the account names on a sibling's behalf, opened with no head of its
|
|
731
|
+
own, fast-forwards onto the first head a sibling device offers, instead of
|
|
732
|
+
replaying from genesis until that device's row happened to land. The head's
|
|
733
|
+
own view carries the device's signed claim to the writer, and the account
|
|
734
|
+
says whose device that is. (#408)
|
|
735
|
+
- One blind-peering client per device, shared by every mesh and core. Each mesh
|
|
736
|
+
(and the config, recovery, departure and drive cores) built its own client,
|
|
737
|
+
all dialling under the device's one key, and a blind peer keeps one connection
|
|
738
|
+
per key: every connect by one mesh dropped another's, endlessly. A mesh's
|
|
739
|
+
invite still names the blind peers it is mirrored on; what is shared is the
|
|
740
|
+
connection to each. (#405)
|
|
741
|
+
- A device no longer dials every device in its account mesh directly on each
|
|
742
|
+
membership change; peers are found on the mesh topic. (#405)
|
|
743
|
+
- A device coming back after a long absence fast-forwards onto the new head
|
|
744
|
+
without diffing the whole view across cores: it reads the landed snapshot,
|
|
745
|
+
and the attachments deleted while it was away refresh on the sweep. On a mesh
|
|
746
|
+
with ~20k rows that jump took 110–150 s; it now takes a few seconds. (#399,
|
|
747
|
+
#402)
|
|
748
|
+
|
|
749
|
+
## [0.7.6] - 2026-10-14
|
|
750
|
+
|
|
751
|
+
### Added
|
|
752
|
+
|
|
753
|
+
- `duck`: `/tools` (and Menu ▸ Agent ▸ Tools) is back as the toolset switches, each
|
|
754
|
+
listing the tools it gates, read from the device the agent runs on. `/permissions`
|
|
755
|
+
keeps only the approval mode. (#380)
|
|
756
|
+
|
|
757
|
+
### Fixed
|
|
758
|
+
|
|
759
|
+
- `duck`: copying (ctrl+y, or a drag selection) works with no clipboard command, in
|
|
760
|
+
a container or over ssh. It asks the terminal to set the clipboard with OSC 52,
|
|
761
|
+
which the terminal has to allow, and `xsel` is tried after `wl-copy` and
|
|
762
|
+
`xclip`. (#395)
|
|
763
|
+
|
|
764
|
+
## [0.7.5] - 2026-10-13
|
|
765
|
+
|
|
766
|
+
### Fixed
|
|
767
|
+
|
|
768
|
+
- A reply cut off by a phone lock now restarts on unlock instead of ending as
|
|
769
|
+
failed (QVAC-24690). Between `presuspend` and `suspend` iOS refuses GPU work,
|
|
770
|
+
so the harness ends the turn with an error event or an abort of its own.
|
|
771
|
+
While the assistant is in the background that ending now replays the run
|
|
772
|
+
under the same `runId`, for chat and capability runs alike, and a run that
|
|
773
|
+
arrives in that window waits. A `resume` from `presuspend` starts both again.
|
|
774
|
+
A thrown error still fails the run, and a context overflow reported during
|
|
775
|
+
that window folds after the resume instead. (#368)
|
|
776
|
+
|
|
777
|
+
## [0.7.4] - 2026-10-13
|
|
778
|
+
|
|
779
|
+
### Added
|
|
780
|
+
|
|
781
|
+
- A mesh write still pending after five seconds, or a mesh's first drain
|
|
782
|
+
still pending after fifteen, logs a warning once: the ops a write carries,
|
|
783
|
+
the drain's counters, and every core the views read through that this device
|
|
784
|
+
holds only in part, with how many peers could serve it, and which blind peers
|
|
785
|
+
it has reached. Writes queued behind
|
|
786
|
+
the same stall do not repeat it, and it logs again when the stall settles or
|
|
787
|
+
the write fails. A drain parked on data no connected peer holds used to say
|
|
788
|
+
nothing, so a hung send, stop, delete or leave left no trace in an exported
|
|
789
|
+
log.
|
|
790
|
+
- Leaving a mesh logs when it starts, so an exported log shows the attempt even
|
|
791
|
+
when the leave never finishes. (#352)
|
|
792
|
+
|
|
793
|
+
- Model routes reach another device of this account (QVAC-25101). `listModels`,
|
|
794
|
+
`modelsWatch`, `loadModel`, `unloadModel`, `deleteModel`, `retryModelDownload`,
|
|
795
|
+
`clearModelDownload`, `modelUsers`, the custom-model routes and the model
|
|
796
|
+
watches take an optional `deviceId`, and Core runs the call on that device over
|
|
797
|
+
the `qvac/device-control` peer channel, so fit, memory, disk and the download
|
|
798
|
+
queue are that device's. Only a live device of this account's own member is
|
|
799
|
+
served, and a custom model added from another device must come from a link.
|
|
800
|
+
While the device is away a call rejects with `the device is not reachable`;
|
|
801
|
+
`meshStatusWatch`'s `peerDeviceIds` says when it is connected again. (#280)
|
|
802
|
+
|
|
803
|
+
```js
|
|
804
|
+
await engine.loadModel({ name: 'Qwen3.5-9B-Q4_K_M', deviceId: desktop.id })
|
|
805
|
+
```
|
|
806
|
+
|
|
807
|
+
- A phone changes a paired desktop's own model settings and pauses its
|
|
808
|
+
downloads. `configGet`, `configSet` and `configWatch` take an optional
|
|
809
|
+
`deviceId` and reach `model.idleUnloadMinutes` and `model.memoryCapPercent` on
|
|
810
|
+
that device; any other key is refused there, since the same store holds
|
|
811
|
+
integration tokens. `setModelPaused` takes `deviceId` too, so a download on the
|
|
812
|
+
desktop pauses there rather than on the phone, until the desktop restarts. (#359)
|
|
813
|
+
|
|
814
|
+
```js
|
|
815
|
+
import { MODEL_MEMORY_CAP_KEY } from '@qvac/core/constants'
|
|
816
|
+
|
|
817
|
+
await engine.configSet({ key: MODEL_MEMORY_CAP_KEY, value: 60, deviceId: desktop.id })
|
|
818
|
+
await engine.setModelPaused({ name: 'Qwen3.5-9B-Q4_K_M', paused: true, deviceId: desktop.id })
|
|
819
|
+
```
|
|
820
|
+
|
|
821
|
+
- `duck`: `/device use <n|name>` points every `/models` command at another
|
|
822
|
+
device of this account, and `/device list` shows each one, whether it is
|
|
823
|
+
connected and how many models it has downloaded. `/models idle`,
|
|
824
|
+
`/models cap` and `/models settings` set and show a device's idle limit and
|
|
825
|
+
memory cap, and `/models pause` / `/models resume` hold a download. (#360)
|
|
826
|
+
|
|
827
|
+
### Changed
|
|
828
|
+
|
|
829
|
+
- `loadModel`, `unloadModel`, `deleteModel`, `modelUsers`,
|
|
830
|
+
`clearModelDownload`, `retryModelDownload` and `removeCustomModel` had a
|
|
831
|
+
request of `name` alone; its new optional `deviceId` adds a flags byte, so
|
|
832
|
+
this Core cannot decode those calls from a `Client` of an earlier release
|
|
833
|
+
(`Out of bounds`). Upgrade the `Client` with the Core.
|
|
834
|
+
- `configGet`, `configWatch` and `configSet` gain the same flags byte with
|
|
835
|
+
their optional `deviceId`, so this Core cannot decode them from a `Client` of
|
|
836
|
+
an earlier release either. (#280, #359)
|
|
837
|
+
- `duck --join <invite>` now takes only a member invite, and the new `duck --device-join <invite>` takes only a device invite; each refuses the other's and names the right flag. `/join` previews say whether the current mesh is retired, and `/invite` says how the invitee joins. `/meshes` tags the account mesh as `home (your account)` and its footer says how to name a mesh. (#377)
|
|
838
|
+
|
|
839
|
+
### Fixed
|
|
840
|
+
|
|
841
|
+
- Suspending no longer logs every watch it closes as `watch failed` with a
|
|
842
|
+
bare `Stream was destroyed`. The assistant ended those streams itself, so
|
|
843
|
+
none of them failed.
|
|
844
|
+
- A log line that carries an error in its details, such as
|
|
845
|
+
`{ op, err }`, prints the error's stack instead of `{}`. A destroyed stream's
|
|
846
|
+
error records the code that destroyed it, so the log now says why it ended.
|
|
847
|
+
- A device lending its compute no longer crashes when the borrower drops a call
|
|
848
|
+
while the lender is still accepting it. Before, the dropped stream's error
|
|
849
|
+
went unhandled and took the lender's whole process down. (#355)
|
|
850
|
+
- `updateAgent` and `deleteAgent` stamp their write after the row it replaces,
|
|
851
|
+
so an edit or a delete made on a device whose clock runs behind the last
|
|
852
|
+
writer's is applied instead of dropped as stale. A dropped delete had still
|
|
853
|
+
deleted the agent's chats. (#358)
|
|
854
|
+
- `duck` started with a device invite no longer fails with
|
|
855
|
+
`This device cannot reach its account to check`. It asked for its own invite
|
|
856
|
+
while the join was still under way; it now waits for the join to finish.
|
|
857
|
+
|
|
858
|
+
## [0.7.3] - 2026-10-13
|
|
859
|
+
|
|
860
|
+
### Changed
|
|
861
|
+
|
|
862
|
+
- `MAX_AUDIO_ATTACHMENT_BYTES` (`@qvac/core/audio-format`) rises from 25 MiB to 100 MiB, matching `MAX_ATTACHMENT_BYTES`, so a client no longer refuses audio the mesh accepts. (#375)
|
|
863
|
+
|
|
864
|
+
## [0.7.2] - 2026-10-13
|
|
865
|
+
|
|
866
|
+
### Added
|
|
867
|
+
|
|
868
|
+
- `duck --join <invite>` (`-j`) joins a mesh invite at boot, so a `--headless` peer, which has no prompt to `/join` from, can get onto an existing mesh. A device invite pairs it into your account; a member invite adds a shared mesh to its own. (#371)
|
|
869
|
+
|
|
870
|
+
```sh
|
|
871
|
+
duck --headless --storage ~/duck-data --join qvac://mesh/…
|
|
872
|
+
```
|
|
873
|
+
|
|
874
|
+
- `/rename device <name>` names this device and `/rename member <name>` names you in every mesh at once, so a roster of `duck-<pid>` devices can be told apart. (#372)
|
|
875
|
+
|
|
876
|
+
## [0.7.1] - 2026-10-12
|
|
877
|
+
|
|
878
|
+
### Added
|
|
879
|
+
|
|
880
|
+
- `forkChat` copies a chat into a new one, through a turn or just before it, in
|
|
881
|
+
the same mesh or another (QVAC-26722). The source stays as it was, the fork
|
|
882
|
+
lands on top of its list with ids of its own, and `AssistantChat` names where
|
|
883
|
+
it came from in `forkedFrom`. Its files are its own copies, so removing one
|
|
884
|
+
in either chat leaves the other's, and into another mesh it needs one of that
|
|
885
|
+
mesh's agents. (#346)
|
|
886
|
+
|
|
887
|
+
```js
|
|
888
|
+
const fork = await engine.forkChat({ meshId, chatId, runId: reply.runId })
|
|
889
|
+
```
|
|
890
|
+
|
|
891
|
+
- `setBlindPeering` and `blindPeeringWatch` turn every blind peering on this
|
|
892
|
+
device off or back on, kept across restarts, for reproducing sync with no
|
|
893
|
+
mirror in the middle. `diagnostics` reports it as `stats.mesh.blindPeering`,
|
|
894
|
+
and a `recoveryPublish` made while it is off does not mark the account
|
|
895
|
+
recoverable. (#334)
|
|
896
|
+
|
|
897
|
+
```js
|
|
898
|
+
await engine.setBlindPeering({ enabled: false })
|
|
899
|
+
```
|
|
900
|
+
|
|
901
|
+
### Changed
|
|
902
|
+
|
|
903
|
+
- `@qvac/harness` is `^0.8.7` and `@qvac/skills` 0.1.14, which bring the
|
|
904
|
+
`browser` skill. Every run now hands the harness its chat as `session`, with
|
|
905
|
+
or without a cache key, so a skill whose manifest declares
|
|
906
|
+
`${session}` in its `env` keeps one resource per chat, such as the browser
|
|
907
|
+
the `browser` skill drives. (#369)
|
|
908
|
+
- `createAgent` and `updateAgent` ignore `toolsScope` and `enabledTools` and
|
|
909
|
+
always store `toolsScope: 'all'`, leaving `disabledToolsets` as the only
|
|
910
|
+
per-agent gate on tools. Each mesh rewrites its stored `selected` agents to
|
|
911
|
+
`all` once on open, so an agent saved with an empty list runs with its tools
|
|
912
|
+
again. (#363)
|
|
913
|
+
|
|
914
|
+
### Fixed
|
|
915
|
+
|
|
916
|
+
- The harness is handed the turn as typed, so a skill mention or a search ask
|
|
917
|
+
is read from what the user wrote, not from attached documents, knowledge or
|
|
918
|
+
sender lines wrapped around it (QVAC-24963). Before,
|
|
919
|
+
`@pdf Summarize these docs` with a PDF attached could load
|
|
920
|
+
`image-generation`, and a document saying "search the web" went out as the
|
|
921
|
+
search query. (#347)
|
|
922
|
+
- The model downloader picks the text-to-speech model for the profile the
|
|
923
|
+
hardware probe found, the same one speaking asks for (QVAC-25679). Before, a
|
|
924
|
+
new device could plan its downloads while its row still held the host's seed
|
|
925
|
+
profile and keep that for the session, so a "mid" or higher device fetched
|
|
926
|
+
`Supertonic3-Q4_0` while read aloud waited for `Supertonic3-FP16` and stayed
|
|
927
|
+
disabled until a restart. If the probe fails, it plans for "low", the voice
|
|
928
|
+
the harness then speaks with. (#367)
|
|
929
|
+
- A device dials the other devices of its account by key as well as finding
|
|
930
|
+
them on the mesh topic, and dials them again on resume. Before, a topic
|
|
931
|
+
refresh that missed after a suspend or a network change left a phone without
|
|
932
|
+
its Mac for ten minutes or more, so a chat with an agent the Mac hosted sat
|
|
933
|
+
on "waiting to reconnect" though both were online. (#327)
|
|
934
|
+
- `removeDevice` on a device of our own member moves the agents it hosted to
|
|
935
|
+
the device that removed it, in that mesh and, for a removal from the account,
|
|
936
|
+
in every shared mesh of ours it is revoked in, so a run waiting on the removed
|
|
937
|
+
device runs there; a removal made on an earlier build is caught up on the
|
|
938
|
+
next boot. Before, the agents stayed orphaned and the chat waited forever.
|
|
939
|
+
(#327)
|
|
940
|
+
|
|
941
|
+
## [0.7.0] - 2026-10-09
|
|
942
|
+
|
|
943
|
+
### Added
|
|
944
|
+
|
|
945
|
+
- Model downloads can wait to be asked for, so a phone on cellular does not
|
|
946
|
+
fetch gigabytes on its own. Pass `autoDownloadModels: false` to the Core
|
|
947
|
+
constructor so it holds from the first boot, or toggle it later. A run that
|
|
948
|
+
needs a missing model then waits as `awaiting-download` instead of fetching it,
|
|
949
|
+
and so do image, music, transcription, speech and embedding loads in the
|
|
950
|
+
harness (#332, #333):
|
|
951
|
+
|
|
952
|
+
```js
|
|
953
|
+
await engine.setAutoDownloadModels({ enabled: false })
|
|
954
|
+
for await (const { downloads } of engine.modelDownloadsWatch({})) {
|
|
955
|
+
const held = (downloads ?? []).find((row) => row.phase === 'held')
|
|
956
|
+
if (held) {
|
|
957
|
+
await engine.retryModelDownload({ name: held.name })
|
|
958
|
+
break
|
|
959
|
+
}
|
|
960
|
+
}
|
|
961
|
+
```
|
|
962
|
+
|
|
963
|
+
- The OAuth loopback serves callbacks under Bare too, so a mobile worklet can
|
|
964
|
+
complete sign-in on the same `127.0.0.1` redirect desktop registers. (#329)
|
|
965
|
+
- `openOAuthLoopback` takes an optional `returnTo`: the callback redirects the
|
|
966
|
+
browser there instead of showing the done page. (#329)
|
|
967
|
+
- Several models stay loaded when memory allows (QVAC-25735). On desktop the
|
|
968
|
+
assistant pushes `model.memoryCapPercent` to the harness: loaded models may
|
|
969
|
+
fill that share of the memory usable for models, 85% by default, so two chat
|
|
970
|
+
models that fit stay loaded and switching chats between them loads neither
|
|
971
|
+
again. A load that would not fit unloads idle models one at a time, other
|
|
972
|
+
kinds before chat models and the least recently used first. It applies with
|
|
973
|
+
no restart; the minimum keeps one chat model loaded, and a mobile device
|
|
974
|
+
always does. `listModels` and `modelsWatch` carry the device's `memory`
|
|
975
|
+
(`usableBytes`, `capPercent`, `capBytes`, `usedBytes`, and `overCap` when a
|
|
976
|
+
model larger than the cap loaded anyway) and each loaded row its
|
|
977
|
+
`memoryBytes`, so a Models screen shows used against the cap. Needs the
|
|
978
|
+
`@qvac/harness` release with `setModelMemoryCap` and `memoryUsage`; an older
|
|
979
|
+
one keeps one chat model loaded and lists no `memory`. (#343)
|
|
980
|
+
|
|
981
|
+
```js
|
|
982
|
+
import { MODEL_MEMORY_CAP_KEY } from '@qvac/core/constants'
|
|
983
|
+
|
|
984
|
+
await engine.configSet({ key: MODEL_MEMORY_CAP_KEY, value: 70 })
|
|
985
|
+
const { memory } = await engine.listModels({ cachedOnly: true })
|
|
986
|
+
```
|
|
987
|
+
|
|
988
|
+
- A device pairs and follows its member with no other device online. A device
|
|
989
|
+
invite carries a keypair attested into the inviter's member, so the joiner
|
|
990
|
+
links itself, and the account holds every shared mesh's seed (the new
|
|
991
|
+
`@qvac/put-mesh-seed` route), so a new device opens them all from a blind
|
|
992
|
+
peer alone. A device invite minted by 0.6.6 still admits a device but no
|
|
993
|
+
longer links it into the member. `meshInvite` refuses a device invite from a
|
|
994
|
+
device whose proof chain is too long to extend, naming another device or the
|
|
995
|
+
phrase instead. (#342)
|
|
996
|
+
- `diagnostics` carries `backendUse`: per tool, the backends its recent runs
|
|
997
|
+
on this device reported, newest last. A run that asked for the gpu and ran
|
|
998
|
+
on the cpu is the fallback to look for. (#22)
|
|
999
|
+
|
|
1000
|
+
```js
|
|
1001
|
+
const { stats } = await engine.diagnostics({})
|
|
1002
|
+
stats.backendUse.generate_music.at(-1)
|
|
1003
|
+
// { requestedGpu: true, device: 'cpu', backend: 'cpu' }
|
|
1004
|
+
```
|
|
1005
|
+
|
|
1006
|
+
- `duck`: `/doctor` checks this device (hardware, engine, model backends, mesh,
|
|
1007
|
+
network) and `/doctor debug` shows the raw diagnostics frame behind it.
|
|
1008
|
+
`ctrl+y` copies either as plain text, with the mesh seed and any invite
|
|
1009
|
+
redacted and keys truncated. (#22)
|
|
1010
|
+
|
|
1011
|
+
### Changed
|
|
1012
|
+
|
|
1013
|
+
- An invite is a password again, as it was before 0.5.0. A member invite mints
|
|
1014
|
+
no grant and a device invite no expiring token: either link is the mesh
|
|
1015
|
+
seed, reusable for good, and the joining device admits itself with the new
|
|
1016
|
+
`@qvac/open-join` route; `joinMesh` and `recoverAccount` return once the
|
|
1017
|
+
join is recorded, appending it in the background, with the account reporting
|
|
1018
|
+
`joining` until the mesh reaches it. A device invite pairs with the inviting
|
|
1019
|
+
device offline, and `recoverAccount` needs no other device online. A removed
|
|
1020
|
+
device comes back the next time it joins. Every route that shipped keeps its
|
|
1021
|
+
0.6.6 meaning, and a 0.6.6 or 0.6.7 replica halts on the new one, so this
|
|
1022
|
+
raises the floor to `>=0.19.1`. (#342)
|
|
1023
|
+
|
|
1024
|
+
```js
|
|
1025
|
+
const { invite } = await engine.meshInvite({ member: true })
|
|
1026
|
+
await engine.joinMesh({ invite }) // any number of times, by anyone holding it
|
|
1027
|
+
```
|
|
1028
|
+
|
|
1029
|
+
- `joinMesh` and `recoverAccount` fail with "This device has no device
|
|
1030
|
+
details: pass `device` when creating Core" on a Core created without
|
|
1031
|
+
`device` and with none stored, and a `meshSeed` boot reports it as its
|
|
1032
|
+
status error: a mesh admits only a device it can list and remove. (#342)
|
|
1033
|
+
|
|
1034
|
+
- A mesh still `joining` refuses a write into it at once with "This mesh is
|
|
1035
|
+
still joining: it accepts writes once it is joined", since nothing written
|
|
1036
|
+
there reaches disk until a peer serves the mesh. Reads keep working; retry
|
|
1037
|
+
the write once the mesh lists `joined`. (#342)
|
|
1038
|
+
|
|
1039
|
+
- `listMeshes` and `meshesWatch` rows no longer set `reason` or
|
|
1040
|
+
`awaitingFrom`: no other device admits a joining one any more. Read
|
|
1041
|
+
`state: 'joining'` alone. (#342)
|
|
1042
|
+
|
|
1043
|
+
### Deprecated
|
|
1044
|
+
|
|
1045
|
+
- `meshEntry.reason` and `meshEntry.awaitingFrom`, which are never set. (#342)
|
|
1046
|
+
|
|
1047
|
+
### Removed
|
|
1048
|
+
|
|
1049
|
+
- The `grantWritableMs`, `grantVisibleMs` and `accountWritableMs` Core options.
|
|
1050
|
+
Nothing on a join, a mint or a logout waits for a mesh to go writable any
|
|
1051
|
+
more: a departure the mesh cannot take yet is revoked by the departures
|
|
1052
|
+
outbox once it can, and a mesh minted before the account can write is
|
|
1053
|
+
registered there once it can. (#342)
|
|
1054
|
+
|
|
1055
|
+
### Fixed
|
|
1056
|
+
|
|
1057
|
+
- A chat's KV cache no longer grows by duplicated history: each run is replayed
|
|
1058
|
+
to the model exactly as it was sent. (#338)
|
|
1059
|
+
- A chat handed to another agent on the same device, by `setChatAgent` or a
|
|
1060
|
+
`sendMessage` naming another `agentId`, no longer leaves the old agent's KV
|
|
1061
|
+
cache file on disk until the chat is deleted. (#330)
|
|
1062
|
+
- Reopening the account mesh after its local database died clears "the local
|
|
1063
|
+
database died" error once the reopened mesh is healthy. (#340)
|
|
1064
|
+
- `duck`: `/agent new` gives the new agent a real model in a mesh with no agent
|
|
1065
|
+
yet, and `/agent use` hands the open chat to the agent it selects. (#348, #331)
|
|
1066
|
+
|
|
1067
|
+
## [0.6.7] - 2026-10-06
|
|
1068
|
+
|
|
1069
|
+
### Added
|
|
1070
|
+
|
|
1071
|
+
- A `quack` model for testing mesh, sync and chat flows without inference. An
|
|
1072
|
+
agent on it replies with `quack` repeated 1 to 500 times, counted from a hash
|
|
1073
|
+
of the last user turn, so the same prompt always gets the same reply. Every
|
|
1074
|
+
other model still runs on the real harness. The device-local
|
|
1075
|
+
`debug.fakeModels` key (`FAKE_MODELS_KEY` in `@qvac/core/constants`, beside the `QUACK_MODEL` name) turns it
|
|
1076
|
+
on and off live, which is what an app's Debug toggle writes. `assistantChild`
|
|
1077
|
+
and `assistantTree` take `fakeModels: true` to force it on, which is what duck
|
|
1078
|
+
does with its `--fake-models` flag or `QVAC_FAKE_MODELS=1`.
|
|
1079
|
+
|
|
1080
|
+
```js
|
|
1081
|
+
await engine.configSet({ key: FAKE_MODELS_KEY, value: true })
|
|
1082
|
+
```
|
|
1083
|
+
|
|
1084
|
+
```sh
|
|
1085
|
+
QVAC_MODEL=quack duck --temp --fake-models
|
|
1086
|
+
```
|
|
1087
|
+
|
|
1088
|
+
- `Core` accepts `store`, `swarm` and `wakeup`, so a host that is already a
|
|
1089
|
+
peer-to-peer application passes the ones it runs rather than having Core
|
|
1090
|
+
stand up a second of each. Core never closes, destroys or suspends what it
|
|
1091
|
+
was passed, takes the device identity from a passed swarm's keypair, and
|
|
1092
|
+
leaves replication and wakeup on a passed swarm to the host. `swarm`
|
|
1093
|
+
requires `store` and `wakeup`. The host suspends Core before its store, and
|
|
1094
|
+
resumes its store before resuming or closing Core. `storagePath` is
|
|
1095
|
+
unchanged and still holds the device-local database. See
|
|
1096
|
+
[the decision record](docs/decisions/2026-09-28-a-host-passes-core-its-corestore-and-swarm.md).
|
|
1097
|
+
|
|
1098
|
+
```js
|
|
1099
|
+
const core = new Core(transport, {
|
|
1100
|
+
storagePath,
|
|
1101
|
+
store: host.rootCorestore.namespace('qvac'),
|
|
1102
|
+
swarm: host.swarm,
|
|
1103
|
+
wakeup: host.wakeup
|
|
1104
|
+
})
|
|
1105
|
+
```
|
|
1106
|
+
|
|
1107
|
+
(#303)
|
|
1108
|
+
|
|
1109
|
+
### Changed
|
|
1110
|
+
|
|
1111
|
+
- `@qvac/skills` is pinned at 0.1.11. 0.1.12 grants the `pptx`, `docx`, `xlsx`
|
|
1112
|
+
and `transcribe_music` tools, which `@qvac/harness` does not register yet, so
|
|
1113
|
+
a range would let a fresh install read presentations, word and excel as
|
|
1114
|
+
unsupported. (#321)
|
|
1115
|
+
|
|
1116
|
+
### Fixed
|
|
1117
|
+
|
|
1118
|
+
- The assistant reports readiness for an agent newly hosted in the account as
|
|
1119
|
+
soon as it lands there, as it already did in a shared mesh, so a credential
|
|
1120
|
+
handed off to an agent created from another device no longer waits on it.
|
|
1121
|
+
(#320)
|
|
1122
|
+
|
|
1123
|
+
## [0.6.6] - 2026-10-05
|
|
1124
|
+
|
|
1125
|
+
### Changed
|
|
1126
|
+
|
|
1127
|
+
- The consensus floor, `VENDORED_MIN_SUPPORTED_VERSION`, is back to `>=0.19.0`.
|
|
1128
|
+
The app ships the #308 apply change in 0.19, so that release is the floor; at
|
|
1129
|
+
`>=0.20.0` a 0.19 build would withhold itself from its own meshes. (#317)
|
|
1130
|
+
|
|
1131
|
+
## [0.6.5] - 2026-10-01
|
|
1132
|
+
|
|
1133
|
+
### Added
|
|
1134
|
+
|
|
1135
|
+
- `setMeshName` names a mesh for every member in it. `setMeshLabel` only
|
|
1136
|
+
names it for the member who set it, so someone who joined a shared mesh read
|
|
1137
|
+
it unnamed. `listMeshes` and `meshesWatch` rows carry the shared name as
|
|
1138
|
+
`name`, and `meshesWatch` emits when another member renames the mesh. A build
|
|
1139
|
+
older than this one halts on the new `name-mesh` op, so every member's devices
|
|
1140
|
+
need this release before a mesh is named.
|
|
1141
|
+
|
|
1142
|
+
```js
|
|
1143
|
+
await engine.setMeshName({ meshId, name: 'Design team' })
|
|
1144
|
+
const { meshes } = await engine.listMeshes({})
|
|
1145
|
+
meshes.find((mesh) => mesh.meshId === meshId).name // 'Design team', on every member
|
|
1146
|
+
```
|
|
1147
|
+
|
|
1148
|
+
(#310)
|
|
1149
|
+
|
|
1150
|
+
- `moveChatToMesh` moves a chat to another mesh with its files and its running
|
|
1151
|
+
turn: the copy lands at once under `targetChatId`, the turn is retried there,
|
|
1152
|
+
and the source is purged once every file has arrived. `chatMoveWatch` reports
|
|
1153
|
+
the move, and `setChatAgent` hands a chat to another agent of its mesh. Until
|
|
1154
|
+
its bytes arrive, a moved attachment's `blobId` is `PENDING_BLOB_REFERENCE`,
|
|
1155
|
+
which `downloadAttachment` rejects with `blob unavailable`. (#312)
|
|
1156
|
+
- `chunksDeltaWatch` streams an open chat as changes: a `reset` with the whole
|
|
1157
|
+
selection first, then only the rows appended, edited or reordered, and the ids
|
|
1158
|
+
of rows that left. A transcript that re-rendered the whole chat on every
|
|
1159
|
+
streamed chunk pays for one row per chunk instead; `chunksWatch` is
|
|
1160
|
+
unchanged. (#314)
|
|
1161
|
+
|
|
1162
|
+
### Changed
|
|
1163
|
+
|
|
1164
|
+
- The consensus floor, `VENDORED_MIN_SUPPORTED_VERSION`, is `>=0.20.0`. How a
|
|
1165
|
+
re-paired device's removal is weighed changed in apply, so a device on an
|
|
1166
|
+
older build would read a shared mesh differently. Ship the 0.20 app before
|
|
1167
|
+
publishing this floor to the lane cores. (#308)
|
|
1168
|
+
- `@qvac/harness` is `^0.7.2`. `web_fetch` attaches a plain-text file it
|
|
1169
|
+
fetched to the chat beside returning its text, and devices on the `mid`
|
|
1170
|
+
profile and up speak with `Supertonic3-FP16` at 16 steps instead of
|
|
1171
|
+
`Supertonic3-Q8_0` at 5, so a host that prefetches the infra models downloads
|
|
1172
|
+
the FP16 model once. (#311)
|
|
1173
|
+
|
|
1174
|
+
### Fixed
|
|
1175
|
+
|
|
1176
|
+
- A device unpaired and paired back gets every project back, however its
|
|
1177
|
+
removal synced, and one that left a shared mesh on its own comes back as soon
|
|
1178
|
+
as it asks; only another member's removal still needs a grant. A re-paired
|
|
1179
|
+
device still live on its old writer is moved onto its new one instead of
|
|
1180
|
+
staying a reader, and a late leave no longer turns a kick into a leave. A
|
|
1181
|
+
consensus change, covered by the `>=0.20.0` floor. (#308)
|
|
1182
|
+
- A member re-invited to a mesh it left brings every device back, not only the
|
|
1183
|
+
one that redeemed the invite. A device asking its siblings to admit it asks
|
|
1184
|
+
again, about once a second for up to a minute, while they are mid-join,
|
|
1185
|
+
instead of waiting as a reader until the next restart. (#307)
|
|
1186
|
+
- `leaveMesh` on the account is no longer refused while this device holds
|
|
1187
|
+
another mesh: it departs each of them as this device alone, then leaves the
|
|
1188
|
+
account. Unpairing a device that held a project did nothing. (#306)
|
|
1189
|
+
- `chatActivityWatch` no longer fails on every tick after a fast-forward leaves
|
|
1190
|
+
its cached view head undiffable. It rebuilds from the current view instead;
|
|
1191
|
+
before, the error repeated until restart. (#301)
|
|
1192
|
+
- `modelCatalogWatch` bumps only when the custom-model set changed. It bumped on
|
|
1193
|
+
every device-local write, several times a second while a reply streamed. (#300)
|
|
1194
|
+
- A typed harness can ask `fetchAttachment` for the newest audio. (#309)
|
|
1195
|
+
- PDF extraction works on Android again: `bare-pdfium` 1.5.5 links its C++
|
|
1196
|
+
runtime into the addon, which 1.5.4's prebuilds left undefined. (#305)
|
|
1197
|
+
|
|
16
1198
|
## [0.6.4] - 2026-09-30
|
|
17
1199
|
|
|
18
1200
|
### Removed
|
|
@@ -1159,7 +2341,29 @@ Published under the `release-0.1` dist-tag.
|
|
|
1159
2341
|
await assistant.ready()
|
|
1160
2342
|
```
|
|
1161
2343
|
|
|
1162
|
-
[Unreleased]: https://github.com/tetherto/qvac-core/compare/v0.
|
|
2344
|
+
[Unreleased]: https://github.com/tetherto/qvac-core/compare/v0.11.4...HEAD
|
|
2345
|
+
[0.11.4]: https://github.com/tetherto/qvac-core/compare/v0.11.3...v0.11.4
|
|
2346
|
+
[0.11.3]: https://github.com/tetherto/qvac-core/compare/v0.11.2...v0.11.3
|
|
2347
|
+
[0.11.2]: https://github.com/tetherto/qvac-core/compare/v0.11.1...v0.11.2
|
|
2348
|
+
[0.11.1]: https://github.com/tetherto/qvac-core/compare/v0.11.0...v0.11.1
|
|
2349
|
+
[0.11.0]: https://github.com/tetherto/qvac-core/compare/v0.10.4...v0.11.0
|
|
2350
|
+
[0.10.4]: https://github.com/tetherto/qvac-core/compare/v0.10.3...v0.10.4
|
|
2351
|
+
[0.10.3]: https://github.com/tetherto/qvac-core/compare/v0.10.2...v0.10.3
|
|
2352
|
+
[0.10.2]: https://github.com/tetherto/qvac-core/compare/v0.10.1...v0.10.2
|
|
2353
|
+
[0.10.1]: https://github.com/tetherto/qvac-core/compare/v0.10.0...v0.10.1
|
|
2354
|
+
[0.10.0]: https://github.com/tetherto/qvac-core/compare/v0.9.0...v0.10.0
|
|
2355
|
+
[0.9.0]: https://github.com/tetherto/qvac-core/compare/v0.8.0...v0.9.0
|
|
2356
|
+
[0.8.0]: https://github.com/tetherto/qvac-core/compare/v0.7.6...v0.8.0
|
|
2357
|
+
[0.7.6]: https://github.com/tetherto/qvac-core/compare/v0.7.5...v0.7.6
|
|
2358
|
+
[0.7.5]: https://github.com/tetherto/qvac-core/compare/v0.7.4...v0.7.5
|
|
2359
|
+
[0.7.4]: https://github.com/tetherto/qvac-core/compare/v0.7.3...v0.7.4
|
|
2360
|
+
[0.7.3]: https://github.com/tetherto/qvac-core/compare/v0.7.2...v0.7.3
|
|
2361
|
+
[0.7.2]: https://github.com/tetherto/qvac-core/compare/v0.7.1...v0.7.2
|
|
2362
|
+
[0.7.1]: https://github.com/tetherto/qvac-core/compare/v0.7.0...v0.7.1
|
|
2363
|
+
[0.7.0]: https://github.com/tetherto/qvac-core/compare/v0.6.7...v0.7.0
|
|
2364
|
+
[0.6.7]: https://github.com/tetherto/qvac-core/compare/v0.6.6...v0.6.7
|
|
2365
|
+
[0.6.6]: https://github.com/tetherto/qvac-core/compare/v0.6.5...v0.6.6
|
|
2366
|
+
[0.6.5]: https://github.com/tetherto/qvac-core/compare/v0.6.4...v0.6.5
|
|
1163
2367
|
[0.6.4]: https://github.com/tetherto/qvac-core/compare/v0.6.3...v0.6.4
|
|
1164
2368
|
[0.6.3]: https://github.com/tetherto/qvac-core/compare/v0.6.2...v0.6.3
|
|
1165
2369
|
[0.6.2]: https://github.com/tetherto/qvac-core/compare/v0.6.1...v0.6.2
|