fix: stabilization batch 4 — generator wiring, time.Time imports, error formatting, CI YAML

[sazardev]

Stabilization batch 4 — deep audit + cross-cutting fixes

This continues the stabilization effort (batches 1–3). I exhaustively exercised every generator command against real, freshly-generated projects — init, entity, usecase, repository, handler, feature, di, integrate, interfaces, mocks, messages, middleware, test-integration, ci, config, analyze, doctor, upgrade, template — across all database backends, then compiled (go build/go vet), ran the generated tests, and read the output for correctness. Findings were reproduced before fixing.

✅ Verified result of this PR

A full feature pipeline (init → feature User --fields "...,joined:time.Time" --validation) now builds + vets + passes generated tests on all six databases — sqlite, postgres, mysql, postgres-json, sqlserver, mongodb (matrix: 6/6 pass, previously several failed to compile). Two-feature projects and --cache projects also compile and test clean. Full go test ./... on the goca repo is green.

---

Fixed in this PR

Critical compile breakers

1. Repository constructor wiring broke every non-Postgres backend. di, feature, integrate and test-integration all referenced NewPostgres<Entity>Repository, but the repository generator emits NewPostgresJSON…, NewSQLServer…, NewMongo…, etc. → undefined: repository.NewPostgres… for postgres-json/sqlserver/sqlite/mongodb. Introduced a single repoConstructorPrefix(database) helper used everywhere.
2. feature hardcoded "postgres" when creating a new DI container and never threaded the chosen --database through updateDIContainer/addFeatureToDI/addSetupMethodsToDI.
3. SQLite was structurally un-wireable. Generated main.go/DI hold a *gorm.DB (gorm.io/driver/sqlite), but the repository used a bespoke database/sql (*sql.DB) impl that could never be injected. Routed SQLite through the shared GORM generator (as MySQL already is). Default DB now works end-to-end.
4. MongoDB container scaffold used NewContainer(db) but mongo main.go exposes mongoClient (no db). Now derives mongoClient.Database(cfg.Database.Name).
5. usecase DTOs with time.Time emitted time.Time fields without importing "time" → dto.go: undefined: time.
6. entity unit tests (default --tests) failed to compile / always failed for common fields: missing "time" import, invalid Priority{} composite literal for string-based custom-type stubs, and assert.Equal(time.Now(), field) that can never pass. Now imports time when needed, uses a string-conversion zero literal, and asserts the field is non-zero.

go vet breakers

7. Repository error formatting: SQLite/SQL Server/DynamoDB/Elasticsearch impls wrote literal %%w (so err was never wrapped) and SQL Server FindByID wrote fmt.Errorf("%s not found") with no argument. Emit %w / substitute the entity name.

Other

8. goca ci produced an invalid test.yml — the step-level env: block was indented at 6 spaces while sibling step keys use 8, so GitHub Actions rejected the file. Fixed indentation; now valid YAML.
9. --cache added to an existing DI container emitted c.redisClient/time references the container didn't provide. Now only wires the decorator when a decorator file exists and the container has a redisClient field; otherwise wires the bare repo so the project always compiles.

Tests updated/added accordingly (addSetupMethodsToDI cache pre-conditions, DB-threading callers).

---

Documented but NOT fixed here (follow-up batch 5)

Reproduced during the audit; left for a focused follow-up to keep this PR reviewable:

• handler --type grpc / feature --handlers grpc: the //go:build proto server imports a pb package that is never generated; go mod tidy/go vet ignore build tags and fail to resolve it, breaking the whole module. Needs a no-op stub package or to defer the server file until protoc runs.
• --cache (first feature): decorator file is generated but the generateDI path is called with cache=false, so the decorator/redis client are never wired (orphaned). Needs full redisClient scaffolding in NewContainer + main.go.
• --middleware-types / --middleware: generates an internal/middleware package that is never imported; routes duplicate inline cors/logging and never apply recovery. In some paths routes.go calls middleware.CORS(...) without importing the package.
• interfaces --handler/--all: emits undefined: User (references a bare *User); --repository/--usecase interfaces drift from the real generated implementations.
• Swagger annotations reference non-existent usecase types (usecase.GetUserOutput, usecase.ListUsersOutput); comment-only, so swag init fails but build is fine.
• Elasticsearch FindAll/FullTextSearch decode the response then return an empty slice (always empty results).
• init --template: all templates produce byte-identical Go code (only .goca.yaml differs); microservice/monolith/enterprise features not delivered. .goca.yaml database.port is always 5432; template .goca.yaml hardcodes type: postgres regardless of --database.
• Custom templates (goca template init + edit) are never consumed by generation.
• Dead flags: usecase --dto-validation, repository --implementation, handler --validation have no observable effect.
• messages writes errors to messages.go and constants to internal/constants/ (mismatch vs docs); --dry-run creates empty dirs.
• test-integration --database doesn't affect helpers.go (always imports all drivers).
• Exit codes: middleware/config validate/config init/template show/doctor print errors but exit 0 (breaks CI gating).
• Wide doc drift in wiki/ (Gin vs gorilla/mux, default db, JWT version, file layout).

Note: analyze --output json was reported as polluted but could not be reproduced — it already routes human output to stderr and emits valid JSON on stdout.

🤖 Generated with Claude Code