Skip to content

Step 5: RockBot as Foragent's first real user#7

Merged
rockfordlhotka merged 2 commits intomainfrom
step/5-rockbot-first-user
Apr 22, 2026
Merged

Step 5: RockBot as Foragent's first real user#7
rockfordlhotka merged 2 commits intomainfrom
step/5-rockbot-first-user

Conversation

@rockfordlhotka
Copy link
Copy Markdown
Member

Summary

  • Pin docker-compose to rockylhotka/rockbot-agent:0.8.5 (first framework release carrying the step 1/3 fixes).
  • Seed post-to-site into deploy/rockbot-seed/well-known-agents.json and into agent-trust.json's approvedSkills so RockBot can both discover and invoke the third capability.
  • Refresh Gateway__Description from "fetch-page-title in step 1" to the three-skill current state.
  • Add docs/framework-feedback.md §"Step 5" section capturing the validation run + a new observation: agent-card metadata is now duplicated three ways (capability code, A2A/gateway options, rockbot-side seed).
  • Bump CLAUDE.md status to milestone 5.

No Foragent code changes — this milestone is about formalizing RockBot as the first real A2A consumer per spec §9.1.

Test plan

  • docker compose up --build with 0.8.5 rockbot-agent image starts cleanly on a fresh rockbot-data volume
  • GET /.well-known/agent-card.json exposes all three skills
  • fetch-page-title against https://example.com returns "Example Domain"
  • extract-structured-data (JSON body) round-trips through the LLM and returns {"heading":"Example Domain"}
  • post-to-site with unknown site returns safe dispatcher error listing known sites
  • post-to-site with configured site + missing credential returns "Credential '…' is not configured." (no value leak)
  • RockBot 0.8.5 container shows the updated seeds at /data/agent/agent-trust.json and /data/agent/well-known-agents.json
  • Blazor-driven LLM-reasoning leg (RockBot invokes Foragent via invoke_agent) — harness is running at http://localhost:8080 for ad-hoc validation; not gated on this PR
  • Real Bluesky post — deferred until FORAGENT_BLUESKY_* are populated in .env

🤖 Generated with Claude Code

Pin docker-compose to rockylhotka/rockbot-agent:0.8.5 (the latest framework
release carrying the step 1/3 fixes) and seed post-to-site into RockBot's
well-known-agents.json + agent-trust.json so all three skills are
discoverable and approved.

Validation ran through the full HTTP A2A gateway: agent-card, fetch-page-title,
extract-structured-data (LLM round-trip), and post-to-site up to broker
lookup / poster dispatch. Real Bluesky posting stays gated on FORAGENT_BLUESKY_*
credentials per user scope.

Framework-feedback step 5 section added. Main observation: agent-card
metadata is now duplicated three ways (capability code, A2A/gateway options,
rockbot-side seed) — candidate for a "discover peer card at first contact"
framework feature.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Original wording implied three places inside Foragent. The third copy
actually lives in rockbot-agent's well-known-agents.json peer registry
and is a framework design issue. Filed as rockbot#287. Separated the
trust-reseed observation since that's a distinct (related but
legitimate) problem.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@rockfordlhotka rockfordlhotka merged commit e1a2335 into main Apr 22, 2026
1 check passed
@rockfordlhotka rockfordlhotka deleted the step/5-rockbot-first-user branch April 22, 2026 03:03
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.

1 participant