Skip to content

refactor: migrate production code to daemonapi v0.4.0#4

Merged
TeoSlayer merged 1 commit into
mainfrom
daemonapi-migrate
May 29, 2026
Merged

refactor: migrate production code to daemonapi v0.4.0#4
TeoSlayer merged 1 commit into
mainfrom
daemonapi-migrate

Conversation

@TeoSlayer
Copy link
Copy Markdown
Contributor

Production code now imports common/daemonapi instead of web4/pkg/daemon. Cycle structurally broken at the production import level. Tests still reference pkg/daemon for spin-up; that's a follow-up.

🤖 Generated with Claude Code

Every production .go file now imports common/daemonapi instead of
web4/pkg/daemon. Production code no longer requires web4 at all —
the structural cycle between runtime and the daemon engine is
broken at the import level.

Changes per file:

  events.go         daemonapi.Event subscription via daemonapi.EventBus
  handshake.go      HandshakeRuntime adapts daemonapi.Daemon (no longer
                    *daemon.Daemon) into handshake.Runtime
  identity.go       Identity / Sign through daemonapi.Daemon
  policy.go         PolicyRuntime adapts daemonapi.Daemon into
                    policy.Runtime
  policy_manager.go AsDaemonPolicyManager returns daemonapi.PolicyManager
  runtime.go        Runtime struct holds a daemonapi.Daemon (interface)
  streams.go        daemonListener uses daemonapi.Listener (Accept +
                    Port + Close methods); streamAdapter uses
                    Connection.Info() for endpoint accessors instead
                    of struct field access

Tests still reference pkg/daemon to spin up real daemons — kept as
a require + replace in go.mod for now; not on the production graph.
Migrating tests to use a fake daemonapi.Daemon implementation is a
follow-up.

go build ($prod) passes.
@TeoSlayer TeoSlayer merged commit cce9239 into main May 29, 2026
1 check failed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants