feat: managing-generators + managing-transforms integration-layer rules

CHANGELOG.md

@@ -4,6 +4,69 @@ All notable changes to this project will be documented in this file.
 
 The format is based on [Keep a Changelog](https://keepachangelog.com/).
 
+## [Unreleased]
+
+### managing-generators
+
+- New rule `python-relationship-references` covering the three
+  accepted forms for relationship fields in
+  `self.client.create()` (HFID dict, ID dict, SDK object) plus
+  the bare-string and over-packed-list anti-patterns.
+- New rule `python-multi-peer-add` explaining that
+  `RelationshipManager.add()` takes one peer per call; iterate
+  the peer list.
+- New rule `patterns-natural-key-preflight` covering form-driven
+  mutations that collide with bootstrap-seeded keys.
+- New advisory rule `testing-integration` recommending
+  end-to-end runs against a live instance before merge.
+- Fixed misleading `device_type_id` example in `python-generate`
+  that suggested bare-string relationship values.
+- Added 5 deterministic evals + 4 graders to `eval.yaml` (first
+  evals for this skill).
+
+### managing-transforms
+
+- New rule `queries-union-fragments` documenting the need for
+  GraphQL inline fragments on union-typed relationships
+  (`DcimDevice.location`, `Organization*` peers) to avoid
+  "Cannot query field 'X' on type 'Y'" failures in
+  CoreRepository schema-sync.
+- New rule `artifacts-async-regen-polling` documenting that
+  `POST /api/artifact/generate` is fire-and-forget and
+  programmatic callers must poll `CoreArtifact` to confirm
+  completion.
+- Added 2 deterministic evals + graders to `eval.yaml` (first
+  evals for this skill).
+
+### Hook (session-start)
+
+- Added per-path skill activation triggers to the
+  SessionStart hook's `additionalContext`. When the user
+  touches `generators/**`, `transforms/**`, `queries/**`,
+  `checks/**`, `objects/**`, `menus/**`, or `.gql` files, the
+  hook now explicitly tells Claude to read the corresponding
+  skill (with specific rule files) before editing. The trigger
+  block opens with a rationale — integration-layer rules live
+  in the skills, not in source, so pattern-matching produces
+  bugs that pass unit tests but fail at runtime.
+
+### infrahub-common
+
+- New rule `deployment-gql-dry-run` recommending that any PR
+  touching `queries/**/*.gql` runs `infrahubctl render
+  --dry-run` (or the equivalent check/generator run) against
+  a live Infrahub schema before merge. YAML schema validation
+  and Python type checking don't catch GraphQL query/schema
+  mismatches; only a live dry-run does. This is the failure
+  class that hides behind silent CoreRepository
+  schema-sync hangs.
+
+### Notes
+
+- `skillgrade --smoke` was not run in this branch (skillgrade
+  CLI not installed in the dev environment). Run before merging
+  to baseline pass rates against the new evals.
+
 ## [1.1.0] - 2026-03-18
 
 ### Added