pycforge 1.3.45__tar.gz → 1.3.52__tar.gz

pycforge-1.3.52/AGENTS.md

@@ -0,0 +1,45 @@
+# PyCForge project instructions
+
+Read `PyCForge-README-Guidelines.txt` before any project update, conversion
+upgrade, README edit, or release preparation. CC's current requirements below
+apply throughout this source tree. Historical release notes, specifications,
+and evidence describe earlier work; they do not authorize restoring an older
+README, image URL, or version heading.
+
+1. PyCForge is not a GitHub project. CC alone uploads releases to PyPI from
+   CC's own computers. Do not publish from an assistant environment or add
+   GitHub hosting, repository links, or GitHub release workflows.
+2. The README permits exactly four image links, in this order: the top
+   PyCForge banner, the two current PyCForge UI screenshots, and the Crucible
+   engine banner directly below the Conversion bug tracker table. Their exact
+   approved URLs are recorded in `PyCForge-README-Guidelines.txt`. Add no other
+   links, including links to files inside the PyCForge project, relative paths,
+   local files, documentation, GitHub, navigation anchors, or mailto addresses.
+3. Preserve the clarity, useful information, concise professional style, and
+   structure of the v1.3.45 README. Update product information only when needed
+   for accuracy. Do not add development cycle status, phase or milestone
+   reports, pending-work lists, internal roadmaps, test counts, or build logs.
+4. After every PyCForge update, the top README version must match the actual
+   project release version, even when no other README information changes.
+   Never leave an old heading because the body did not need editing. Keep
+   historical screenshot labels and bug-fix versions accurate.
+   A previous release reached PyPI with an incorrect old README version.
+   To prevent a repeat, interpret CC's "no need to update the README during
+   upgrades" as preserving its prose and other content. It never means
+   freezing the version number at the top: always update that number to match
+   the new release before building the files CC will upload.
+5. Never remove any of the four approved image links or restore past image
+   links. The top PyCForge banner and bottom Crucible engine banner, including
+   their exact URLs, are permanent and never change. Preserve their respective
+   widths of 320 and 640 pixels and the Crucible subtitle.
+
+For every update, review the README diff, verify its heading against
+`pyproject.toml` and `pycforge/_version.py`, and run the existing README checks.
+For a release, also verify the README embedded in the wheel and source archive.
+Use `python -m tools.verify_pypi_readme` and
+`python -m tools.verify_public_distribution <release-directory>` as applicable.
+Do not weaken these checks or replace the approved image constants to make an
+unrequested README change pass. Check prose manually for development status.
+
+Retain this file and `PyCForge-README-Guidelines.txt` in the project root and
+future source archives. Carry both forward before continuing conversion work.