Brace groups follow bash: no comma or sequence means literal

PARITY.md

@@ -257,6 +257,13 @@ the skip rules (configured `ignore` plus the built-in `node_modules/**` and
 by `db::query` and the `dirsql_path` module). All three SDKs and the CLI get the
 same answers with no per-binding surface and no SDK signature changes.
 
+**Path-table braces follow bash brace expansion (#1262) — parity by
+construction, no drift.** A comma group alternates, a `..` range expands, and
+any other brace is literal text. The expansion runs in the shared Rust core
+(`brace::expand`, called by `scanner::compile_glob`), so all three SDKs and the
+CLI match the same files with no per-binding surface and no SDK signature
+changes. Config `[[table]] glob` does not use it yet.
+
 **Gitignore-by-default in path-tables (#742) — at parity, opt-out
 restored (#745/#746).** Path-table scans respect `.gitignore` files by default
 (hierarchical, traversal-pruned, hidden files still scanned). The *behavior*

docs/reference/path-tables.md

@@ -54,6 +54,13 @@ depth, as in the shell. A trailing `/` is `*` appended, so `'./*/'` is
 A path containing `*`, `?`, `[` or `{` is a glob and is used exactly as
 written: `*` matches within a single directory, `**` crosses directories.
 
+Braces expand as bash expands them. A group holding a comma is an
+alternation: `'./docs/{a,b}.md'` is `docs/a.md` and `docs/b.md`, and groups
+nest. A group holding a `..` range counts: `'./log/{1..3}.txt'`,
+`'./{a..c}.md'`, `'./{01..10}.md'` (zero-padded) and `'./{1..10..2}.md'`
+(every second value). Any other brace is literal text, so `'./br/{q}.md'`
+names the file `br/{q}.md`, and `\{` is always a literal brace.
+
 The scan starts at the last directory named outright before the first glob
 component, and descends only as deep as the pattern can match --
 `'./small/*.md'` lists `small/` and nothing else -- so a query over one

packages/python/changelog.d/2026-10-05-brace-groups-follow-bash.md

@@ -0,0 +1,6 @@
+**Changed** Braces in a path-table follow bash brace expansion. A group with
+a top-level comma (`{a,b}`, nested allowed) is an alternation, and a `..`
+range (`{1..3}`, `{a..c}`, `{01..10}`, `{1..10..2}`) expands to each value.
+Any other brace is literal text: `'./br/{q}.md'` names the file `br/{q}.md`
+where it used to match `br/q.md`, and `{` or `}` without a partner no longer
+fails to compile. Config `[[table]] glob` is unchanged.

packages/python/e2e-attestations/claude-1262-brace-literal.json

@@ -0,0 +1,7 @@
+{
+  "command": "just test-e2e",
+  "ran_at": 1791240509,
+  "exit_code": 0,
+  "commit": "42886c665ab14434f259593bf7868455cf206eda",
+  "branch": "claude/1262-brace-literal"
+}

packages/python/migrations.d/2026-10-05-brace-groups-follow-bash.md

@@ -0,0 +1,39 @@
+### Core: path-table braces follow bash brace expansion
+
+#### Summary
+
+A path-table's braces now expand as bash expands them before globbing: a
+group with a top-level comma is an alternation, a `..` range expands to each
+value, and every other brace is literal text. `'./br/{q}.md'` used to match
+`br/q.md` and now matches only a file named `br/{q}.md`; `'./a{1..3}.md'`
+used to match nothing and now matches `a1.md`, `a2.md`, `a3.md`. Comma groups
+behave as before. Every surface that resolves a path-table is affected (CLI,
+REPL, HTTP server, SDKs, `--on-file`); config `[[table]] glob` is not.
+
+#### Required changes
+
+| Surface | Before | After |
+| ------- | ------ | ----- |
+| One-option group | `SELECT * FROM './br/{q}.md'` (matched `br/q.md`) | `SELECT * FROM './br/q.md'` |
+
+#### Deprecations removed
+
+_None._
+
+#### Behavior changes without code changes
+
+- A brace group with neither a top-level comma nor a valid `..` range is
+  literal text.
+- `{1..3}`, `{a..c}`, `{01..10}` and `{1..10..2}` expand to their values
+  instead of matching the literal text between the braces.
+- An unpaired `{` or `}` is literal text instead of a glob compile error.
+
+#### Verification
+
+```python
+# root holds q.md, {q}.md, a1.md and a2.md
+rows = await DirSQL(root).query("SELECT path FROM './{q}.md'")
+# expected: [{"path": "{q}.md"}]
+rows = await DirSQL(root).query("SELECT path FROM './a{1..2}.md' ORDER BY path")
+# expected: [{"path": "a1.md"}, {"path": "a2.md"}]
+```

packages/rust/changelog.d/2026-10-05-brace-groups-follow-bash.md

@@ -0,0 +1,6 @@
+**Changed** Braces in a path-table follow bash brace expansion. A group with
+a top-level comma (`{a,b}`, nested allowed) is an alternation, and a `..`
+range (`{1..3}`, `{a..c}`, `{01..10}`, `{1..10..2}`) expands to each value.
+Any other brace is literal text: `'./br/{q}.md'` names the file `br/{q}.md`
+where it used to match `br/q.md`, and `{` or `}` without a partner no longer
+fails to compile. Config `[[table]] glob` is unchanged.

packages/rust/migrations.d/2026-10-05-brace-groups-follow-bash.md

@@ -0,0 +1,40 @@
+### Core: path-table braces follow bash brace expansion
+
+#### Summary
+
+A path-table's braces now expand as bash expands them before globbing: a
+group with a top-level comma is an alternation, a `..` range expands to each
+value, and every other brace is literal text. `'./br/{q}.md'` used to match
+`br/q.md` and now matches only a file named `br/{q}.md`; `'./a{1..3}.md'`
+used to match nothing and now matches `a1.md`, `a2.md`, `a3.md`. Comma groups
+behave as before. Every surface that resolves a path-table is affected (CLI,
+REPL, HTTP server, SDKs, `--on-file`); config `[[table]] glob` is not.
+
+#### Required changes
+
+| Surface | Before | After |
+| ------- | ------ | ----- |
+| One-option group | `SELECT * FROM './br/{q}.md'` (matched `br/q.md`) | `SELECT * FROM './br/q.md'` |
+
+#### Deprecations removed
+
+_None._
+
+#### Behavior changes without code changes
+
+- A brace group with neither a top-level comma nor a valid `..` range is
+  literal text.
+- `{1..3}`, `{a..c}`, `{01..10}` and `{1..10..2}` expand to their values
+  instead of matching the literal text between the braces.
+- An unpaired `{` or `}` is literal text instead of a glob compile error.
+
+#### Verification
+
+```bash
+cd "$(mktemp -d)"
+touch q.md '{q}.md' a1.md a2.md
+dirsql query "SELECT path FROM './{q}.md'"
+# expected: [{"path":"{q}.md"}]
+dirsql query "SELECT path FROM './a{1..2}.md' ORDER BY path"
+# expected: [{"path":"a1.md"},{"path":"a2.md"}]
+```