Add target schema and this compile context (#68)

Author: sabino

.agent/research/dbt-upstream-reference-map.md

@@ -47,7 +47,7 @@ Every compatibility slice should record:
 | YAML properties and resource patches | `core/dbt/parser/schemas.py::SchemaParser`, `SourceParser`, `PatchParser`, `ModelPatchParser`, `MacroPatchParser`; `core/dbt/parser/schema_yaml_readers.py::ExposureParser`, `MetricParser`, `SemanticModelParser`, `SavedQueryParser` | `crates/dbt-parser/src/resolver.rs::resolve_package_waves` resource order: sources, seeds, snapshots, groups, models, analyses, functions, exposures, semantic models, metrics, saved queries, data tests, unit tests | Current `src/project.zig` YAML routines and `src/project/parse.zig` helpers; future `src/project/parse.zig` plus narrower modules if needed |
 | Exposure, source, ref, metric dependency resolution | `core/dbt/parser/manifest.py::_process_refs`, `_process_sources_for_node`, `_process_sources_for_exposure`, `_process_metrics_for_node` | `crates/dbt-jinja-utils/src/node_resolver.rs::resolve_dependencies`; `crates/dbt-parser/src/resolver.rs` access validation, relation uniqueness, primary-key inference | `src/project/resolve.zig`; current higher-level orchestration still in `src/project.zig` |
 | Parse vs runtime Jinja context | `core/dbt/context/providers.py::ParseProvider`, `RuntimeProvider`, `ProviderContext.ref`, `source`, `execute`, `var`, `graph`, `env_var`, `selected_resources`, `generate_parser_model_context`, `generate_runtime_model_context`, `generate_parse_exposure`, `generate_parse_semantic_models` | `crates/dbt-parser/src/renderer.rs::render_sql_file_inner`, `augment_sql_resources_with_static_sources`; `crates/dbt-parser/src/dbt_namespace.rs::DbtNamespace` parse-mode interception of `get_relation` and `get_columns_in_relation` | Current lexical `src/project/jinja.zig`; future parse context and compile/runtime context modules before M2 |
-| Profile and adapter identity | `core/dbt/config/profile.py::Profile.pick_profile_name`, `render_profile`, `from_raw_profile_info`, `_get_profile_data`, `_credentials_from_profile`, `to_target_dict`; `core/dbt/config/runtime.py::load_profile`, `RuntimeConfig.get_metadata`; `core/dbt/context/target.py::TargetContext.target` | `crates/dbt-loader/src/load_profiles.rs::load_profiles`; `crates/dbt-profile/src/resolve.rs`; `crates/dbt-schemas/src/schemas/profiles.rs::DbConfig::adapter_type`; `crates/dbt-adapter-core/src/lib.rs::AdapterType` | `src/project/profile.zig` owns the current scalar `profiles.yml` adapter-type parser; `src/project/config.zig` owns `dbt_project.yml` `profile:`; future profile/context modules own Jinja rendering, credentials, target context, and relation identity |
+| Profile, target context, and relation identity | `core/dbt/config/profile.py::Profile.pick_profile_name`, `render_profile`, `from_raw_profile_info`, `_get_profile_data`, `_credentials_from_profile`, `to_target_dict`; `core/dbt/config/runtime.py::load_profile`, `RuntimeConfig.get_metadata`; `core/dbt/context/target.py::TargetContext.target`; `core/dbt/context/providers.py::ModelContext.this`, `generate_parser_model_context`, `generate_runtime_model_context`; `core/dbt/parser/base.py::ConfiguredParser.update_parsed_node_relation_names`, `_update_node_relation_name`; `core/dbt/compilation.py::Compiler._create_node_context`, `_compile_code`, `compile_node` | `crates/dbt-loader/src/load_profiles.rs::load_profiles`; `crates/dbt-profile/src/resolve.rs`; `crates/dbt-jinja-utils/src/phases/utils.rs::build_target_context_map`; `crates/dbt-schemas/src/schemas/profiles.rs::DbConfig::adapter_type`, `TargetContext`, `CommonTargetContext`; `crates/dbt-jinja-utils/src/phases/compile/compile_node_context.rs`; `crates/dbt-adapter-core/src/lib.rs::AdapterType`; `crates/dbt-adapter/src/relation/relation_impl.rs`; `crates/dbt-schemas/src/schemas/relations/base.rs` | `src/project/profile.zig` owns the current scalar `profiles.yml` adapter-type and schema parser; `src/project/config.zig` owns `dbt_project.yml` `profile:`; `src/project/compiler.zig` owns current two-part quoted relation rendering and narrow `target.*`/`this` compile expressions; future profile/context/relation modules own Jinja rendering, credentials, adapter-specific target fields, target database, include policy, custom schema/alias/database generation, and full relation identity |
 | Manifest data model and maps | `core/dbt/contracts/graph/manifest.py::Manifest` maps for nodes, sources, macros, docs, exposures, metrics, groups, selectors, files, disabled, semantic_models, unit_tests, saved_queries, fixtures; `build_flat_graph`, `build_parent_and_child_maps`, lookup rebuilders, resource adders | `crates/dbt-schemas/src/schemas/manifest/manifest.rs::build_manifest`, `build_disabled_map`, `build_parent_and_child_maps`, path normalization, `nodes_from_dbt_manifest` | `src/project/types.zig`, `src/project/manifest.zig`, `src/project/resolve.zig` |
 | Selector grammar and methods | `core/dbt/graph/selector_spec.py`, `selector.py`, `selector_methods.py`, `cli.py`, `graph.py`, `queue.py`; methods include FQN, tag, group, access, source, exposure, metric, semantic_model, saved_query, unit_test, path, file, package, config, resource_type, test_name, test_type, state, result, source_status, version, selector | `crates/dbt-parser/src/resolver.rs` selector YAML loading; command flags in `crates/dbt-clap-core/src/commands.rs` | `src/project/selector.zig` and CLI validation in `src/root.zig`; future state/result/source-status work in `src/project/state.zig` |
 | Artifact schemas | `schemas/dbt/manifest/v12.json`, `schemas/dbt/run-results/v6.json`, `schemas/dbt/sources/v3.json`, `schemas/dbt/catalog/v1.json` | v2 still emits JSON for compatibility and adds Parquet artifacts per README; manifest builder in `crates/dbt-schemas/src/schemas/manifest/manifest.rs` | `src/project/manifest.zig`, future run/catalog/source writers and schema validators under tests/scripts |
@@ -87,6 +87,11 @@ Every compatibility slice should record:
   `src/project/resolve.zig` for static `adapter.dispatch(...)`
   `depends_on.macros` extraction. This is documented in
   `.agent/research/m2-project-dispatch-config.md`.
+- Profile-derived target schema is parsed in `src/project/profile.zig`, copied
+  into the graph by `src/project/loader.zig`, and consumed by
+  `src/project/compiler.zig` for render-only model/ref relation names and
+  narrow `target.*` / `this` compile expressions. This is documented in
+  `.agent/research/m2-target-schema-this-compile.md`.
 - The test base includes native Zig tests for module-level helpers and pytest
   integration tests for CLI/artifact fixtures plus a pinned local Manifest v12
   schema slice.

.agent/research/m2-target-schema-this-compile.md

@@ -0,0 +1,117 @@
+# M2 Target Schema And This Compile Context Slice
+
+This slice extends dxt's render-only compiler with a narrow profile-derived
+target context and current-model relation context. It does not execute SQL,
+validate credentials, implement custom schema or alias generation, render
+arbitrary Jinja expressions, or open adapter connections.
+
+## Upstream References
+
+dbt Core v1, branch `1.latest`, commit `566b75d`:
+
+- `core/dbt/config/profile.py::Profile.render_profile` selects the target from
+  CLI override, profile `target:`, then `default`.
+- `core/dbt/config/profile.py::Profile.to_target_dict` exposes selected target
+  credentials plus `type`, `threads`, `name`, `target_name`, and
+  `profile_name`.
+- `core/dbt/context/target.py::TargetContext.target` defines the shared
+  `target` context, including `name`, `schema`, `type`, and `threads`.
+- `core/dbt/context/providers.py::ModelContext.this` exposes the current model
+  as an adapter relation; its documented values include `{{ this }}`,
+  `{{ this.schema }}`, `{{ this.table }}`, and `{{ this.name }}`.
+- `core/dbt/context/providers.py::generate_parser_model_context` and
+  `generate_runtime_model_context` keep the model context shape stable while
+  provider behavior changes between parse and runtime.
+- `core/dbt/parser/base.py::ConfiguredParser.update_parsed_node_relation_names`
+  and `_update_node_relation_name` assign relation names through the adapter
+  relation class after database, schema, and alias resolution.
+- `core/dbt/compilation.py::Compiler._create_node_context`, `_compile_code`,
+  and `compile_node` render raw SQL through the model context before writing
+  compiled output.
+
+dbt Core v2 / Fusion foundation, branch `main`, commit `0529e06`:
+
+- `crates/dbt-profile/src/resolve.rs::resolve_target`,
+  `resolve_with_env`, `ResolvedProfile::schema`, and
+  `ResolvedProfile::database` keep profile target resolution and default
+  database/schema identity as data.
+- `crates/dbt-jinja-utils/src/phases/utils.rs::build_target_context_map`
+  inserts `profile_name`, `name`, and `target_name` into the target map.
+- `crates/dbt-schemas/src/schemas/profiles.rs::TargetContext`,
+  `CommonTargetContext`, and `TryFrom<DbConfig> for TargetContext` define
+  common `database`, `schema`, `type`, and `threads`; DuckDB defaults missing
+  schema to `main`.
+- `crates/dbt-jinja-utils/src/phases/compile/compile_node_context.rs` builds
+  compile-time `this` relation data and exposes `this`, `database`, `schema`,
+  and `identifier`.
+- `crates/dbt-jinja-ctx/src/compile.rs::CompileNodeCtx` defines the typed
+  compile context contract.
+- `crates/dbt-adapter/src/relation/relation_impl.rs` and
+  `crates/dbt-schemas/src/schemas/relations/base.rs` define adapter relation
+  rendering and include-policy behavior.
+
+## dxt Ownership
+
+- `src/project/profile.zig` parses selected profile output scalar `type` and
+  now scalar `schema`.
+- `src/project/types.zig` carries `Graph.target_schema` and
+  `AdapterIdentity.target_schema`.
+- `src/project/loader.zig` copies profile-derived target schema into the graph
+  before parser and compiler use.
+- `src/project/compiler.zig` owns the render-only relation formatter and the
+  narrow `target.*` / `this` expression surface.
+- `src/project.zig` keeps the compile orchestration path and assigns manifest
+  `relation_name` through the compiler.
+
+## Supported Surface
+
+- Select profile from CLI `--profile`, falling back to `dbt_project.yml`
+  `profile:`.
+- Select target from CLI `--target`, falling back to profile `target:`, then
+  `default`.
+- Read selected output scalar `schema`; default to `main` only for selected
+  DuckDB targets when missing.
+- Render supported model/ref relations with the graph target schema.
+- Render literal compile expressions:
+  - `target.name`
+  - `target.target_name`
+  - `target.schema`
+  - `target.type`
+  - `target.profile_name`
+  - `this`
+  - `this.schema`
+  - `this.name`
+  - `this.table`
+  - `this.identifier`
+
+## Unsupported Surface
+
+- General Jinja expression evaluation, filters, indexing, conditionals, loops,
+  concatenation, macro execution, and adapter calls.
+- Adapter-specific target fields such as database, dbname, project, dataset,
+  host, user, warehouse, or role.
+- Node-level custom schema, alias, database, config rendering, and
+  `generate_schema_name` / `generate_alias_name` / `generate_database_name`.
+- Ephemeral/deferred/unit-test `this`, operation context, source freshness
+  context, hooks, and materialization runtime behavior.
+- Adapter include policy beyond the current two-part quoted
+  `schema.identifier` model relation format.
+
+## Validation
+
+- Native Zig tests cover profile schema extraction/defaulting, target-schema
+  relation rendering for refs, and compile rendering for `target.*` plus
+  `this` fields.
+- Pytest fixture `profile_target_context` validates the native CLI compile
+  path, selected profile target schema/type/name/profile fields, ref rendering,
+  compiled SQL files, manifest `relation_name`, and manifest schema slice.
+- Schema validation is run against the fixture `manifest.json`.
+
+## Stop Conditions
+
+- Stop before adding arbitrary Jinja expression support.
+- Stop before implementing custom schema/alias/database semantics.
+- Stop before adding live adapter connections, materialization SQL execution,
+  catalog introspection, or run-results artifacts.
+- Stop if a fixture requires secrets, private profile values, live credentials,
+  or local absolute paths.

PLAN.md

@@ -329,6 +329,19 @@ root-project dispatch config parser. This slice lets static
 parse installed-package dispatch as root config, render Jinja in project config,
 or run adapters.
 
+Current target schema and `this` compile context source note:
+`.agent/research/m2-target-schema-this-compile.md` maps upstream dbt Core v1
+profile target context, model `this`, relation-name assignment, and compile
+context behavior plus Fusion target-context and compile-context references to
+dxt's narrow render-only implementation. This slice lets `compile`, `docs
+generate`, and run/build preflight compile selected models with profile-derived
+target schema, `target.name`, `target.target_name`, `target.schema`,
+`target.type`, `target.profile_name`, `this`, `this.schema`, `this.name`,
+`this.table`, and `this.identifier`. It does not implement arbitrary Jinja,
+adapter-specific target fields, custom schema/alias/database generation, live
+adapter connections, materialization execution, catalog introspection, or
+run-results artifacts.
+
 The next source-grounded M1/M2 slices after macro block variant support are:
 
 1. Extend the render-only artifact boundary to adapter-free docs generation:
@@ -361,8 +374,10 @@ The next source-grounded M1/M2 slices after macro block variant support are:
 5. Grow artifact schema coverage only alongside emitted fields, using v1 JSON
    schemas and v2 manifest builder behavior while keeping dxt-specific metadata
    out of dbt schemas.
-6. Add adapter relation identity and target context values after the render-only
-   compile boundary is stable, using v1 compile runner/compiler behavior plus
+6. Continue adapter relation identity beyond the current two-part
+   profile-schema relation rendering: database include policy, quoting config,
+   adapter-specific target fields, custom schema/alias/database generation, and
+   source/model relation parity, using v1 compile runner/compiler behavior plus
    v2 adapter core/SQL identity references.
 
 ## Fixture Ladder