backup-before-delivery

A project delivery archive captures the exact repository state by requiring a clean Git status, final conventional commit, and annotated tag, then generates a portable ZIP package and delivery record for verifiable proof and rollback capability.

A project delivery archive package should include the final source code, a LIVRAISON.md file containing deployment information and URLs, and performance scores, while explicitly excluding node_modules and .git directories to ensure portability.

Yes, tagging a project for delivery requires a clean Git repository state. The workflow mandates eliminating temporary files, validating build and lint checks, and finalizing conventional commits before creating an annotated delivery tag.

Git tagging for client delivery works by creating an annotated tag following the v[MAJOR].[MINOR].[PATCH]-[CLIENT] convention. This records the exact delivery state in the repository history, ensuring reproducibility and traceability for compliance audits.

The best way to ensure traceability is to combine a final conventional Git commit, an annotated version tag, and a generated delivery record with deployment documentation. This archive guarantees reproducibility and maintains history for compliance requirements.

Yes, you can generate a ZIP archive directly from a Git tag or as a complete archive including essential files. Both methods produce a portable package for delivery, but generating from a tag ensures the archive matches the exact certified commit state.