Mark auto-generated files for GitHub linguist

[janniklasrose]

Changes

Extend linguist-generated=true coverage so generated files don't pollute language stats or show up as hand-written code in review. Follows the existing convention of one local .gitattributes per generated folder (alongside bundle/schema/, bundle/internal/tf/, bundle/internal/validation/generated/, acceptance/, integration/).

New / updated local files:

Generator	.gitattributes location	Pattern
./task generate-direct	bundle/direct/dresources/	*.generated.yml
./task generate-schema-docs	bundle/schema/ (extended)	jsonschema_for_docs.json
./task generate-schema	bundle/internal/schema/	annotations_openapi.yml
./task generate-docs	bundle/docsgen/output/	*.md
mockery	internal/mocks/	*.go
./task pydabs-codegen	python/databricks/bundles/	{catalogs,jobs,pipelines,schemas,volumes}/**

Excluded by request from review:

• internal/genkit/tagging.py{,.lock} and .github/workflows/tagging.yml — kept visible because changes there can affect the release process (@andrewnester).
• acceptance/**/out* and acceptance/**/output/** — kept visible because acceptance-output diffs are how reviewers detect behavior changes (@pietern, @andrewnester).

Why

bundle/direct/dresources/apitypes.generated.yml (and resources.generated.yml) were showing up as human-authored code on GitHub. The genkit-managed section of the root .gitattributes only covers cmd/account/** and cmd/workspace/**, so the rest of the auto-generated tree was unmarked. This brings linguist's view in line with .agent/rules/auto-generated-files.md.

Tests

Verified each pattern with git check-attr linguist-generated <path>:

• Intended generated files resolve to true.
• Adjacent manually-maintained files stay unspecified: bundle/direct/dresources/apitypes.yml, bundle/internal/schema/annotations.yml, bundle/internal/schema/annotations_openapi_overrides.yml, bundle/docsgen/{main.go,README.md}, bundle/schema/schema.go, internal/mocks/README.md, python/databricks/bundles/{__init__.py,build.py,core/**}.
• Pre-existing local .gitattributes files (TF schema, validation generated, bundle/schema/jsonschema.json, acceptance out.test.toml) still resolve correctly.

./task ws passes.

This PR was written by Claude Code.

[github-actions]

Approval status: pending

/bundle/ - needs approval

4 files changed
Suggested: @denik
Also eligible: @andrewnester, @pietern, @shreyas-goenka, @lennartkats-db, @anton-107

/internal/ - needs approval

Files: internal/mocks/.gitattributes
Suggested: @simonfaltum
Also eligible: @tanmay-db, @renaudhartert-db, @hectorcast-db, @parthban-db, @Divyansh-db, @tejaskochar-db, @mihaimitrea-db, @chrisst, @rauchy

General files (require maintainer)

Files: python/databricks/bundles/.gitattributes
Based on git history:

• @denik -- recent work in bundle/direct/dresources/, bundle/internal/schema/, python/databricks/bundles/

_{Any maintainer (@andrewnester, @anton-107, @denik, @pietern, @shreyas-goenka, @simonfaltum, @renaudhartert-db) can approve all areas.
See OWNERS for ownership rules.}

[pietern]

I like seeing these on all PRs because it forces you to acknowledge any side effects of the change.

Sometimes the unexpected behavior is captured only inside the output files.

[andrewnester]

I think all the output of the acceptance test is important to see explicitly as it helps to detect the changes in behaviour

[andrewnester]

I'd maybe keep this unhidden because if there's something changes here it can affect the release process