fix: a created resource answers with what names it

[ShocOne]

Every generated resource failed at apply. Each fix uncovered the next, which is why they arrive together.

1. The request body carried invented values

Fixture derivation read enum, advisory values and format — never the document's own example, which is the only thing a document says about a string whose shape it otherwise leaves to prose. A URL property declaring no format became "tfpfgen-test-stream-endpoint-url", and the API refused it.

- stream_endpoint_url = "tfpfgen-test-stream-endpoint-url"
+ stream_endpoint_url = "https://api.thousandeyes.otel-collector"

The example now wins over an invented name, and a number moves inside whatever bounds the document declares rather than always being 7.

One synthesised name is restored when preferring examples would otherwise leave an entity with no prefixed string at all — the audit's cleanup pass matches a live object by any one of its string fields carrying the prefix, so one is enough, and an entity whose every string is an example is indistinguishable from an object the toolkit did not create.

2. A wire fixture whose example carries a backtick

The generated const is a raw Go literal, which has no escape for one, so the file stopped being Go mid-value:

"suggestion": "The pattern ` / ` will never match anything, did you mean ` * ` instead?",

Latent until now — an invented tfpfgen-test- name can't contain a backtick. The literal is rendered in Go (raw where the value permits, interpreted where it does not) and the template embeds one finished expression.

3. No resource wrote its identity

With bodies the API accepts, creates began succeeding and failing later. The framework refuses a resource that declares an identity schema and returns without setting the identity, reporting it as a provider fault whatever the API did.

34  resources declare an IdentitySchema
 0  resources ever write resp.Identity

Create and Read now write it beside the state.

4. A create response of its own type was discarded whole

CreateMapsResponse required the create response type to be identical to the read model; where they differ the whole response was dropped, including the server-assigned id, so the settling read addressed the object by an empty string. The id is now taken from that response where the same accessor answers the same type on both — which is what makes the conversion settled for the read correct for it. Five resources; conversions are per-type, including APIToFrameworkUUID.

Why one PR

These four share render_resource.go and the crud template. Splitting them there would mean staging half a file.

Verified

make check green at 91.1%. Both pilot trees regenerate and pass postcheck (go mod tidy, go build, go vet): 1,931 files and 4,442 files.

🤖 Generated with Claude Code