Add YAML model property parsing

Author: sabino

.agent/research/m1-model-properties-slice.md

@@ -0,0 +1,29 @@
+# M1 Model Properties Slice
+
+## Scope
+
+This slice extends the native Zig M1 parser to read SQL-backed model properties from YAML files under configured model paths. It remains a deliberately small artifact-first subset, not a general YAML or Jinja implementation.
+
+Implemented surface:
+
+- Scalar model descriptions and dbt-shaped `patch_path`.
+- Simple column names and scalar descriptions.
+- Simple model and column test names parsed internally for later dbt-shaped test-node work.
+- Block-form `config.materialized`.
+- Block-form `config.tags` plus top-level inline `tags`.
+- `config.enabled: false` for SQL models.
+- Disabled SQL model representation under manifest `disabled`.
+- Loud failure when an active model `ref`s a disabled model.
+- dbt-compatible warnings, not fatal errors, for YAML model properties that do not match a discovered SQL model.
+
+## Compatibility Notes
+
+Active nodes exclude disabled models from `nodes`, `parent_map`, `child_map`, and `dxt ls`. Disabled SQL models are retained in `disabled` as a list under their model unique id, matching the dbt artifact shape more closely than silently dropping them.
+
+The YAML parser is intentionally subset-based. Unsupported richer property forms should fail or remain outside the advertised supported surface until a real YAML layer is introduced.
+
+Parsed generic tests are intentionally not written into model or column objects because dbt manifests represent them as separate `test.*` nodes. Emitting those nodes is a follow-up M1 compatibility slice.
+
+## Validation
+
+Focused fixtures cover model properties, columns, combined source/model YAML, disabled model representation, disabled ref diagnostics, and unmatched model-property warnings.

PLAN.md

@@ -513,8 +513,8 @@ Exit criteria:
 ## Current Status
 
 - M0 is under PR review as the Zig `0.16.0` runtime scaffold.
-- M1 has started on a stacked branch with a native Zig artifact-first parser slice.
-- `dxt parse` now targets the supported Tier 0 subset: project name/model paths, SQL model discovery, literal `ref`, literal `source`, inline `config(materialized=..., tags=...)`, dependency maps, and deterministic partial `manifest.json`.
+- M1 has started on stacked branches with native Zig artifact-first parser slices.
+- `dxt parse` now targets the supported Tier 0 subset: project name/model paths, SQL model discovery, literal `ref`, literal `source`, inline `config(materialized=..., tags=...)`, narrow YAML model properties for scalar descriptions, simple columns, tags, materialization, disabled SQL models, dependency maps, and deterministic partial `manifest.json`. Generic tests are parsed for later graph work but are not yet emitted as dbt-shaped `test.*` nodes.
 - `dxt ls` now lists resources from the same parser graph with stable text/JSON output and basic name, tag, path, resource type, and exact exclude filters.
-- Synthetic fixtures cover one model, model refs, source refs, inline config/tag selection, duplicate model diagnostics, unsupported dynamic ref diagnostics, and unsupported macro-call diagnostics.
-- The next M1 slices should add published schema validation, YAML model properties, disabled resources, docs blocks, macros, stronger selector parity, and Jaffle Shop DuckDB parse exploration.
+- Synthetic fixtures cover one model, model refs, source refs, combined source/model YAML, inline config/tag selection, YAML model properties and columns, disabled models, disabled ref diagnostics, unmatched model-property warnings, duplicate model diagnostics, unsupported dynamic ref diagnostics, and unsupported macro-call diagnostics.
+- The next M1 slices should add published schema validation, docs blocks, macros, stronger selector parity, and Jaffle Shop DuckDB parse exploration.

README.md

@@ -35,7 +35,7 @@ Implemented pre-alpha commands:
 ./zig-out/bin/dxt ls --project-dir tests/fixtures/model_ref --output json
 ```
 
-`parse` and `ls` currently support only the documented M1 parser subset: `dbt_project.yml` name/model paths/target path, SQL model discovery, literal `ref`, literal `source`, basic inline `config`, deterministic partial `manifest.json`, and simple name/tag/path/resource filters. `compile`, `build`, and `docs generate` remain planned placeholders.
+`parse` and `ls` currently support only the documented M1 parser subset: `dbt_project.yml` name/model paths/target path, SQL model discovery, literal `ref`, literal `source`, basic inline `config`, narrow YAML model properties for scalar descriptions, simple columns, tags, materialization and disabled SQL models, deterministic partial `manifest.json`, and simple name/tag/path/resource filters. dbt-shaped generic test nodes, `compile`, `build`, and `docs generate` remain planned placeholders.
 
 ## Development