Piagent Platform v1.51.2

One operating standard for the team

Each repository links the package, selects a fitting profile and keeps project documentation in its own repository.

Do

Ask the agent to read the project and record its context, apply /profile auto, assign work in plain language, run real checks, and state blockers clearly.

Avoid

Do not place tokens, authentication files, caches, sessions, private examples, or project-specific business logic in the public core package.

The final answer

A final response should briefly state what changed, which verification ran, whether subagents were used, and which risks or next steps require review.

Release documentation gate

A new docs version is promoted to Vercel only after tag-triggered CI passes and the stable dry run resolves the exact commit SHA. Promotion uses the tagged commit without an intervening merge or docs-only edit. The canonical domain is piagent.io.vn; the apex is the Vercel primary and www redirects to it.