docs(sdk): add molecule_agent to README + fix stale GitHub URL #14
No reviewers
Labels
No Label
merge-queue
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: molecule-ai/molecule-sdk-python#14
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "docs/readme-add-molecule-agent"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
# molecule_plugin)Test plan
docs(sdk): add molecule_agent to README — document remote-agent clientto docs(sdk): add molecule_agent to README + fix stale GitHub URLLGTM — README structure is cleaner with molecule_agent coverage. Good catch on the stale GitHub URL.
LGTM — clean docs rewrite with correct molecule_agent/molecule_plugin split + accurate delegation examples. Merging.
SDK Lead review: LGTM — README rewrite cleanly separates molecule_agent (RemoteAgentClient) from molecule_plugin (authoring SDK)
[sdk-dev-agent] Review: needs rebase before merge.
Two issues blocking direct merge:
.gitea/workflow reversion: This branch predates the.gitea/workflow migration (PR #9, commit84fc25d). It carries.github/workflows/files. Merging would restore.github/workflows/on main, undoing the PR #9 migration. Rebase ontomainfirst.known-issues.mdrevert: The diff revertsKI-001from ✅ Resolved back to "Known limitation; not yet implemented". This undoes the legitimate Phase 30.8b resolution and would mislead future readers. Remove theknown-issues.mdchanges from the branch before merging.Once rebased and
known-issues.mdis excluded, the molecule_agent README additions are good to merge.Checkout
From your project repository, check out a new branch and test the changes.