[EstebanGZam]

What changes

The shared agent assets in this repository are refreshed from microservice-app-ai-agents da9f2c7 and microservice-app-docs 305389a by scripts/sync-agent-assets.sh:

• .claude/skills/ and .agents/skills/;
• .agents/rules/;
• .specify/templates/, .specify/scripts/, and .specify/init-options.json;
• .specify/memory/constitution.md.

.specify/agent-assets.json is stamped with those commits. The diff is exactly what changed upstream.

Why

This repository carries copies of the shared assets instead of sibling symlinks (ai-agents specs/001-governance-and-iac-program T020). The sync workflow in microservice-app-ai-agents is meant to open this pull request. Its push to this repository was rejected, so the same change was pushed by hand, as described below.

Tasks

• ai-agents specs/001-governance-and-iac-program T020 — the distribution it established; no task changes.

• The task register is updated in this pull request — no register changes; the refresh completes no task.

• Every task ticked here was verified by locating its artifact — no task is ticked.

• Infrastructure changes: the documentation consulted through the required MCP servers is listed above

How it is verified

• Workflow run 34805893740 synced this repository from the two commits above. Its push was rejected by GitHub twice, on the first attempt and on the rerun, with remote: fatal error in commit_refs and ! [remote rejected] chore/sync-agent-assets -> chore/sync-agent-assets (failure). The other six repositories accepted the same push in the same run.
• The same change, pushed by the maintainer account, was accepted. scripts/sync-agent-assets.sh from microservice-app-ai-agents da9f2c7 was run locally against this repository's main (305389a). It produced the diff the app's rejected commit had: .agents/rules/iac/MTS-IAC-103-account-and-region-parameters.md, .agents/rules/iac/PC-IAC-024-configuration-traceability.md, and .specify/agent-assets.json, 3 files, +19/−7.
• The rejection is specific to the app's token here. This repository has no rulesets and no branch protection rules, and the app is installed on all repositories with contents: write. GitHub's status page reported git operations as operational. The cause is not yet known.
• tests/agent-assets.sh in microservice-app-ai-agents guards the sync script.
• No infrastructure code changes, so no MCP lookup applies.

Risk and rollback

Agent tooling files only. Closing the pull request skips this refresh; the next upstream change or the weekly run proposes it again.

What this PR does not do

It changes no application code, test, or workflow.

🤖 Generated with Claude Code