Include the .agents folder during publish

[MikeAlhayek]

This pull request updates the deployment workflow to ensure that the .agents/skills directory (which contains agent skills) is correctly included in the published and deployed package. Previously, hidden files and folders like .agents/skills could be silently dropped during artifact upload, resulting in deployments missing required skills. The changes add steps to explicitly preserve .agents, remove all other hidden files, and verify that agent skills are present both before and after artifact upload.

Artifact packaging and verification improvements:

• Added a step to remove all hidden files and folders from the publish output except for .agents, ensuring only the required hidden directory is shipped.
• Enabled the include-hidden-files: true option for artifact upload to allow .agents to be included in the package.
• Added a verification step after pruning to confirm that at least one agent skill (SKILL.md) exists in .agents/skills before uploading the artifact.

Deployment package validation:

• Added a guard step after artifact download to verify that agent skills are still present in the deployment package, preventing deployments with missing skills.

[Piedone]

This looks like something that needs to be fixed in the packages, no? Because otherwise every consumer needs special care for publishing. You can do such copying from a package's .targets file.

[MikeAlhayek]

No. The package already includes it. The problem is that the deploy pipeline ignores or does not include the hidden folders like the package included .agents folder. So it does not publish it.

We need the pipeline to include it

[Piedone]

Okay. One issue though, that this will also upload any skills we may add to to this repo for local development as well.

[MikeAlhayek]

Yes. It will. I doubt this website will ever need skills though.