fixing broken links in identity and coffeeAgntcy

docs/coffee-agntcy/slim-coffee-agntcy.md

@@ -42,7 +42,7 @@ The `expected_responses` parameter defines how many replies the caller waits for
 You can explore the CoffeeAGNTCY code to see these concepts in context:  
 
 - **Client implementation** (message sending logic):  
-  [coffee_agents/lungo/exchange/graph/tools.py](https://github.com/agntcy/coffeeAgntcy/blob/main/coffeeAGNTCY/coffee_agents/lungo/exchange/graph/tools.py)  
+  [coffee_agents/lungo/agents/supervisors/auction/graph/tools.py](https://github.com/agntcy/coffeeAgntcy/blob/main/coffeeAGNTCY/coffee_agents/lungo/agents/supervisors/auction/graph/tools.py)
 
 - **Server implementation** (message handling logic):  
-  [coffee_agents/lungo/farms/brazil/farm_server.py](https://github.com/agntcy/coffeeAgntcy/blob/main/coffeeAGNTCY/coffee_agents/lungo/farms/brazil/farm_server.py)  
+  [coffee_agents/lungo/agents/farms/brazil/farm_server.py](https://github.com/agntcy/coffeeAgntcy/blob/main/coffeeAGNTCY/coffee_agents/lungo/agents/farms/brazil/farm_server.py)

docs/identity/arch_diagrams.md

@@ -8,7 +8,7 @@ The above diagram depicts the process for generating and storing a verifiable Ag
 
 - The top left of the image shows that an organization may have several sub-organizations, each of which may create its own Agent subjects.
 - As described in the [examples](./identifier_examples.md), each agent subject will be associated to an agent ID. More specifically, AGNTCY enables organizations to bring their own identities for their agents (for example, identities created via Okta, Duo, or A2A) as well as the capacity to generate an identity through AGNTCY, for example, using DIDs.
-- Each agent subject is required to use a schema to create an Agent definition (e.g., using an [OASF schema](../oasf/open-agentic-schema-framework.md) or an A2A [Agent Card](https://google.github.io/A2A/specification/agent-card/)). The agent ID must be included in the Agent Definition (see examples of agent IDs [here](./identifier_examples.md)).
+- Each agent subject is required to use a schema to create an Agent definition (e.g., using an [OASF schema](../oasf/open-agentic-schema-framework.md) or an A2A [Agent Card](https://a2a-protocol.org/latest/topics/key-concepts/)). The agent ID must be included in the Agent Definition (see examples of agent IDs [here](./identifier_examples.md)).
 - Each organization or sub-organization may create public and private key pairs, and store the private keys (PrivKeys) on their wallet or vault of choice, or other means enabling secure access to the PrivKeys.
 - A PrivKey owned and managed by an organization or sub-organization is required to create a ProofValue of the agent definition. As described in detail in the [Agent Badge Examples](./identifier_examples.md), the Agent Definition, the ProofValue, and additional metadata are used to create a Verifiable Credential in the form of a verifiable Agent Badge. Also note that, specific metadata, such as a verification method, an assertion method, and a service endpoint are used to create a `ResolverMetadata` object that is associated to the ID and the verifiable Agent Badge.
 

docs/identity/credentials.md

@@ -2,7 +2,7 @@
 
 AGNTCY supports various types of Verifiable Credentials (VCs). A verifiable credential is a structured and cryptographically verifiable way to express claims made by an issuer. These claims can pertain to:
 
-- Agent definitions (for example, an [OASF definition](../oasf/open-agentic-schema-framework.md) or an [A2A Agent Card](https://google.github.io/A2A/specification/agent-card/))
+- Agent definitions (for example, an [OASF definition](../oasf/open-agentic-schema-framework.md) or an [A2A Agent Card](https://a2a-protocol.org/latest/topics/key-concepts/))
 - Deployment configurations
 - Authorization assertions used in processes such as Multi-Factor Authentication (MFA)
 

docs/identity/identifier_examples.md

@@ -82,7 +82,7 @@ Hence, the A2A model may benefit from the use of verifiable identities and `Reso
 ID: A2A-Agent_ID
 ```
 
-In the [Agent2Agent (A2A) model](https://google.github.io/A2A/#/documentation), the `ID` could be represented by a URL, e.g., hosted at `https://YOUR-DOMAIN/.well-known/agent.json`, which links to a structured metadata file in the form of an [Agent Card](https://google.github.io/A2A/specification/agent-card/).
+In the [Agent2Agent (A2A) model](https://a2a-protocol.org/latest/#/documentation), the `ID` could be represented by a URL, e.g., hosted at `https://YOUR-DOMAIN/.well-known/agent.json`, which links to a structured metadata file in the form of an [Agent Card](https://a2a-protocol.org/latest/topics/key-concepts/).
 
 ### ResolverMetadata