Add v0.0.1 concept doc, README, ROADMAP, and implementation scaffold - #1
Conversation
- Architecture concept doc, README, ROADMAP, AGENTS.md dev reference - Package scaffold: models, in-memory registry, discovery, read-only API facade, CLI/console/config placeholders, thin adapter catalog - Tests, examples, CI + PyPI release workflows, contributing/security docs
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 4ea7758173
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| def get_agent(self, agent_id: str) -> AgentRecord: | ||
| return self._registry.get(agent_id) |
There was a problem hiding this comment.
When a caller mutates the result of get_agent()—for example, by assigning to status or editing capabilities—it mutates the exact AgentRecord held by _agents, bypassing registration and heartbeat handling; list_agents() exposes the same mutable aliases. Return deep copies or make exposed records immutable so this advertised read-only surface cannot silently alter registry state.
AGENTS.md reference: AGENTS.md:L92-L95
Useful? React with 👍 / 👎.
| release: | ||
| types: [published] | ||
| push: | ||
| tags: | ||
| - "v*" |
There was a problem hiding this comment.
When a version is both pushed as a tag and subsequently published as a GitHub Release, these two triggers start identical publishing runs for the same distribution filenames. The tag run can publish successfully, but the release run then attempts to upload that version again and PyPI rejects the duplicate; use a single release trigger or explicitly prevent the second publication.
AGENTS.md reference: AGENTS.md:L174-L180
Useful? React with 👍 / 👎.
1 participant
Summary
Verification
ruff check/ruff format --check/mypy --strict/pytestall pass cleanpython -m build+twine check dist/*passRelease plan
This branch brings the repo to the state described in
CHANGELOG.md's0.0.1entry (scaffold only, no new behavior). Once merged tomain, the next step is taggingv0.0.1to triggerrelease-pypi.ymlvia Trusted Publishing.