Add godoc to Foundry MemoryProvider.Invoking and Invoked

[PratikDhanave]

What

Adds godoc comments to the two exported MemoryProvider methods in provider/foundryprovider/memory.go:

• Invoking — called before an agent run; searches the Foundry memory store for memories relevant to the incoming messages and returns them as additional context to inject into the run.
• Invoked — called after an agent run to persist the request and response messages as memory updates in the Foundry memory store.

Why

Every other exported symbol in the file (MemoryProviderConfig and its fields, MemoryProvider, NewMemoryProvider) is already documented. These two methods are the runtime entry points that satisfy the agent.ContextProvider interface, so their behavior should be discoverable via go doc. Documenting the interface entry points also keeps the Go provider aligned with the .NET/Python context-provider surfaces, whose equivalent invoking/invoked hooks carry XML/docstring documentation.

How tested

Documentation-only change (no code change). Verified with:

• go build ./...
• go vet ./provider/foundryprovider/...
• go test ./provider/foundryprovider/... (pass)
• go doc ./provider/foundryprovider MemoryProvider.Invoking and .Invoked now render the new text.

[Copilot]

Pull request overview

Adds GoDoc comments for the two exported MemoryProvider hook methods that implement the runtime entry points for Foundry-backed context injection and persistence.

Changes:

• Documented MemoryProvider.Invoking (pre-run memory search and context injection behavior).
• Documented MemoryProvider.Invoked (post-run request/response persistence as memory updates).

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[github-actions]

Cross-Repo Parity Review

This PR adds GoDoc comments to the existing Invoking and Invoked methods on MemoryProvider in provider/foundryprovider/memory.go. No exported types, method signatures, option shapes, or runtime behavior were changed.

Scope determination: Documentation-only change — no exported Go API surface was added, removed, or modified.

Parity verdict: ✅ No parity concerns. The Invoking/Invoked lifecycle hooks remain semantically aligned with the equivalent pre/post-invocation memory hooks in the upstream .NET and Python implementations. The added comments accurately describe the existing behavior (retrieve relevant memories before a run; persist messages after a run).

Warning

Firewall blocked 1 domain

The following domain was blocked by the firewall during workflow execution:

• awmgmcpg

To allow these domains, add them to the network.allowed list in your workflow frontmatter:

network:
  allowed:
    - defaults
    - "awmgmcpg"

See Network Configuration for more information.

Generated by Go API Consistency Review Agent · 21.9 AIC · ⌖ 3.93 AIC · ⊞ 5.9K · ◷