a2acalling 0.6.73 → 0.6.75

package/src/server.js

@@ -28,6 +28,7 @@ const { A2AConfig } = require('./lib/config');
 const { UpdateManager } = require('./lib/update-manager');
 const { DashboardEventStore } = require('./lib/dashboard-events');
 const { CallbookStore } = require('./lib/callbook');
+const { buildAgentCard } = require('./lib/agent-card');
 const { spawn } = require('child_process');
 const { resolveTurnTimeoutMs } = require('./lib/turn-timeout');
 
@@ -968,6 +969,24 @@ app.use('/api/a2a', createRoutes({
   notifyOwner
 }));
 
+// A2A-76: Google A2A Agent Card — dynamically generated from config + disclosure
+app.get('/.well-known/a2a-agent-card', (req, res) => {
+  const agent = config.getAgent();
+  const manifest = getTopicsForTier('public');
+  const keypair = config.getKeypair();
+  const hostname = (agent && agent.hostname) || process.env.A2A_HOSTNAME || req.headers.host || 'localhost';
+  const protocol = req.protocol || 'https';
+  const card = buildAgentCard({
+    config: { ...agent, owner: agentContext.owner },
+    manifest,
+    publicKey: keypair ? keypair.publicKey : null,
+    serverUrl: `${protocol}://${hostname}`,
+    version: require('../package.json').version
+  });
+  res.set('Cache-Control', 'public, max-age=3600');
+  res.json(card);
+});
+
 app.get('/', (req, res) => {
   res.json({ service: 'a2a', status: 'ok', agent: agentContext.name });
 });

package/.maestro/inbox/release-workflow-spam.md

@@ -1,25 +0,0 @@
-# Ticket: Reduce Release Workflow Email Spam
-
-## Summary
-Consolidate or batch release workflows to reduce GitHub notification email volume
-
-## Problem
-Every commit/merge triggers a separate "Release (npm + GitHub) workflow run" notification email. During active development (like the current A2A-47/48/49 sprint), this floods the inbox.
-
-## Proposed Solution
-1. **Batch releases**: Only trigger release workflow once per PM run completion, not per-merge
-2. **Conditional triggers**: Skip release workflow for WIP branches, only run on main after all tickets in a batch are merged
-3. **Consolidate notifications**: Use GitHub's workflow_run event to chain workflows and send a single summary notification
-
-## Acceptance Criteria
-- [ ] Release workflow runs maximum once per maestro PM batch
-- [ ] No release emails for intermediate merges during a sprint
-- [ ] Single "Release complete" notification at end of batch
-
-## Labels
-- chore
-- dx
-- priority: medium
-
-## Team
-a2a calling