docs: update condition tree controls by lan17 · Pull Request #28 · agentcontrol/docs-agent-control

lan17 · 2026-03-12T22:47:14Z

Feature work: agentcontrol/agent-control#115

Summary

update control-shape examples to use canonical condition instead of flat top-level selector/evaluator
refresh the core concepts and models docs to describe condition trees as the public control contract
sync integration and example pages with the current example code and remove adjacent stale schema usage

Validation

npm run broken-links
npx mintlify validate

github-actions · 2026-03-12T22:47:24Z

Card links check

✅ No broken Card links found. Checked external links in 0.6s

github-actions · 2026-03-12T22:47:36Z

✅ Markdown Lint Passed

All markdown files meet the linting standards! 🎉

lan17 · 2026-03-12T23:15:03Z

 - `scope` (ControlScope): When to apply the control
- `selector` (ControlSelector): What data to evaluate
- `evaluator` (EvaluatorSpec): How to evaluate
+- `condition` (ConditionNode): Recursive condition tree; leaf nodes contain `selector` + `evaluator`


we should still explain selector here somewhere, no?

lan17 · 2026-03-12T23:19:26Z

+ "selector": {"path": "output"},
+ "evaluator": {
+ "name": "regex",
+ "config": {"pattern": r"\\b\\d{3}-\\d{2}-\\d{4}\\b"}


is this correct regex for SSN or are we escaping too many times?

lan17 · 2026-03-12T23:21:11Z

+ "selector": {"path": "output"},
+ "evaluator": {
+ "name": "regex",
+ "config": {"pattern": "\\\\b\\\\d{3}-\\\\d{2}-\\\\d{4}\\\\b"}


potentially same prlblem here. the correct regex should be \b\d{3}-\d{2}-\d{4}\b

Yea r\b\d{3}-\d{2}-\d{4}\b

lan17 · 2026-03-12T23:21:47Z

+ "selector": { "path": "output" },
+ "evaluator": {
+ "name": "regex",
+ "config": { "pattern": "\\b\\d{3}-\\d{2}-\\d{4}\\b" }


why the fuck does it keep escaping this shit? it should be \b\d{3}-\d{2}-\d{4}\b and i already fixed it previously: aedbbed

namrataghadi-galileo · 2026-03-12T23:31:59Z

+ "evaluator": {
+ "name": "regex",
+ "config": {
+ "pattern": "\\b\\d{3}-\\d{2}-\\d{4}\\b"


should be r "\b\d{3}-\d{2}-\d{4}\b"

this is pure JSON so these need to be escaped

namrataghadi-galileo · 2026-03-12T23:32:17Z

+ "evaluator": {
+ "name": "regex",
+ "config": {
+ "pattern": "\\b\\d{3}-\\d{2}-\\d{4}\\b"


json only example needs escape

lan17 · 2026-03-12T23:37:30Z

 "scripts": {
 "dev": "mintlify dev",
- "build": "mintlify build",
+ "build": "mintlify validate",


revert this

corresponding docs update: agentcontrol/docs-agent-control#28 ## Summary - replace flat control predicates with recursive `condition` trees across the shared models, engine, server, SDKs, and UI contracts - add pre-upgrade control migration tooling plus safe `condition_trace` metadata for composite evaluation - bump package majors and regenerate the TypeScript SDK/API types for the new contract ## Scope - User-facing/API changes: - `ControlDefinition` now uses a top-level `condition` tree instead of top-level `selector` / `evaluator` - controls now support nested `and` / `or` / `not` composition with a hard API depth limit of `6` - `/api/v1` stays the same, but this is a major-version wire break for the canonical contract and old SDK majors are unsupported against the new server - added `make server-migrate-control-conditions MIGRATE_ARGS=--dry-run` and `make server-migrate-control-conditions MIGRATE_ARGS=--apply` - Internal changes: - recursive engine evaluation with short-circuiting and `metadata.condition_trace` - recursive server-side validation with nested field paths - Python SDK recursive leaf checks plus non-blocking server-version mismatch warnings - UI keeps the existing single-condition editor behavior for leaf conditions; composite trees are shown but preserved on save rather than fully edited in this PR - Rollout compatibility notes: - server/models still canonicalize legacy flat control payloads (`selector` + `evaluator`) into `condition` during rollout - strict runtime rejection of legacy flat payloads is deferred until after the migration window closes - Out of scope: - full condition-tree editing in the current UI modal - runtime strict rejection of legacy flat control payloads - drag-and-drop tree editing ## Risk and Rollout - Risk level: high - Rollback plan: - take a database backup before running the migration apply step - if rollout fails before migration, revert to the previous server/SDK major - if rollout fails after migration, restore the pre-migration database snapshot before rolling back the server major ## Testing - [x] Added or updated automated tests - [x] Ran `make check` - [ ] Manually verified behavior `make check` passed, which covered: - `make server-test` - `make engine-test` - `make sdk-test` - `make evaluators-test` - repo linting - repo typechecking Notes: - the run emitted a few existing third-party warnings (`sqlglot[rs]` deprecation, Strands resource/deprecation warnings), but the full target passed cleanly ## Checklist - [x] Linked issue/spec: sc-57582, sc-58429 - [x] Updated docs/examples for user-facing changes - [x] Included any required follow-up tasks

lan17 · 2026-03-12T22:47:14Z

Feature work: agentcontrol/agent-control#115

Summary

update control-shape examples to use canonical condition instead of flat top-level selector/evaluator
refresh the core concepts and models docs to describe condition trees as the public control contract
sync integration and example pages with the current example code and remove adjacent stale schema usage

Validation

npm run broken-links
npx mintlify validate

github-actions · 2026-03-12T22:47:24Z

Card links check

✅ No broken Card links found. Checked external links in 0.6s

github-actions · 2026-03-12T22:47:36Z

✅ Markdown Lint Passed

All markdown files meet the linting standards! 🎉

lan17 · 2026-03-12T23:15:03Z

 - `scope` (ControlScope): When to apply the control
- `selector` (ControlSelector): What data to evaluate
- `evaluator` (EvaluatorSpec): How to evaluate
+- `condition` (ConditionNode): Recursive condition tree; leaf nodes contain `selector` + `evaluator`


we should still explain selector here somewhere, no?

lan17 · 2026-03-12T23:19:26Z

+ "selector": {"path": "output"},
+ "evaluator": {
+ "name": "regex",
+ "config": {"pattern": r"\\b\\d{3}-\\d{2}-\\d{4}\\b"}


is this correct regex for SSN or are we escaping too many times?

lan17 · 2026-03-12T23:21:11Z

+ "selector": {"path": "output"},
+ "evaluator": {
+ "name": "regex",
+ "config": {"pattern": "\\\\b\\\\d{3}-\\\\d{2}-\\\\d{4}\\\\b"}


potentially same prlblem here. the correct regex should be \b\d{3}-\d{2}-\d{4}\b

Yea r\b\d{3}-\d{2}-\d{4}\b

lan17 · 2026-03-12T23:21:47Z

+ "selector": { "path": "output" },
+ "evaluator": {
+ "name": "regex",
+ "config": { "pattern": "\\b\\d{3}-\\d{2}-\\d{4}\\b" }


why the fuck does it keep escaping this shit? it should be \b\d{3}-\d{2}-\d{4}\b and i already fixed it previously: aedbbed

namrataghadi-galileo · 2026-03-12T23:31:59Z

+ "evaluator": {
+ "name": "regex",
+ "config": {
+ "pattern": "\\b\\d{3}-\\d{2}-\\d{4}\\b"


should be r "\b\d{3}-\d{2}-\d{4}\b"

this is pure JSON so these need to be escaped

namrataghadi-galileo · 2026-03-12T23:32:17Z

+ "evaluator": {
+ "name": "regex",
+ "config": {
+ "pattern": "\\b\\d{3}-\\d{2}-\\d{4}\\b"


json only example needs escape

lan17 · 2026-03-12T23:37:30Z

 "scripts": {
 "dev": "mintlify dev",
- "build": "mintlify build",
+ "build": "mintlify validate",


revert this

corresponding docs update: agentcontrol/docs-agent-control#28 ## Summary - replace flat control predicates with recursive `condition` trees across the shared models, engine, server, SDKs, and UI contracts - add pre-upgrade control migration tooling plus safe `condition_trace` metadata for composite evaluation - bump package majors and regenerate the TypeScript SDK/API types for the new contract ## Scope - User-facing/API changes: - `ControlDefinition` now uses a top-level `condition` tree instead of top-level `selector` / `evaluator` - controls now support nested `and` / `or` / `not` composition with a hard API depth limit of `6` - `/api/v1` stays the same, but this is a major-version wire break for the canonical contract and old SDK majors are unsupported against the new server - added `make server-migrate-control-conditions MIGRATE_ARGS=--dry-run` and `make server-migrate-control-conditions MIGRATE_ARGS=--apply` - Internal changes: - recursive engine evaluation with short-circuiting and `metadata.condition_trace` - recursive server-side validation with nested field paths - Python SDK recursive leaf checks plus non-blocking server-version mismatch warnings - UI keeps the existing single-condition editor behavior for leaf conditions; composite trees are shown but preserved on save rather than fully edited in this PR - Rollout compatibility notes: - server/models still canonicalize legacy flat control payloads (`selector` + `evaluator`) into `condition` during rollout - strict runtime rejection of legacy flat payloads is deferred until after the migration window closes - Out of scope: - full condition-tree editing in the current UI modal - runtime strict rejection of legacy flat control payloads - drag-and-drop tree editing ## Risk and Rollout - Risk level: high - Rollback plan: - take a database backup before running the migration apply step - if rollout fails before migration, revert to the previous server/SDK major - if rollout fails after migration, restore the pre-migration database snapshot before rolling back the server major ## Testing - [x] Added or updated automated tests - [x] Ran `make check` - [ ] Manually verified behavior `make check` passed, which covered: - `make server-test` - `make engine-test` - `make sdk-test` - `make evaluators-test` - repo linting - repo typechecking Notes: - the run emitted a few existing third-party warnings (`sqlglot[rs]` deprecation, Strands resource/deprecation warnings), but the full target passed cleanly ## Checklist - [x] Linked issue/spec: sc-57582, sc-58429 - [x] Updated docs/examples for user-facing changes - [x] Included any required follow-up tasks

lan17 · 2026-03-12T22:47:14Z

Feature work: agentcontrol/agent-control#115

Summary

update control-shape examples to use canonical condition instead of flat top-level selector/evaluator
refresh the core concepts and models docs to describe condition trees as the public control contract
sync integration and example pages with the current example code and remove adjacent stale schema usage

Validation

npm run broken-links
npx mintlify validate

github-actions · 2026-03-12T22:47:24Z

Card links check

✅ No broken Card links found. Checked external links in 0.6s

github-actions · 2026-03-12T22:47:36Z

✅ Markdown Lint Passed

All markdown files meet the linting standards! 🎉

lan17 · 2026-03-12T23:15:03Z

 - `scope` (ControlScope): When to apply the control
- `selector` (ControlSelector): What data to evaluate
- `evaluator` (EvaluatorSpec): How to evaluate
+- `condition` (ConditionNode): Recursive condition tree; leaf nodes contain `selector` + `evaluator`


we should still explain selector here somewhere, no?

lan17 · 2026-03-12T23:19:26Z

+ "selector": {"path": "output"},
+ "evaluator": {
+ "name": "regex",
+ "config": {"pattern": r"\\b\\d{3}-\\d{2}-\\d{4}\\b"}


is this correct regex for SSN or are we escaping too many times?

lan17 · 2026-03-12T23:21:11Z

+ "selector": {"path": "output"},
+ "evaluator": {
+ "name": "regex",
+ "config": {"pattern": "\\\\b\\\\d{3}-\\\\d{2}-\\\\d{4}\\\\b"}


potentially same prlblem here. the correct regex should be \b\d{3}-\d{2}-\d{4}\b

Yea r\b\d{3}-\d{2}-\d{4}\b

lan17 · 2026-03-12T23:21:47Z

+ "selector": { "path": "output" },
+ "evaluator": {
+ "name": "regex",
+ "config": { "pattern": "\\b\\d{3}-\\d{2}-\\d{4}\\b" }


why the fuck does it keep escaping this shit? it should be \b\d{3}-\d{2}-\d{4}\b and i already fixed it previously: aedbbed

namrataghadi-galileo · 2026-03-12T23:31:59Z

+ "evaluator": {
+ "name": "regex",
+ "config": {
+ "pattern": "\\b\\d{3}-\\d{2}-\\d{4}\\b"


should be r "\b\d{3}-\d{2}-\d{4}\b"

this is pure JSON so these need to be escaped

namrataghadi-galileo · 2026-03-12T23:32:17Z

+ "evaluator": {
+ "name": "regex",
+ "config": {
+ "pattern": "\\b\\d{3}-\\d{2}-\\d{4}\\b"


json only example needs escape

lan17 · 2026-03-12T23:37:30Z

 "scripts": {
 "dev": "mintlify dev",
- "build": "mintlify build",
+ "build": "mintlify validate",


revert this

corresponding docs update: agentcontrol/docs-agent-control#28 ## Summary - replace flat control predicates with recursive `condition` trees across the shared models, engine, server, SDKs, and UI contracts - add pre-upgrade control migration tooling plus safe `condition_trace` metadata for composite evaluation - bump package majors and regenerate the TypeScript SDK/API types for the new contract ## Scope - User-facing/API changes: - `ControlDefinition` now uses a top-level `condition` tree instead of top-level `selector` / `evaluator` - controls now support nested `and` / `or` / `not` composition with a hard API depth limit of `6` - `/api/v1` stays the same, but this is a major-version wire break for the canonical contract and old SDK majors are unsupported against the new server - added `make server-migrate-control-conditions MIGRATE_ARGS=--dry-run` and `make server-migrate-control-conditions MIGRATE_ARGS=--apply` - Internal changes: - recursive engine evaluation with short-circuiting and `metadata.condition_trace` - recursive server-side validation with nested field paths - Python SDK recursive leaf checks plus non-blocking server-version mismatch warnings - UI keeps the existing single-condition editor behavior for leaf conditions; composite trees are shown but preserved on save rather than fully edited in this PR - Rollout compatibility notes: - server/models still canonicalize legacy flat control payloads (`selector` + `evaluator`) into `condition` during rollout - strict runtime rejection of legacy flat payloads is deferred until after the migration window closes - Out of scope: - full condition-tree editing in the current UI modal - runtime strict rejection of legacy flat control payloads - drag-and-drop tree editing ## Risk and Rollout - Risk level: high - Rollback plan: - take a database backup before running the migration apply step - if rollout fails before migration, revert to the previous server/SDK major - if rollout fails after migration, restore the pre-migration database snapshot before rolling back the server major ## Testing - [x] Added or updated automated tests - [x] Ran `make check` - [ ] Manually verified behavior `make check` passed, which covered: - `make server-test` - `make engine-test` - `make sdk-test` - `make evaluators-test` - repo linting - repo typechecking Notes: - the run emitted a few existing third-party warnings (`sqlglot[rs]` deprecation, Strands resource/deprecation warnings), but the full target passed cleanly ## Checklist - [x] Linked issue/spec: sc-57582, sc-58429 - [x] Updated docs/examples for user-facing changes - [x] Included any required follow-up tasks

lan17 · 2026-03-12T22:47:14Z

Feature work: agentcontrol/agent-control#115

Summary

update control-shape examples to use canonical condition instead of flat top-level selector/evaluator
refresh the core concepts and models docs to describe condition trees as the public control contract
sync integration and example pages with the current example code and remove adjacent stale schema usage

Validation

npm run broken-links
npx mintlify validate

github-actions · 2026-03-12T22:47:24Z

Card links check

✅ No broken Card links found. Checked external links in 0.6s

github-actions · 2026-03-12T22:47:36Z

✅ Markdown Lint Passed

All markdown files meet the linting standards! 🎉

lan17 · 2026-03-12T23:15:03Z

 - `scope` (ControlScope): When to apply the control
- `selector` (ControlSelector): What data to evaluate
- `evaluator` (EvaluatorSpec): How to evaluate
+- `condition` (ConditionNode): Recursive condition tree; leaf nodes contain `selector` + `evaluator`


we should still explain selector here somewhere, no?

lan17 · 2026-03-12T23:19:26Z

+ "selector": {"path": "output"},
+ "evaluator": {
+ "name": "regex",
+ "config": {"pattern": r"\\b\\d{3}-\\d{2}-\\d{4}\\b"}


is this correct regex for SSN or are we escaping too many times?

lan17 · 2026-03-12T23:21:11Z

+ "selector": {"path": "output"},
+ "evaluator": {
+ "name": "regex",
+ "config": {"pattern": "\\\\b\\\\d{3}-\\\\d{2}-\\\\d{4}\\\\b"}


potentially same prlblem here. the correct regex should be \b\d{3}-\d{2}-\d{4}\b

Yea r\b\d{3}-\d{2}-\d{4}\b

lan17 · 2026-03-12T23:21:47Z

+ "selector": { "path": "output" },
+ "evaluator": {
+ "name": "regex",
+ "config": { "pattern": "\\b\\d{3}-\\d{2}-\\d{4}\\b" }


why the fuck does it keep escaping this shit? it should be \b\d{3}-\d{2}-\d{4}\b and i already fixed it previously: aedbbed

namrataghadi-galileo · 2026-03-12T23:31:59Z

+ "evaluator": {
+ "name": "regex",
+ "config": {
+ "pattern": "\\b\\d{3}-\\d{2}-\\d{4}\\b"


should be r "\b\d{3}-\d{2}-\d{4}\b"

this is pure JSON so these need to be escaped

namrataghadi-galileo · 2026-03-12T23:32:17Z

+ "evaluator": {
+ "name": "regex",
+ "config": {
+ "pattern": "\\b\\d{3}-\\d{2}-\\d{4}\\b"


json only example needs escape

lan17 · 2026-03-12T23:37:30Z

 "scripts": {
 "dev": "mintlify dev",
- "build": "mintlify build",
+ "build": "mintlify validate",


revert this

corresponding docs update: agentcontrol/docs-agent-control#28 ## Summary - replace flat control predicates with recursive `condition` trees across the shared models, engine, server, SDKs, and UI contracts - add pre-upgrade control migration tooling plus safe `condition_trace` metadata for composite evaluation - bump package majors and regenerate the TypeScript SDK/API types for the new contract ## Scope - User-facing/API changes: - `ControlDefinition` now uses a top-level `condition` tree instead of top-level `selector` / `evaluator` - controls now support nested `and` / `or` / `not` composition with a hard API depth limit of `6` - `/api/v1` stays the same, but this is a major-version wire break for the canonical contract and old SDK majors are unsupported against the new server - added `make server-migrate-control-conditions MIGRATE_ARGS=--dry-run` and `make server-migrate-control-conditions MIGRATE_ARGS=--apply` - Internal changes: - recursive engine evaluation with short-circuiting and `metadata.condition_trace` - recursive server-side validation with nested field paths - Python SDK recursive leaf checks plus non-blocking server-version mismatch warnings - UI keeps the existing single-condition editor behavior for leaf conditions; composite trees are shown but preserved on save rather than fully edited in this PR - Rollout compatibility notes: - server/models still canonicalize legacy flat control payloads (`selector` + `evaluator`) into `condition` during rollout - strict runtime rejection of legacy flat payloads is deferred until after the migration window closes - Out of scope: - full condition-tree editing in the current UI modal - runtime strict rejection of legacy flat control payloads - drag-and-drop tree editing ## Risk and Rollout - Risk level: high - Rollback plan: - take a database backup before running the migration apply step - if rollout fails before migration, revert to the previous server/SDK major - if rollout fails after migration, restore the pre-migration database snapshot before rolling back the server major ## Testing - [x] Added or updated automated tests - [x] Ran `make check` - [ ] Manually verified behavior `make check` passed, which covered: - `make server-test` - `make engine-test` - `make sdk-test` - `make evaluators-test` - repo linting - repo typechecking Notes: - the run emitted a few existing third-party warnings (`sqlglot[rs]` deprecation, Strands resource/deprecation warnings), but the full target passed cleanly ## Checklist - [x] Linked issue/spec: sc-57582, sc-58429 - [x] Updated docs/examples for user-facing changes - [x] Included any required follow-up tasks

lan17 · 2026-03-12T22:47:14Z

Feature work: agentcontrol/agent-control#115

Summary

update control-shape examples to use canonical condition instead of flat top-level selector/evaluator
refresh the core concepts and models docs to describe condition trees as the public control contract
sync integration and example pages with the current example code and remove adjacent stale schema usage

Validation

npm run broken-links
npx mintlify validate

github-actions · 2026-03-12T22:47:24Z

Card links check

✅ No broken Card links found. Checked external links in 0.6s

github-actions · 2026-03-12T22:47:36Z

✅ Markdown Lint Passed

All markdown files meet the linting standards! 🎉

lan17 · 2026-03-12T23:15:03Z

 - `scope` (ControlScope): When to apply the control
- `selector` (ControlSelector): What data to evaluate
- `evaluator` (EvaluatorSpec): How to evaluate
+- `condition` (ConditionNode): Recursive condition tree; leaf nodes contain `selector` + `evaluator`


we should still explain selector here somewhere, no?

lan17 · 2026-03-12T23:19:26Z

+ "selector": {"path": "output"},
+ "evaluator": {
+ "name": "regex",
+ "config": {"pattern": r"\\b\\d{3}-\\d{2}-\\d{4}\\b"}


is this correct regex for SSN or are we escaping too many times?

lan17 · 2026-03-12T23:21:11Z

+ "selector": {"path": "output"},
+ "evaluator": {
+ "name": "regex",
+ "config": {"pattern": "\\\\b\\\\d{3}-\\\\d{2}-\\\\d{4}\\\\b"}


potentially same prlblem here. the correct regex should be \b\d{3}-\d{2}-\d{4}\b

Yea r\b\d{3}-\d{2}-\d{4}\b

lan17 · 2026-03-12T23:21:47Z

+ "selector": { "path": "output" },
+ "evaluator": {
+ "name": "regex",
+ "config": { "pattern": "\\b\\d{3}-\\d{2}-\\d{4}\\b" }


why the fuck does it keep escaping this shit? it should be \b\d{3}-\d{2}-\d{4}\b and i already fixed it previously: aedbbed

namrataghadi-galileo · 2026-03-12T23:31:59Z

+ "evaluator": {
+ "name": "regex",
+ "config": {
+ "pattern": "\\b\\d{3}-\\d{2}-\\d{4}\\b"


should be r "\b\d{3}-\d{2}-\d{4}\b"

this is pure JSON so these need to be escaped

namrataghadi-galileo · 2026-03-12T23:32:17Z

+ "evaluator": {
+ "name": "regex",
+ "config": {
+ "pattern": "\\b\\d{3}-\\d{2}-\\d{4}\\b"


json only example needs escape

lan17 · 2026-03-12T23:37:30Z

 "scripts": {
 "dev": "mintlify dev",
- "build": "mintlify build",
+ "build": "mintlify validate",


revert this

corresponding docs update: agentcontrol/docs-agent-control#28 ## Summary - replace flat control predicates with recursive `condition` trees across the shared models, engine, server, SDKs, and UI contracts - add pre-upgrade control migration tooling plus safe `condition_trace` metadata for composite evaluation - bump package majors and regenerate the TypeScript SDK/API types for the new contract ## Scope - User-facing/API changes: - `ControlDefinition` now uses a top-level `condition` tree instead of top-level `selector` / `evaluator` - controls now support nested `and` / `or` / `not` composition with a hard API depth limit of `6` - `/api/v1` stays the same, but this is a major-version wire break for the canonical contract and old SDK majors are unsupported against the new server - added `make server-migrate-control-conditions MIGRATE_ARGS=--dry-run` and `make server-migrate-control-conditions MIGRATE_ARGS=--apply` - Internal changes: - recursive engine evaluation with short-circuiting and `metadata.condition_trace` - recursive server-side validation with nested field paths - Python SDK recursive leaf checks plus non-blocking server-version mismatch warnings - UI keeps the existing single-condition editor behavior for leaf conditions; composite trees are shown but preserved on save rather than fully edited in this PR - Rollout compatibility notes: - server/models still canonicalize legacy flat control payloads (`selector` + `evaluator`) into `condition` during rollout - strict runtime rejection of legacy flat payloads is deferred until after the migration window closes - Out of scope: - full condition-tree editing in the current UI modal - runtime strict rejection of legacy flat control payloads - drag-and-drop tree editing ## Risk and Rollout - Risk level: high - Rollback plan: - take a database backup before running the migration apply step - if rollout fails before migration, revert to the previous server/SDK major - if rollout fails after migration, restore the pre-migration database snapshot before rolling back the server major ## Testing - [x] Added or updated automated tests - [x] Ran `make check` - [ ] Manually verified behavior `make check` passed, which covered: - `make server-test` - `make engine-test` - `make sdk-test` - `make evaluators-test` - repo linting - repo typechecking Notes: - the run emitted a few existing third-party warnings (`sqlglot[rs]` deprecation, Strands resource/deprecation warnings), but the full target passed cleanly ## Checklist - [x] Linked issue/spec: sc-57582, sc-58429 - [x] Updated docs/examples for user-facing changes - [x] Included any required follow-up tasks

lan17 · 2026-03-12T22:47:14Z

Feature work: agentcontrol/agent-control#115

Summary

update control-shape examples to use canonical condition instead of flat top-level selector/evaluator
refresh the core concepts and models docs to describe condition trees as the public control contract
sync integration and example pages with the current example code and remove adjacent stale schema usage

Validation

npm run broken-links
npx mintlify validate

github-actions · 2026-03-12T22:47:24Z

Card links check

✅ No broken Card links found. Checked external links in 0.6s

github-actions · 2026-03-12T22:47:36Z

✅ Markdown Lint Passed

All markdown files meet the linting standards! 🎉

lan17 · 2026-03-12T23:15:03Z

 - `scope` (ControlScope): When to apply the control
- `selector` (ControlSelector): What data to evaluate
- `evaluator` (EvaluatorSpec): How to evaluate
+- `condition` (ConditionNode): Recursive condition tree; leaf nodes contain `selector` + `evaluator`


we should still explain selector here somewhere, no?

lan17 · 2026-03-12T23:19:26Z

+ "selector": {"path": "output"},
+ "evaluator": {
+ "name": "regex",
+ "config": {"pattern": r"\\b\\d{3}-\\d{2}-\\d{4}\\b"}


is this correct regex for SSN or are we escaping too many times?

lan17 · 2026-03-12T23:21:11Z

+ "selector": {"path": "output"},
+ "evaluator": {
+ "name": "regex",
+ "config": {"pattern": "\\\\b\\\\d{3}-\\\\d{2}-\\\\d{4}\\\\b"}


potentially same prlblem here. the correct regex should be \b\d{3}-\d{2}-\d{4}\b

Yea r\b\d{3}-\d{2}-\d{4}\b

lan17 · 2026-03-12T23:21:47Z

+ "selector": { "path": "output" },
+ "evaluator": {
+ "name": "regex",
+ "config": { "pattern": "\\b\\d{3}-\\d{2}-\\d{4}\\b" }


why the fuck does it keep escaping this shit? it should be \b\d{3}-\d{2}-\d{4}\b and i already fixed it previously: aedbbed

namrataghadi-galileo · 2026-03-12T23:31:59Z

+ "evaluator": {
+ "name": "regex",
+ "config": {
+ "pattern": "\\b\\d{3}-\\d{2}-\\d{4}\\b"


should be r "\b\d{3}-\d{2}-\d{4}\b"

this is pure JSON so these need to be escaped

namrataghadi-galileo · 2026-03-12T23:32:17Z

+ "evaluator": {
+ "name": "regex",
+ "config": {
+ "pattern": "\\b\\d{3}-\\d{2}-\\d{4}\\b"


json only example needs escape

lan17 · 2026-03-12T23:37:30Z

 "scripts": {
 "dev": "mintlify dev",
- "build": "mintlify build",
+ "build": "mintlify validate",


revert this

corresponding docs update: agentcontrol/docs-agent-control#28 ## Summary - replace flat control predicates with recursive `condition` trees across the shared models, engine, server, SDKs, and UI contracts - add pre-upgrade control migration tooling plus safe `condition_trace` metadata for composite evaluation - bump package majors and regenerate the TypeScript SDK/API types for the new contract ## Scope - User-facing/API changes: - `ControlDefinition` now uses a top-level `condition` tree instead of top-level `selector` / `evaluator` - controls now support nested `and` / `or` / `not` composition with a hard API depth limit of `6` - `/api/v1` stays the same, but this is a major-version wire break for the canonical contract and old SDK majors are unsupported against the new server - added `make server-migrate-control-conditions MIGRATE_ARGS=--dry-run` and `make server-migrate-control-conditions MIGRATE_ARGS=--apply` - Internal changes: - recursive engine evaluation with short-circuiting and `metadata.condition_trace` - recursive server-side validation with nested field paths - Python SDK recursive leaf checks plus non-blocking server-version mismatch warnings - UI keeps the existing single-condition editor behavior for leaf conditions; composite trees are shown but preserved on save rather than fully edited in this PR - Rollout compatibility notes: - server/models still canonicalize legacy flat control payloads (`selector` + `evaluator`) into `condition` during rollout - strict runtime rejection of legacy flat payloads is deferred until after the migration window closes - Out of scope: - full condition-tree editing in the current UI modal - runtime strict rejection of legacy flat control payloads - drag-and-drop tree editing ## Risk and Rollout - Risk level: high - Rollback plan: - take a database backup before running the migration apply step - if rollout fails before migration, revert to the previous server/SDK major - if rollout fails after migration, restore the pre-migration database snapshot before rolling back the server major ## Testing - [x] Added or updated automated tests - [x] Ran `make check` - [ ] Manually verified behavior `make check` passed, which covered: - `make server-test` - `make engine-test` - `make sdk-test` - `make evaluators-test` - repo linting - repo typechecking Notes: - the run emitted a few existing third-party warnings (`sqlglot[rs]` deprecation, Strands resource/deprecation warnings), but the full target passed cleanly ## Checklist - [x] Linked issue/spec: sc-57582, sc-58429 - [x] Updated docs/examples for user-facing changes - [x] Included any required follow-up tasks

lan17 · 2026-03-12T22:47:14Z

Feature work: agentcontrol/agent-control#115

Summary

update control-shape examples to use canonical condition instead of flat top-level selector/evaluator
refresh the core concepts and models docs to describe condition trees as the public control contract
sync integration and example pages with the current example code and remove adjacent stale schema usage

Validation

npm run broken-links
npx mintlify validate

github-actions · 2026-03-12T22:47:24Z

Card links check

✅ No broken Card links found. Checked external links in 0.6s

github-actions · 2026-03-12T22:47:36Z

✅ Markdown Lint Passed

All markdown files meet the linting standards! 🎉

lan17 · 2026-03-12T23:15:03Z

 - `scope` (ControlScope): When to apply the control
- `selector` (ControlSelector): What data to evaluate
- `evaluator` (EvaluatorSpec): How to evaluate
+- `condition` (ConditionNode): Recursive condition tree; leaf nodes contain `selector` + `evaluator`


we should still explain selector here somewhere, no?

lan17 · 2026-03-12T23:19:26Z

+ "selector": {"path": "output"},
+ "evaluator": {
+ "name": "regex",
+ "config": {"pattern": r"\\b\\d{3}-\\d{2}-\\d{4}\\b"}


is this correct regex for SSN or are we escaping too many times?

lan17 · 2026-03-12T23:21:11Z

+ "selector": {"path": "output"},
+ "evaluator": {
+ "name": "regex",
+ "config": {"pattern": "\\\\b\\\\d{3}-\\\\d{2}-\\\\d{4}\\\\b"}


potentially same prlblem here. the correct regex should be \b\d{3}-\d{2}-\d{4}\b

Yea r\b\d{3}-\d{2}-\d{4}\b

lan17 · 2026-03-12T23:21:47Z

+ "selector": { "path": "output" },
+ "evaluator": {
+ "name": "regex",
+ "config": { "pattern": "\\b\\d{3}-\\d{2}-\\d{4}\\b" }


why the fuck does it keep escaping this shit? it should be \b\d{3}-\d{2}-\d{4}\b and i already fixed it previously: aedbbed

namrataghadi-galileo · 2026-03-12T23:31:59Z

+ "evaluator": {
+ "name": "regex",
+ "config": {
+ "pattern": "\\b\\d{3}-\\d{2}-\\d{4}\\b"


should be r "\b\d{3}-\d{2}-\d{4}\b"

this is pure JSON so these need to be escaped

namrataghadi-galileo · 2026-03-12T23:32:17Z

+ "evaluator": {
+ "name": "regex",
+ "config": {
+ "pattern": "\\b\\d{3}-\\d{2}-\\d{4}\\b"


json only example needs escape

lan17 · 2026-03-12T23:37:30Z

 "scripts": {
 "dev": "mintlify dev",
- "build": "mintlify build",
+ "build": "mintlify validate",


revert this

corresponding docs update: agentcontrol/docs-agent-control#28 ## Summary - replace flat control predicates with recursive `condition` trees across the shared models, engine, server, SDKs, and UI contracts - add pre-upgrade control migration tooling plus safe `condition_trace` metadata for composite evaluation - bump package majors and regenerate the TypeScript SDK/API types for the new contract ## Scope - User-facing/API changes: - `ControlDefinition` now uses a top-level `condition` tree instead of top-level `selector` / `evaluator` - controls now support nested `and` / `or` / `not` composition with a hard API depth limit of `6` - `/api/v1` stays the same, but this is a major-version wire break for the canonical contract and old SDK majors are unsupported against the new server - added `make server-migrate-control-conditions MIGRATE_ARGS=--dry-run` and `make server-migrate-control-conditions MIGRATE_ARGS=--apply` - Internal changes: - recursive engine evaluation with short-circuiting and `metadata.condition_trace` - recursive server-side validation with nested field paths - Python SDK recursive leaf checks plus non-blocking server-version mismatch warnings - UI keeps the existing single-condition editor behavior for leaf conditions; composite trees are shown but preserved on save rather than fully edited in this PR - Rollout compatibility notes: - server/models still canonicalize legacy flat control payloads (`selector` + `evaluator`) into `condition` during rollout - strict runtime rejection of legacy flat payloads is deferred until after the migration window closes - Out of scope: - full condition-tree editing in the current UI modal - runtime strict rejection of legacy flat control payloads - drag-and-drop tree editing ## Risk and Rollout - Risk level: high - Rollback plan: - take a database backup before running the migration apply step - if rollout fails before migration, revert to the previous server/SDK major - if rollout fails after migration, restore the pre-migration database snapshot before rolling back the server major ## Testing - [x] Added or updated automated tests - [x] Ran `make check` - [ ] Manually verified behavior `make check` passed, which covered: - `make server-test` - `make engine-test` - `make sdk-test` - `make evaluators-test` - repo linting - repo typechecking Notes: - the run emitted a few existing third-party warnings (`sqlglot[rs]` deprecation, Strands resource/deprecation warnings), but the full target passed cleanly ## Checklist - [x] Linked issue/spec: sc-57582, sc-58429 - [x] Updated docs/examples for user-facing changes - [x] Included any required follow-up tasks

lan17 · 2026-03-12T22:47:14Z

Feature work: agentcontrol/agent-control#115

Summary

update control-shape examples to use canonical condition instead of flat top-level selector/evaluator
refresh the core concepts and models docs to describe condition trees as the public control contract
sync integration and example pages with the current example code and remove adjacent stale schema usage

Validation

npm run broken-links
npx mintlify validate

github-actions · 2026-03-12T22:47:24Z

Card links check

✅ No broken Card links found. Checked external links in 0.6s

github-actions · 2026-03-12T22:47:36Z

✅ Markdown Lint Passed

All markdown files meet the linting standards! 🎉

lan17 · 2026-03-12T23:15:03Z

 - `scope` (ControlScope): When to apply the control
- `selector` (ControlSelector): What data to evaluate
- `evaluator` (EvaluatorSpec): How to evaluate
+- `condition` (ConditionNode): Recursive condition tree; leaf nodes contain `selector` + `evaluator`


we should still explain selector here somewhere, no?

lan17 · 2026-03-12T23:19:26Z

+ "selector": {"path": "output"},
+ "evaluator": {
+ "name": "regex",
+ "config": {"pattern": r"\\b\\d{3}-\\d{2}-\\d{4}\\b"}


is this correct regex for SSN or are we escaping too many times?

lan17 · 2026-03-12T23:21:11Z

+ "selector": {"path": "output"},
+ "evaluator": {
+ "name": "regex",
+ "config": {"pattern": "\\\\b\\\\d{3}-\\\\d{2}-\\\\d{4}\\\\b"}


potentially same prlblem here. the correct regex should be \b\d{3}-\d{2}-\d{4}\b

Yea r\b\d{3}-\d{2}-\d{4}\b

lan17 · 2026-03-12T23:21:47Z

+ "selector": { "path": "output" },
+ "evaluator": {
+ "name": "regex",
+ "config": { "pattern": "\\b\\d{3}-\\d{2}-\\d{4}\\b" }


why the fuck does it keep escaping this shit? it should be \b\d{3}-\d{2}-\d{4}\b and i already fixed it previously: aedbbed

namrataghadi-galileo · 2026-03-12T23:31:59Z

+ "evaluator": {
+ "name": "regex",
+ "config": {
+ "pattern": "\\b\\d{3}-\\d{2}-\\d{4}\\b"


should be r "\b\d{3}-\d{2}-\d{4}\b"

this is pure JSON so these need to be escaped

namrataghadi-galileo · 2026-03-12T23:32:17Z

+ "evaluator": {
+ "name": "regex",
+ "config": {
+ "pattern": "\\b\\d{3}-\\d{2}-\\d{4}\\b"


json only example needs escape

lan17 · 2026-03-12T23:37:30Z

 "scripts": {
 "dev": "mintlify dev",
- "build": "mintlify build",
+ "build": "mintlify validate",


revert this

corresponding docs update: agentcontrol/docs-agent-control#28 ## Summary - replace flat control predicates with recursive `condition` trees across the shared models, engine, server, SDKs, and UI contracts - add pre-upgrade control migration tooling plus safe `condition_trace` metadata for composite evaluation - bump package majors and regenerate the TypeScript SDK/API types for the new contract ## Scope - User-facing/API changes: - `ControlDefinition` now uses a top-level `condition` tree instead of top-level `selector` / `evaluator` - controls now support nested `and` / `or` / `not` composition with a hard API depth limit of `6` - `/api/v1` stays the same, but this is a major-version wire break for the canonical contract and old SDK majors are unsupported against the new server - added `make server-migrate-control-conditions MIGRATE_ARGS=--dry-run` and `make server-migrate-control-conditions MIGRATE_ARGS=--apply` - Internal changes: - recursive engine evaluation with short-circuiting and `metadata.condition_trace` - recursive server-side validation with nested field paths - Python SDK recursive leaf checks plus non-blocking server-version mismatch warnings - UI keeps the existing single-condition editor behavior for leaf conditions; composite trees are shown but preserved on save rather than fully edited in this PR - Rollout compatibility notes: - server/models still canonicalize legacy flat control payloads (`selector` + `evaluator`) into `condition` during rollout - strict runtime rejection of legacy flat payloads is deferred until after the migration window closes - Out of scope: - full condition-tree editing in the current UI modal - runtime strict rejection of legacy flat control payloads - drag-and-drop tree editing ## Risk and Rollout - Risk level: high - Rollback plan: - take a database backup before running the migration apply step - if rollout fails before migration, revert to the previous server/SDK major - if rollout fails after migration, restore the pre-migration database snapshot before rolling back the server major ## Testing - [x] Added or updated automated tests - [x] Ran `make check` - [ ] Manually verified behavior `make check` passed, which covered: - `make server-test` - `make engine-test` - `make sdk-test` - `make evaluators-test` - repo linting - repo typechecking Notes: - the run emitted a few existing third-party warnings (`sqlglot[rs]` deprecation, Strands resource/deprecation warnings), but the full target passed cleanly ## Checklist - [x] Linked issue/spec: sc-57582, sc-58429 - [x] Updated docs/examples for user-facing changes - [x] Included any required follow-up tasks

docs: update condition tree controls
4f3ec4b

mintlifyBotdeployed to staging March 12, 2026 22:47 View deployment

build: fix docs validation script
e09fda8

mintlifyBotdeployed to staging March 12, 2026 22:48 View deployment

lan17 mentioned this pull request Mar 12, 2026
feat(server)!: implement recursive control condition trees agentcontrol/agent-control#115
Merged
6 tasks

lan17 commented Mar 12, 2026
View reviewed changes

docs: clarify condition submodels
6be287a

mintlifyBotdeployed to staging March 12, 2026 23:29 View deployment

namrataghadi-galileo reviewed Mar 12, 2026
View reviewed changes

docs: fix regex escaping in curl example
06be2f7

mintlifyBotdeployed to staging March 12, 2026 23:36 View deployment

lan17 commented Mar 12, 2026
View reviewed changes

yashsheth46 approved these changes Mar 17, 2026
View reviewed changes

namrataghadi-galileo approved these changes Mar 17, 2026
View reviewed changes

lan17 merged commit f75920d into mainMar 17, 2026
6 checks passed

docs: update condition tree controls
4f3ec4b

mintlifyBotdeployed to staging March 12, 2026 22:47 View deployment

build: fix docs validation script
e09fda8

mintlifyBotdeployed to staging March 12, 2026 22:48 View deployment

lan17 mentioned this pull request Mar 12, 2026
feat(server)!: implement recursive control condition trees agentcontrol/agent-control#115
Merged
6 tasks

lan17 commented Mar 12, 2026
View reviewed changes

docs: clarify condition submodels
6be287a

mintlifyBotdeployed to staging March 12, 2026 23:29 View deployment

namrataghadi-galileo reviewed Mar 12, 2026
View reviewed changes

docs: fix regex escaping in curl example
06be2f7

mintlifyBotdeployed to staging March 12, 2026 23:36 View deployment

lan17 commented Mar 12, 2026
View reviewed changes

yashsheth46 approved these changes Mar 17, 2026
View reviewed changes

namrataghadi-galileo approved these changes Mar 17, 2026
View reviewed changes

lan17 merged commit f75920d into mainMar 17, 2026
6 checks passed

docs: update condition tree controls
4f3ec4b

mintlifyBotdeployed to staging March 12, 2026 22:47 View deployment

build: fix docs validation script
e09fda8

mintlifyBotdeployed to staging March 12, 2026 22:48 View deployment

lan17 mentioned this pull request Mar 12, 2026
feat(server)!: implement recursive control condition trees agentcontrol/agent-control#115
Merged
6 tasks

lan17 commented Mar 12, 2026
View reviewed changes

docs: clarify condition submodels
6be287a

mintlifyBotdeployed to staging March 12, 2026 23:29 View deployment

namrataghadi-galileo reviewed Mar 12, 2026
View reviewed changes

docs: fix regex escaping in curl example
06be2f7

mintlifyBotdeployed to staging March 12, 2026 23:36 View deployment

lan17 commented Mar 12, 2026
View reviewed changes

yashsheth46 approved these changes Mar 17, 2026
View reviewed changes

namrataghadi-galileo approved these changes Mar 17, 2026
View reviewed changes

lan17 merged commit f75920d into mainMar 17, 2026
6 checks passed

docs: update condition tree controls
4f3ec4b

mintlifyBotdeployed to staging March 12, 2026 22:47 View deployment

build: fix docs validation script
e09fda8

mintlifyBotdeployed to staging March 12, 2026 22:48 View deployment

lan17 mentioned this pull request Mar 12, 2026
feat(server)!: implement recursive control condition trees agentcontrol/agent-control#115
Merged
6 tasks

lan17 commented Mar 12, 2026
View reviewed changes

docs: clarify condition submodels
6be287a

mintlifyBotdeployed to staging March 12, 2026 23:29 View deployment

namrataghadi-galileo reviewed Mar 12, 2026
View reviewed changes

docs: fix regex escaping in curl example
06be2f7

mintlifyBotdeployed to staging March 12, 2026 23:36 View deployment

lan17 commented Mar 12, 2026
View reviewed changes

yashsheth46 approved these changes Mar 17, 2026
View reviewed changes

namrataghadi-galileo approved these changes Mar 17, 2026
View reviewed changes

lan17 merged commit f75920d into mainMar 17, 2026
6 checks passed

docs: update condition tree controls
4f3ec4b

mintlifyBotdeployed to staging March 12, 2026 22:47 View deployment

build: fix docs validation script
e09fda8

mintlifyBotdeployed to staging March 12, 2026 22:48 View deployment

lan17 mentioned this pull request Mar 12, 2026
feat(server)!: implement recursive control condition trees agentcontrol/agent-control#115
Merged
6 tasks

lan17 commented Mar 12, 2026
View reviewed changes

docs: clarify condition submodels
6be287a

mintlifyBotdeployed to staging March 12, 2026 23:29 View deployment

namrataghadi-galileo reviewed Mar 12, 2026
View reviewed changes

docs: fix regex escaping in curl example
06be2f7

mintlifyBotdeployed to staging March 12, 2026 23:36 View deployment

lan17 commented Mar 12, 2026
View reviewed changes

yashsheth46 approved these changes Mar 17, 2026
View reviewed changes

namrataghadi-galileo approved these changes Mar 17, 2026
View reviewed changes

lan17 merged commit f75920d into mainMar 17, 2026
6 checks passed

docs: update condition tree controls
4f3ec4b

mintlifyBotdeployed to staging March 12, 2026 22:47 View deployment

build: fix docs validation script
e09fda8

mintlifyBotdeployed to staging March 12, 2026 22:48 View deployment

lan17 mentioned this pull request Mar 12, 2026
feat(server)!: implement recursive control condition trees agentcontrol/agent-control#115
Merged
6 tasks

lan17 commented Mar 12, 2026
View reviewed changes

docs: clarify condition submodels
6be287a

mintlifyBotdeployed to staging March 12, 2026 23:29 View deployment

namrataghadi-galileo reviewed Mar 12, 2026
View reviewed changes

docs: fix regex escaping in curl example
06be2f7

mintlifyBotdeployed to staging March 12, 2026 23:36 View deployment

lan17 commented Mar 12, 2026
View reviewed changes

yashsheth46 approved these changes Mar 17, 2026
View reviewed changes

namrataghadi-galileo approved these changes Mar 17, 2026
View reviewed changes

lan17 merged commit f75920d into mainMar 17, 2026
6 checks passed

docs: update condition tree controls
4f3ec4b

mintlifyBotdeployed to staging March 12, 2026 22:47 View deployment

build: fix docs validation script
e09fda8

mintlifyBotdeployed to staging March 12, 2026 22:48 View deployment

lan17 mentioned this pull request Mar 12, 2026
feat(server)!: implement recursive control condition trees agentcontrol/agent-control#115
Merged
6 tasks

lan17 commented Mar 12, 2026
View reviewed changes

docs: clarify condition submodels
6be287a

mintlifyBotdeployed to staging March 12, 2026 23:29 View deployment

namrataghadi-galileo reviewed Mar 12, 2026
View reviewed changes

docs: fix regex escaping in curl example
06be2f7

mintlifyBotdeployed to staging March 12, 2026 23:36 View deployment

lan17 commented Mar 12, 2026
View reviewed changes

yashsheth46 approved these changes Mar 17, 2026
View reviewed changes

namrataghadi-galileo approved these changes Mar 17, 2026
View reviewed changes

lan17 merged commit f75920d into mainMar 17, 2026
6 checks passed

docs: update condition tree controls
4f3ec4b

mintlifyBotdeployed to staging March 12, 2026 22:47 View deployment

build: fix docs validation script
e09fda8

mintlifyBotdeployed to staging March 12, 2026 22:48 View deployment

lan17 mentioned this pull request Mar 12, 2026
feat(server)!: implement recursive control condition trees agentcontrol/agent-control#115
Merged
6 tasks

lan17 commented Mar 12, 2026
View reviewed changes

docs: clarify condition submodels
6be287a

mintlifyBotdeployed to staging March 12, 2026 23:29 View deployment

namrataghadi-galileo reviewed Mar 12, 2026
View reviewed changes

docs: fix regex escaping in curl example
06be2f7

mintlifyBotdeployed to staging March 12, 2026 23:36 View deployment

lan17 commented Mar 12, 2026
View reviewed changes

yashsheth46 approved these changes Mar 17, 2026
View reviewed changes

namrataghadi-galileo approved these changes Mar 17, 2026
View reviewed changes

lan17 merged commit f75920d into mainMar 17, 2026
6 checks passed

Uh oh!

Conversation

lan17 commented Mar 12, 2026• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Validation

Uh oh!

github-actionsBot commented Mar 12, 2026• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Card links check

Uh oh!

github-actionsBot commented Mar 12, 2026• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

✅ Markdown Lint Passed

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Uh oh!

Conversation

lan17 commented Mar 12, 2026• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Validation

Uh oh!

github-actionsBot commented Mar 12, 2026• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Card links check

Uh oh!

github-actionsBot commented Mar 12, 2026• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

✅ Markdown Lint Passed

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

lan17 commented Mar 12, 2026•
edited
Loading

github-actionsBot commented Mar 12, 2026•
edited
Loading

github-actionsBot commented Mar 12, 2026•
edited
Loading

lan17 commented Mar 12, 2026•
edited
Loading

github-actionsBot commented Mar 12, 2026•
edited
Loading

github-actionsBot commented Mar 12, 2026•
edited
Loading

lan17 commented Mar 12, 2026•
edited
Loading

github-actionsBot commented Mar 12, 2026•
edited
Loading

github-actionsBot commented Mar 12, 2026•
edited
Loading