Post the deployed hfwatch public URL (stream A) — unblocks the TermiX agent-evidence chain

[fercodes]

Requested by: stream S. Owner: stream A (moises-cisneros).

Goal
Post the exact public base URL of the deployed hfwatch agent so the marketplace and the TermiX evidence chain can point at a live, registered agent. The agent is already deployed and registered (see PR #20: Cloudflare Worker hfwatch-agent, workers_dev = true, ERC-8004 token id 2292, chain id 97). The only missing fact is the concrete URL — the tasks ledger records it as https://-agent..workers.dev, and the account subdomain is known only to the deployer's Cloudflare account.
What to post
The URLs go in a comment on this issue (never in a commit). Post it as a JSON block in this exact shape:
{
"agent": "hf-watch",
"erc8004TokenId": "2292",
"endpoints": {
"a2a": "https://.workers.dev/.well-known/agent-card.json",
"mcp": "https://.workers.dev/mcp"
}
}
Replace the subdomain with the real one (visible in the Cloudflare Workers dashboard or in any prior wrangler deploy output). If the sibling agent URLs (rangekeeper, yieldrouter, gridrunner) are handy, post them too — they help the companion catalog issue — but only hf-watch is required to close this.
Acceptance criteria

• Both absolute URLs posted and publicly reachable: GET returns 200 with the A2A agent card; GET /mcp responds as an MCP endpoint
• The posted URL matches the on-chain ERC-8004 registration (read-only confirm: pnpm register -- --agent hfwatch --check, keystore-holder machine only — see the agent section)
• No repository changes made for this issue (pure coordination)
  What this unblocks

1. Stream S: the marketplace-hired agent leg of TermiX task 1 (health-factor monitoring) — the row feeding the 30% "proven agent advantage" criterion of the TermiX partner track (Agent Advantage Report, mandatory for prize eligibility).
2. Stream C: honest values for the two pending fields in agents/LISTING-HANDOFF.md and the matching fixture records (packages/indexer/fixtures/featured.json — companion catalog issue, filed separately for stream C).
3. Wed 9 submission: real endpoints replacing invented placeholders in evidence/SUBMISSION.md.
   Context for AI agents reading this
   If you are an agent acting on this issue:

• Your task is limited to (a) collecting the already-known URLs from the deployer (issue comments, their dashboard) and posting the JSON as a comment, or (b) explaining exactly what is still missing. Nothing else.
• The Cloudflare account subdomain is NOT derivable from the repository. Never guess, infer, or template-fill it. If the URLs are not already written in the repo or in a comment, the correct action is a human follow-up (Cloudflare dashboard), not a fabricated URL.
• Do not edit any file in any tree. packages/indexer/fixtures/featured.json belongs to stream C (companion catalog issue); agents/* changes are out of scope here.
• Do not run --check or any registration yourself: the keystore key is gitignored and exists on one machine only. If registration state must be inspected, request the human to run the read-only check.
• Verify before reporting success: curl must return the agent card JSON with HTTP 200; any other result means "not done".
• Grounding files, in reading order: agents/LISTING-HANDOFF.md (endpoint contract), agents/REGISTRATION.md (who can run what), evidence/task-01-health-factor/protocol.md (what gets unblocked).

[TOMOKI977]

Endpoints are now recorded and probed (HTTP 200 on ping / A2A / MCP) in agents/LISTING-HANDOFF.md via #27

• hf-watch: https://hfwatch-agent.moisescisnerosdl.workers.dev
• range-keeper: https://rangekeeper-agent.moisescisnerosdl.workers.dev
• yield-router: https://yieldrouter-agent.moisescisnerosdl.workers.dev
• grid-runner: https://gridrunner-agent.moisescisnerosdl.workers.dev

If this matches your Cloudflare account, this issue can close and Catalog can proceed on #26 with endpoints included.

[TOMOKI977]

Closing as done for Day-D win path: endpoints are in agents/LISTING-HANDOFF.md (PR #27), all four hosts probed HTTP 200, and Stream C can consume them via #26. No further coordination comment required.