v0.5.49 - MCP review posting packet

MCP review posting packet

This release adds docs/MCP_REVIEW_POSTING_PACKET.md, a human-reviewed posting aid for asking one narrow MCP/tool-boundary review question without sounding promotional.

It includes:

• copy-ready short post for MCP-style tool-boundary review
• one-sentence field-level ask
• replies for compliance concerns, too-heavy feedback, and route suggestions
• link discipline: one primary link and at most two support links
• venue rules for avoiding cold tagging, cross-posting, and endorsement requests
• evidence recording rules for public route signals
• anti-claims for MCP compliance, AAIF endorsement, Linux Foundation endorsement, project status, adoption, and contributor credit

Boundary: no forum, LinkedIn, upstream, or external post was made by this release. This is a preparation artifact only. It does not claim MCP compliance, AAIF Ambassador acceptance, Agentic AI Foundation endorsement, Linux Foundation endorsement, maintainer approval, external adoption, or project proposal status.

Validation:

• npm test
• git diff --check
• ASCII scan over changed files

v0.5.48 - MCP tool boundary evidence checklist

MCP tool boundary evidence checklist

This release adds docs/MCP_TOOL_BOUNDARY_EVIDENCE_CHECKLIST.md as the second monthly ambassador-style educational artifact in the Agentic Enterprise Readiness Profile.

It gives maintainers a practical 20-minute path for documenting MCP-style and agent-callable tools:

• tool inventory and side-effect matrix
• input and output schema evidence
• MCP annotation mapping for readOnlyHint, destructiveHint, idempotentHint, and openWorldHint
• identity, tenant, token audience, and consent checks
• human approval gates for destructive, costly, identity-sensitive, public, or external actions
• audit, trace, result, and error evidence
• dry-run, mock, fixture, or local fallback expectations
• copy-ready reviewer ask

Boundary: this is an independent OSS educational artifact. It does not claim MCP compliance, production readiness, AAIF Ambassador acceptance, Agentic AI Foundation endorsement, Linux Foundation endorsement, maintainer approval, or external adoption.

Validation:

• npm test
• git diff --check
• ASCII scan over changed files

v0.5.47 - AGENTS.md enterprise evidence checklist

Adds the first monthly AAIF Ambassador-style educational artifact for the readiness profile: an AGENTS.md Enterprise Evidence Checklist.

Highlights:

• 20-minute implementation path for maintainers
• copy-ready AGENTS.md starter block
• tool/action boundary model
• human approval gates
• OSS fallback notes for paid provider dependencies
• one-comment reviewer ask and anti-claim boundaries

This is independent developer education. It does not claim AAIF Ambassador acceptance, AAIF endorsement, Linux Foundation endorsement, AGENTS.md maintainer approval, or external adoption.

Validation:

• npm test: Validated 16 readiness example(s).
• git diff --check: clean, with line-ending warnings only
• ASCII scan: passed for changed files

v0.5.46 - AAIF ambassador contribution plan

What changed

• Added docs/AAIF_AMBASSADOR_CONTRIBUTION_PLAN.md for monthly project-based educational contributions tied to AGENTS.md, MCP, Goose, and agentgateway.
• Linked the plan from README, public review packet, AAIF engagement dossier, community engagement plan, and the docs portal.
• Kept the boundary explicit: no AAIF Ambassador acceptance, AAIF endorsement, Linux Foundation endorsement, or official project status is claimed.

Proof

• npm test validates all 16 readiness examples.
• git diff --check passed locally with line-ending warnings only.
• No Docker was used.

v0.5.45 - AAIF forum posting packet

What changed

• Added docs/AAIF_FORUM_POSTING_PACKET.md as the human-facing posting aid for one concise AAIF/LF-adjacent public ask.
• Linked the packet from README, public review packet, AAIF engagement dossier, and the docs portal.
• Kept the boundary explicit: this is not endorsement, foundation status, a project proposal, working-group status, or contributor-list credit.

Proof

• npm test validates all 16 readiness examples.
• git diff --check passed locally with line-ending warnings only.
• No Docker was used.

v0.5.44 - proposal readiness review refresh

Proposal-readiness review refresh

This release refreshes the focused AAIF/LF-style proposal-readiness review path.

• updates the proposal preflight dossier and self-audit with the current focused review issue and release links
• updates the engagement dossier, public review packet, README, and docs portal
• keeps the proposal boundary explicit: public review ready and proposal-preflight ready, but not AAIF Growth-stage, Impact-stage, or working-group proposal ready
• keeps the ask technical: challenge missing evidence, routing fit, and maintainer burden before any formal foundation route

Validation:

• npm test validated 16 readiness examples

v0.5.43 - external reviewer call refresh

External reviewer call refresh

This release refreshes the external reviewer path so reviewers land on the current call and release surface.

• updates the external reviewer program with the current reviewer call and release links
• updates the external review guide, public review packet, README, and docs portal
• keeps the first action small: one lane, one artifact, one useful signal
• keeps the boundary explicit: reviewer feedback is not endorsement, adoption, certification, AAIF status, or Linux Foundation status

Validation:

• npm test validated 16 readiness examples

v0.5.42 - adoption trial intake refresh

Adoption trial intake refresh

This release refreshes the external adoption-trial path so reviewers land on the current intake issue and release surface.

• updates the adoption trial protocol with the current issue and release links
• updates the public review packet and operating queue with the fastest safe adoption-trial entry point
• surfaces the opt-in adoption-trial intake in README and the docs portal
• keeps the boundary explicit: a trial is not adoption, endorsement, certification, AAIF status, or Linux Foundation status

Validation:

• npm test validated 16 readiness examples

v0.5.41 - public routing discussion refresh

Changed

• Refreshed public discussion #3 so it points to the current release, docs portal, pinned first-review issue, route-signal template, A2A/interoperability routing, and anti-endorsement boundary.
• Linked the public discussion from README, public review packet, and docs portal as the broader technical-feedback path beside the one-signal issue.
• Updated public review packet routing language for AGENTS.md, MCP, A2A/interoperability, agentgateway, Goose, independent profile, and no-fit feedback.

Validation

• npm test passed locally and validated 16 readiness examples.
• git diff --check passed.
• Changed files were checked for ASCII-only content.

Boundary

This release improves public technical feedback routing. It does not claim AAIF endorsement, Linux Foundation endorsement, project adoption, certification, production readiness, or external reviewer recognition.

v0.5.40 - route signal intake refresh

Changed

• Refreshed the route-signal issue template with first-review context links, A2A/interoperability routing, one-sentence response shape, anti-claim checks, and public acknowledgement consent.
• Updated README, public review packet, review signal matrix, roadmap, docs portal, and package metadata to 0.5.40.
• Corrected the public review packet current-release link so external reviewers land on the current release surface.

Validation

• npm test passed locally and validated 16 readiness examples.
• git diff --check passed.
• Changed files were checked for ASCII-only content.

Boundary

This release improves the public reviewer entry point. It does not claim AAIF endorsement, Linux Foundation endorsement, project adoption, certification, production readiness, or external reviewer recognition.