PERMANENT HANDOFF RULE — DEVELOPER PACKAGE NAMING AND FOLDER STRUCTURE

This rule is intentionally written into the package source/documentation so it
does not have to be restated in chat, handoff notes, or future sessions.

Correct developer-facing CloudFront package naming patterns:

  Descriptive package:
    s3-cloudfront-indexer-YYYY-MM-DD-HHMM-pdt-v096-large-touch-sort-headers.zip

  Short daily working package:
    s3-cloudfront-indexer-YYYY-MM-DD-HHMM-pdt-v096.zip

Required principles:

  1. The English project/package name comes first.
     Example: s3-cloudfront-indexer

  2. The developer-local date/time comes next.
     Timezone for Ken's development workflow:
       America/Los_Angeles
       PDT/PST as applicable

  3. The version remains prominent.
     Example: v096

  4. Extra change-note words are optional.
     Example: large-touch-sort-headers

  5. Every ZIP opens into exactly one clearly named top-level folder whose name
     matches the ZIP basename.

  6. Every developer package must include read-first files at the top of that
     folder:
       000-READ-FIRST-DEVELOPER-PACKAGING-RULE.txt
       000-START-HERE-PACKAGE-MAP.txt

  7. Do not use a bare timestamp first for these human-facing developer tool
     packages. The first visible words should identify what the package is.

  8. Do not rely on accidental sandbox, UTC, browser download, S3, or ZIP-tool
     timestamps as the only chronology. The filename itself must carry the
     developer-local chronology.

  9. Internal ZIP entry timestamps should be set consistently to the same
     developer-local build chronology when practical.

 10. This is a permanent handoff rule for future CloudFront/S3 directory browser
     packages unless the user explicitly overrides it.

Reason:

  Ken works with many daily app builds and CloudFront utility packages in the
  same dated S3/local folder. Packages must be immediately recognizable and
  chronologically sortable without confusion.