atdd 0.4.4__tar.gz → 0.4.5__tar.gz

{atdd-0.4.4/src/atdd.egg-info → atdd-0.4.5}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: atdd
-Version: 0.4.4
+Version: 0.4.5
 Summary: ATDD Platform - Acceptance Test Driven Development toolkit
 License: MIT
 Requires-Python: >=3.10
@@ -58,14 +58,20 @@ atdd --help
 ```bash
 atdd init                      # Initialize ATDD in your project
 atdd gate                      # ⚠️ START EVERY SESSION WITH THIS
-atdd session new <capability>    # Create a planning session
+atdd session new <task>        # Create a planning session
 atdd sync                      # Sync rules to agent config files
 atdd validate                  # Run all validators
 ```
 
 > **⚠️ `atdd gate` is required.** 
 > 🤖 Tell your agent: "Run `atdd gate` and follow ATDD rigorously." 
-> Agents skip instruction files but can't ignore tool output. No gate = no ATDD guarantees.
+> Agents skip instruction files but can't ignore tool ou
+
+
+
+
+
+tput. No gate = no ATDD guarantees.
 
 ## What It Does
 
@@ -232,14 +238,16 @@ atdd validate --html       # With HTML report
 
 ### Release Versioning
 
-ATDD enforces release versioning via coach validators. Configure the version file and tag prefix in `.atdd/config.yaml`:
+ATDD enforces release versioning via coach validators. Recommended: keep a single root `VERSION` file as the canonical source (first line like `1.2.3 - short summary`; trailing summary is ignored). Configure the version file and tag prefix in `.atdd/config.yaml`:
 
 ```yaml
 release:
-  version_file: "pyproject.toml"  # or package.json, VERSION, etc.
+  version_file: "VERSION"  # recommended single source of truth
   tag_prefix: "v"
 ```
 
+If you also publish with language-specific manifests (e.g., `pyproject.toml`, `package.json`), keep their version fields in sync with `VERSION`.
+
 Validation (`atdd validate coach` or `atdd validate`) requires:
 - Version file exists and contains a version
 - Git tag on HEAD matches `{tag_prefix}{version}`

{atdd-0.4.4 → atdd-0.4.5}/README.md

@@ -44,14 +44,20 @@ atdd --help
 ```bash
 atdd init                      # Initialize ATDD in your project
 atdd gate                      # ⚠️ START EVERY SESSION WITH THIS
-atdd session new <capability>    # Create a planning session
+atdd session new <task>        # Create a planning session
 atdd sync                      # Sync rules to agent config files
 atdd validate                  # Run all validators
 ```
 
 > **⚠️ `atdd gate` is required.** 
 > 🤖 Tell your agent: "Run `atdd gate` and follow ATDD rigorously." 
-> Agents skip instruction files but can't ignore tool output. No gate = no ATDD guarantees.
+> Agents skip instruction files but can't ignore tool ou
+
+
+
+
+
+tput. No gate = no ATDD guarantees.
 
 ## What It Does
 
@@ -218,14 +224,16 @@ atdd validate --html       # With HTML report
 
 ### Release Versioning
 
-ATDD enforces release versioning via coach validators. Configure the version file and tag prefix in `.atdd/config.yaml`:
+ATDD enforces release versioning via coach validators. Recommended: keep a single root `VERSION` file as the canonical source (first line like `1.2.3 - short summary`; trailing summary is ignored). Configure the version file and tag prefix in `.atdd/config.yaml`:
 
 ```yaml
 release:
-  version_file: "pyproject.toml"  # or package.json, VERSION, etc.
+  version_file: "VERSION"  # recommended single source of truth
   tag_prefix: "v"
 ```
 
+If you also publish with language-specific manifests (e.g., `pyproject.toml`, `package.json`), keep their version fields in sync with `VERSION`.
+
 Validation (`atdd validate coach` or `atdd validate`) requires:
 - Version file exists and contains a version
 - Git tag on HEAD matches `{tag_prefix}{version}`

