[DNM] refactor: significant pythonic restructuring preparing 0.7.x

[PsiACE]

Note

Preview / DNM.
This refactor does not correspond to any protocol update — it simply prepares the codebase for easier integration of future changes.

Summary

Bring in the 0.7.x changes, which resolve most points raised in #30.
Includes major refactoring and compatibility-preserving improvements — with special thanks to @frostming for the exceptional contributions.

Related issues

Closes #30

Testing

• Ran make check
• Ran make test
• Manual verification of example flows on 0.7.x
• Confirmed backward compatibility for existing import paths and common execution paths

Docs & screenshots

• No user-facing docs changed yet; full docs updates will come when 0.7.x is ready for release.
• This PR is opened as [DNM] to allow early review and tracking.

Checklist

• Conventional Commit title (chore: for DNM aggregation work)
• Tests cover the change or are not required (covered by existing 0.7.x refactor tests)
• Docs/examples updated when behaviour is user-facing (planned for release)
• Schema regenerations (make gen-all) not applicable at this stage

[frostming]

I’m considering whether we need to add a helper function that allows the agent to serve on a TCP host port pair and also make client connect to it. Is there a real use case for it? AFAIK it seems Zed only supports stdio streams.

[PsiACE]

I’m considering whether we need to add a helper function that allows the agent to serve on a TCP host port pair and also make client connect to it. Is there a real use case for it? AFAIK it seems Zed only supports stdio streams.

I believe this is useful. Having observed several instances of acp being utilised on SaaS platforms, I support it.

Additionally, we may need to consider how to address the changes introduced by this PR agentclientprotocol/agent-client-protocol#252

[frostming]

Additionally, we may need to consider how to address the changes introduced by this PR agentclientprotocol/agent-client-protocol#252

Hmm, the schema generation failed on the new json schema. Not sure whether it is an issue with the schema or generator.

[PsiACE]

Additionally, we may need to consider how to address the changes introduced by this PR agentclientprotocol/agent-client-protocol#252

Hmm, the schema generation failed on the new json schema. Not sure whether it is an issue with the schema or generator.

Just need to add a small guard in scripts/gen_schema.py that rewrites bare booleans under anyOf/allOf/oneOf to {}/{"not":{}} so datamodel-code-generator doesn’t choke. And I only checked the main schema so far — for the "unstable schema" parts, probably need to add a few small handlers as well.

[benbrandt]

@PsiACE I found a transform on my end that can rewrite these bools. will push it up

[PsiACE]

@PsiACE I found a transform on my end that can rewrite these bools. will push it up

Thanks, @benbrandt . That will make things a lot smoother for the Python generator.

Also, if it makes sense, I’d like to suggest adding @frostming to the Python team in the org . He’s done an exceptional amount of work — essentially a full rewrite of the SDK — and would be a great fit for long-term maintenance and reviews.