refactor(queue)!: own the redis connection instead of borrowing one

[juicycleff]

Groundwork for removing extensions/database. This was the last real compile-time dependency on it outside the extension itself.

What it was doing

The queue extension imported the database extension for exactly one reason. When DatabaseRedisConnection was set, it pulled a Redis client out of the database manager's pool instead of dialling its own:

dbManager, err := forge.InjectType[*database.DatabaseManager](container)
redisClient, err := dbManager.Redis(cfg.DatabaseRedisConnection)
queue, err = NewRedisQueueWithClient(cfg, logger, metrics, redisClient)

Note what that is: not a database, a Redis connection it borrowed from something that happened to hold one.

Why it is removed rather than migrated

It cannot move to grove. Grove has no Redis driver. It ships clickhouse, elasticsearch, mongo, mysql, postgres, sqlite and turso, and that is the whole list. There is nothing to point the borrowing at.

So the borrowing goes. NewRedisQueue already dialled its own connection and that path is now the only one, which is how every other driver in this extension already worked.

What changed

• extension.go: the import, the fail-fast check, and the borrowed-client branch are gone. Dependencies() now returns nil, because the queue owns every connection it uses.
• config.go: DatabaseRedisConnection, WithDatabaseRedisConnection, and the two validation branches that existed to let Redis skip url/hosts.
• redis.go: NewRedisQueue's guard no longer accepts a database connection as a substitute for url or hosts.
• go.mod: the require and the replace ../database.
• Three docs pages, plus the three tests that only covered the removed option.

Verification

go build, go vet and gofmt are clean. The suite passes apart from TestNATSQueue_PublishConsume, which needs a live NATS broker. I confirmed that one fails identically on unmodified main, so it is not from this change.

Breaking change

database_redis_connection is removed. If you were sharing a Redis connection with the database extension, give the queue its own url or hosts.

Not included

extensions/database still exists. Removing it also needs the CLI work in chore/cli-grove-migration and a decision about the nine model base types forge generate model emits, which have no grove equivalent.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
forge	Ready	Preview	Aug 18, 2026 1:33pm

[github-actions]

Conventional Commits Validation

PR Title: valid
Commits: all 1 follow conventional format