Skip to content

docs: move (since vNEXT) tags out of markdown headings #697

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
padak merged 1 commit into from
Aug 25, 2026
Merged

docs: move (since vNEXT) tags out of markdown headings #697

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 7 additions & 5 deletions plugins/kbagent/skills/kbagent/references/gotchas.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1337,7 +1337,9 @@ events and emits a final `done` SSE frame mirroring the same record.
components sharing a config ID, a deleted parent config, or a failed lookup
all yield `""` rather than a guess. A blank name never means the
subscription is inactive.
## Notification subscriptions can now be written, and the write path has sharp edges (since vNEXT)
## Notification subscriptions can now be written, and the write path has sharp edges

*(since vNEXT)*

- **`notification replace-recipient` always mints a NEW `subscription_id`.**
The Notification Service has **no update primitive** -- there is no PATCH or
Expand Down Expand Up @@ -4558,9 +4560,9 @@ shapes.
today a deny policy gates only `/auth/*`, not the ~30 other routers a
session token can otherwise reach.

## `serve` honors the root-level `--config-dir` (since vNEXT)
## `serve` honors the root-level `--config-dir`

`serve` is the only subcommand carrying a `--config-dir` of its own, so the
*(since vNEXT)* `serve` is the only subcommand carrying a `--config-dir` of its own, so the
flag has two possible positions. The precedence is **most specific wins**,
matching what `kbagent repl` does with the root flags:

Expand All @@ -4583,9 +4585,9 @@ resolution is left to the server, which lands on the same directory anyway.
-- if the aliases are not the ones in the directory you named, the flag was
in the position your version ignores.

## `workspace load` now auto-CLONEs eligible tables instead of always COPYing (since vNEXT, closes #687)
## `workspace load` now auto-CLONEs eligible tables instead of always COPYing

Before this, `workspace load` always sent a plain `copy` (the API's own
*(since vNEXT, closes #687)* Before this, `workspace load` always sent a plain `copy` (the API's own
default when `loadType` is omitted) -- a 282 GB table load burned warehouse
credits for hours where `clone` is metadata-only and finishes in seconds.
kbagent now mirrors the server's `LoadTypeDecider` per table.
Expand Down
4 changes: 2 additions & 2 deletions plugins/kbagent/skills/kbagent/references/workspace-workflow.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -91,9 +91,9 @@ kbagent --json workspace query \
--sql "SELECT * FROM \"table1\" LIMIT 10"
```

## Load types: clone / copy / view (since vNEXT, #687)
## Load types: clone / copy / view

`workspace load` supports three load types. **Default (no `--load-type`)**:
*(since vNEXT, #687)* `workspace load` supports three load types. **Default (no `--load-type`)**:
kbagent decides per table, mirroring the server's own eligibility rules --
zero-copy `clone` when the table is on the same backend as the workspace
with a full (unfiltered) load and no external-schema/Analytics-Hub source
Expand Down