docs: document the 1.52.0 feature wave (reference, concepts, dagster)#930
Merged
Conversation
… + 2 correctness fixes Adds coverage for features that shipped in engine 1.52.0 after the last docs overhaul, grounded against the source and verified file-by-file. Reference: - model-format.md: new [[surrogate_key]], [[tests]], [[use_test]], [[test]], and [columns.<name>] sidecar-block sections + group/[args] Fields-table rows. - cli.md + commands/modeling.md: the new rocky emit-sql verb (+ backfill catalog), the rocky test unit_tests summary, per-column description in catalog output, and a fully-populated compile models_detail example with a tags object. - json-output.md, configuration.md, glossary.md: unit_tests/tags/failures-shape notes, a config-groups pointer, and surrogate-key + config-group glossary entries. Concepts: testing.md (declarative + unit-test sections), data-quality-checks.md ([[test]] vs [[tests]] callout), sql-generation.md (surrogate-key SQL), and schema-patterns.md (config-groups vs source-schema-pattern distinction). Dagster: translator/derived-models/types/resource for the model-tag projection (get_model_tags), ModelDetail.tags, and the TestOutput/CiOutput aliases. Correctness fixes: - migrate-from-dbt.md: emitted [[test]] blocks now execute under rocky test as of engine-v1.52.0 (#899); the prior 'not yet wired' clause was stale. - testing.md: test failures are {name, error} objects, not positional tuples (#924).
This was referenced Jun 19, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
PR 1 of a 3-part sweep documenting the engine 1.52.0 feature wave, which shipped after the last docs overhaul and was almost entirely undocumented (found by a coverage audit). This PR covers the reference, concept, and dagster pages; a follow-up covers discovery/positioning pages, and a third adds runnable POCs.
Correctness fixes (these were wrong on
main)guides/migrate-from-dbt.md— removed the stale claim that emitted[[test]]blocks "aren't yet wired into rocky test execution." They execute as of engine-v1.52.0 (feat(engine): execute fixture-driven unit tests inrocky test#899). The still-true "CSV / SQL fixtures deferred" clause is preserved.concepts/testing.md— thefailuresexample showed the obsolete positional-tuple shape; it's now[{name, error}]objects (fix: address self-review findings across engine, rocky-sdk, and dagster #924), matching the generatedTestOutputschema and the other reference pages.Reference
model-format.md— five new sidecar-block sections:[[surrogate_key]],[[tests]],[[use_test]],[[test]],[columns.<name>], plusgroup/[args]rows in the Fields table. Per-column docs are scoped torocky catalog --output json(not therocky docsHTML, which has no column introspection).cli.md+commands/modeling.md— the newrocky emit-sqlverb (+ backfilledrocky catalog), therocky testunit_testssummary, the per-columndescriptionin catalog output, and a populatedrocky compilemodels_detailexample with atagsobject.json-output.md,configuration.md,glossary.md—unit_tests/tags/failures-shape notes, a config-groups cross-reference, and surrogate-key + config-group glossary entries.Concepts & Dagster
testing.md(declarative + unit-test sections),data-quality-checks.md([[test]]vs[[tests]]callout),sql-generation.md(surrogate-key SQL + dbt_utils parity),schema-patterns.md(config-groups distinction).dagster/{translator,derived-models,types,resource}— the model-tag projection (get_model_tags),ModelDetail.tags, and theTestOutput/CiOutputaliases.How this was produced & verified
15 files, one agent per file, each draft adversarially verified against the source (accuracy + de-AI prose standard), then a cross-link/terminology sweep. The verify pass caught real issues — e.g. a draft wrongly claimed
rocky cataloghas no JSON mode (it does;emit-sqldoesn't), and thecompileexample'ssignalsstring was checked verbatim against the live dagster fixture. +826 / −10 across 15 files (deletions are the two correctness rewrites + a couple of hedge phrasings).astro buildgreen (89 pages, no frontmatter/MDX/link errors).goldmatches are medallion-layer (schema: "gold",tier: "gold"), consistent with the existingbronze-layer/silver-layerdocs.🤖 Generated with Claude Code