{atdd-0.4.4 → atdd-0.4.5}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "atdd"
-version = "0.4.4"
+version = "0.4.5"
 description = "ATDD Platform - Acceptance Test Driven Development toolkit"
 requires-python = ">=3.10"
 readme = "README.md"

{atdd-0.4.4 → atdd-0.4.5}/src/atdd/coach/templates/SESSION-TEMPLATE.md

@@ -348,7 +348,7 @@ Rules:
 -->
 
 - [ ] Determine change class: PATCH / MINOR / MAJOR
-- [ ] Bump version in version file (pyproject.toml, package.json, etc.)
+- [ ] Bump version in version file (recommended: VERSION; sync any language manifests if used)
 - [ ] Commit: "Bump version to {version}"
 - [ ] Create tag: `git tag v{version}`
 - [ ] Push with tags: `git push origin {branch} --tags`

{atdd-0.4.4 → atdd-0.4.5}/src/atdd/coach/validators/test_release_versioning.py

@@ -62,6 +62,12 @@ def _read_version_from_file(path: Path) -> str:
         version = _parse_package_json_version(path)
     else:
         version = _parse_plain_version(path)
+        if not version:
+            pytest.fail(
+                f"Could not read version from {path}. "
+                "Expected first non-comment line to contain a semver like "
+                "'1.2.3' or '1.2.3 - short summary'."
+            )
 
     if not version:
         pytest.fail(f"Could not read version from {path}")
@@ -127,11 +133,17 @@ def _parse_package_json_version(path: Path) -> Optional[str]:
 
 
 def _parse_plain_version(path: Path) -> Optional[str]:
+    version_pattern = re.compile(
+        r"\bv?(?P<version>\d+\.\d+(?:\.\d+)?(?:-[0-9A-Za-z.-]+)?(?:\+[0-9A-Za-z.-]+)?)\b"
+    )
     for line in path.read_text().splitlines():
         stripped = line.strip()
         if not stripped or stripped.startswith("#"):
             continue
-        return stripped
+        match = version_pattern.search(stripped)
+        if match:
+            return match.group("version")
+        return None
     return None
 
 

{atdd-0.4.4 → atdd-0.4.5/src/atdd.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: atdd
-Version: 0.4.4
+Version: 0.4.5
 Summary: ATDD Platform - Acceptance Test Driven Development toolkit
 License: MIT
 Requires-Python: >=3.10
@@ -58,14 +58,20 @@ atdd --help
 ```bash
 atdd init                      # Initialize ATDD in your project
 atdd gate                      # ⚠️ START EVERY SESSION WITH THIS
-atdd session new <capability>    # Create a planning session
+atdd session new <task>        # Create a planning session
 atdd sync                      # Sync rules to agent config files
 atdd validate                  # Run all validators
 ```
 
 > **⚠️ `atdd gate` is required.** 
 > 🤖 Tell your agent: "Run `atdd gate` and follow ATDD rigorously." 
-> Agents skip instruction files but can't ignore tool output. No gate = no ATDD guarantees.
+> Agents skip instruction files but can't ignore tool ou
+
+
+
+
+
+tput. No gate = no ATDD guarantees.
 
 ## What It Does
 
@@ -232,14 +238,16 @@ atdd validate --html       # With HTML report
 
 ### Release Versioning
 
-ATDD enforces release versioning via coach validators. Configure the version file and tag prefix in `.atdd/config.yaml`:
+ATDD enforces release versioning via coach validators. Recommended: keep a single root `VERSION` file as the canonical source (first line like `1.2.3 - short summary`; trailing summary is ignored). Configure the version file and tag prefix in `.atdd/config.yaml`:
 
 ```yaml
 release:
-  version_file: "pyproject.toml"  # or package.json, VERSION, etc.
+  version_file: "VERSION"  # recommended single source of truth
   tag_prefix: "v"
 ```
 
+If you also publish with language-specific manifests (e.g., `pyproject.toml`, `package.json`), keep their version fields in sync with `VERSION`.
+
 Validation (`atdd validate coach` or `atdd validate`) requires:
 - Version file exists and contains a version
 - Git tag on HEAD matches `{tag_prefix}{version}`