sdr-visualizer 1.2.3__tar.gz → 1.2.4__tar.gz

{sdr_visualizer-1.2.3 → sdr_visualizer-1.2.4}/CHANGELOG.md

@@ -4,6 +4,19 @@ All notable changes to `sdr-visualizer` will be documented here. The format foll
 
 ## [Unreleased]
 
+## [1.2.4] - 2026-10-17
+
+### Changed
+
+- Advance the catalog tested-through generator markers to `cja_auto_sdr`
+  3.12.12 and `aa_auto_sdr` 1.21.24. Snapshots declaring those versions no
+  longer raise a newer-than-tested warning; later versions remain accepted
+  with a compatibility warning. The separate lineage allowlist is unchanged.
+
+### Fixed
+
+- Label the lineage report footer “CJA lineage” instead of “Private CJA lineage POC”.
+
 ## [1.2.3] - 2026-10-16
 
 ### Fixed
@@ -739,7 +752,8 @@ The following are explicitly internal and may change without notice:
 - Workspace project visualization (v0.4)
 - Schema map view (v0.5)
 
-[Unreleased]: https://github.com/brian-a-au/sdr-visualizer/compare/v1.2.3...HEAD
+[Unreleased]: https://github.com/brian-a-au/sdr-visualizer/compare/v1.2.4...HEAD
+[1.2.4]: https://github.com/brian-a-au/sdr-visualizer/releases/tag/v1.2.4
 [1.2.3]: https://github.com/brian-a-au/sdr-visualizer/releases/tag/v1.2.3
 [1.2.2]: https://github.com/brian-a-au/sdr-visualizer/releases/tag/v1.2.2
 [1.2.1]: https://github.com/brian-a-au/sdr-visualizer/releases/tag/v1.2.1

{sdr_visualizer-1.2.3 → sdr_visualizer-1.2.4}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: sdr-visualizer
-Version: 1.2.3
+Version: 1.2.4
 Summary: Static-output visual catalog generator for Adobe Customer Journey Analytics and Adobe Analytics implementations.
 Project-URL: Homepage, https://brian-a-au.github.io/sdr-visualizer/
 Project-URL: Documentation, https://github.com/brian-a-au/sdr-visualizer#documentation

{sdr_visualizer-1.2.3 → sdr_visualizer-1.2.4}/docs/PRODUCT_CONTRACT.md

@@ -207,8 +207,8 @@ unusable, and capped-out members do not warn. The current markers are:
 
 | Platform | Warning threshold |
 |---|---:|
-| CJA (`cja_auto_sdr`) | 3.12.4 |
-| AA (`aa_auto_sdr`) | 1.21.15 |
+| CJA (`cja_auto_sdr`) | 3.12.12 |
+| AA (`aa_auto_sdr`) | 1.21.24 |
 
 A marker is evidence of exercised compatibility, not a promise about every
 possible snapshot produced by that version. It may advance only after a

{sdr_visualizer-1.2.3 → sdr_visualizer-1.2.4}/docs/RELEASE_EVIDENCE_TEMPLATE.md

@@ -200,7 +200,9 @@ cannot be closed by recording the current delta as diff-backed N/A.
 | Candidate SHA | pending |
 | Complete changed-path output permalink | pending |
 | Shared runtime paths changed | pending |
-| Full parity or diff-backed N/A evidence | pending |
+| Full parity review, marker-only disposition, or diff-backed N/A evidence | pending |
+| Marker-only: both projects' marker values and explicit-SHA adapter/helper review | pending |
+| Marker-only: fresh candidate qualification and literal warning-boundary evidence | pending |
 | Current sibling PR and commit permalinks, if applicable | pending |
 | Shared-contract comparator result, if applicable | pending |
 | Reviewer / reviewed UTC / result | pending |
@@ -252,7 +254,7 @@ renumber these requirements.
 | R15 shipped, consistent docs | Markdown links + source-distribution check | pending |
 | R16 safe sharing guidance | README review | pending |
 | R17 current compatibility | privacy-safe fresh/corpus record | pending |
-| R18 sibling parity | linked green sibling PR/commit and passing shared-contract comparator when color packs change | pending |
+| R18 sibling parity | full sibling review; linked green merged sibling PR/commit unless the marker-only disposition applies; shared-contract comparator when color packs change | pending |
 | R19 protected/monitored `main` | settings/API inspection | pending |
 | R20 complete community surface | community profile + advertised public-link resolution | pending |
 | R21 one traced candidate | this matrix + final go/no-go | pending |
@@ -312,20 +314,29 @@ renumber these requirements.
 ## Authoritative artifact and retention
 
 Use one artifact set throughout. Record every retry separately; never combine
-evidence from different attempts or manifests.
+evidence from different attempts or manifests. Inspect retention settings before
+tagging; inspect the created artifact's actual expiry before PyPI publication
+approval. A configured duration does not establish the actual recovery deadline.
+The actual expiry must cover the recorded full 90-day policy window; stop if it
+falls short. Record the window start and its basis rather than inferring them
+from a previous release's retention behavior.
 
 | Field | Value |
 |---|---|
 | Release workflow URL | pending |
 | Workflow run ID | pending |
 | Attempt | pending |
+| Workflow creation UTC | pending |
 | Event / tag / `headSha` | pending |
 | Job conclusions | pending |
 | Retained artifact ID | pending |
 | Artifact URL | pending |
-| Artifact expiry UTC | pending |
-| Repository retention setting and inspection URL | pending |
-| 90-day recovery-window end UTC | pending |
+| Artifact creation UTC | pending |
+| Actual artifact expiry UTC and inspection URL | pending |
+| Repository retention setting / workflow retention request / pre-tag inspection URL | pending |
+| Policy-window start UTC and basis | pending |
+| 90-day recovery deadline UTC | pending |
+| Actual expiry covers the full policy window / post-build inspection UTC | pending |
 | Wheel filename / SHA-256 | pending |
 | Source-distribution filename / SHA-256 | pending |
 | Authoritative `SHA256SUMS` manifest URL | pending |

{sdr_visualizer-1.2.3 → sdr_visualizer-1.2.4}/docs/RELEASING.md

@@ -238,6 +238,24 @@ Review changes to `core/models.py`, `adapters/`,
 Missing access or an unreviewed sibling change blocks release; it does not turn
 parity into an optional follow-up.
 
+A candidate whose changes to shared runtime paths are limited to
+`TESTED_THROUGH_GENERATOR_VERSION` values in the catalog adapters still requires
+full sibling review. Record the visualizer base and candidate SHAs, the sibling
+full SHA, complete candidate changed paths, exact adapter diff, and each project's
+marker values. Prove that the shared-path delta changes only those constant
+values, and compare the warning and version-parser helpers at those SHAs. Retain
+the documented intentional differences. Fresh exact-version snapshots, the full
+historical private corpus, supported catalog modes, and literal target/next-patch
+warning tests must pass for the visualizer candidate.
+
+Marker values are project-specific qualification evidence. Do not copy them to
+the sibling without that project's own qualification. When the review establishes
+that no shared implementation change needs mirroring, record **full review — no
+sibling code change required**; a new sibling PR and merge are not required for
+this limited case. This is not diff-backed N/A. Any other shared-runtime change
+follows the linked green, merged sibling requirement above. Color-pack comparator
+requirements remain unchanged.
+
 For `render/color_packs.py`, both repositories must export the same shared
 contract snapshot: `catalog` (`default`, `ADBE`, `OMTR`, `BLUE` in
 that order), ordered `source_swatches` for all four entries, and ordered
@@ -262,7 +280,8 @@ parity may be recorded as a **diff-backed N/A**. The record must include the
 base and candidate SHAs, the complete changed-path output, and a reviewer
 confirmation that no shared runtime surface changed. A documentation-only
 label or commit message is not sufficient evidence. Any shared-path change
-requires the full sibling review above.
+requires full sibling review; marker-only review may use the limited disposition
+above.
 
 ## GitHub and community controls
 
@@ -337,7 +356,7 @@ checklist remains authoritative.
 | R15 shipped, consistent docs | Markdown links + source-distribution check | pending |
 | R16 safe sharing guidance | README review | pending |
 | R17 current compatibility | privacy-safe fresh/corpus record | pending |
-| R18 sibling parity | linked green sibling PR/commit and passing shared-contract comparator when color packs change | pending |
+| R18 sibling parity | full sibling review; linked green merged sibling PR/commit unless the marker-only disposition applies; shared-contract comparator when color packs change | pending |
 | R19 protected/monitored `main` | settings/API inspection | pending |
 | R20 complete community surface | community profile + advertised public-link resolution | pending |
 | R21 one traced candidate | this matrix + final go/no-go | pending |
@@ -446,9 +465,23 @@ deploys again before announcement GO, repeat those checks against the newer
 deployment SHA.
 
 The authoritative workflow artifact must remain available throughout a
-90-day recovery window. Confirm repository retention and the artifact's actual
-expiry before approval; if either is shorter, stop and repair the recovery
-path before tagging.
+90-day recovery window. Before tagging, inspect the repository retention setting
+and workflow retention request; if either cannot support that window, stop and
+repair the recovery path before tagging. The artifact does not exist at this
+stage, so its actual expiry cannot yet be verified.
+
+After the build creates the authoritative artifact and before PyPI publication
+approval, record the workflow creation time, artifact creation time, policy-window
+start and its basis, actual artifact expiry, and recovery deadline. Verify that
+the actual expiry covers the full recorded 90-day window; if it falls short, stop
+publication approval and repair the recovery path. Retain the same artifact and
+manifest under the recovery rules below.
+
+In the [1.2.3 publication record](https://github.com/brian-a-au/sdr-visualizer/pull/89),
+the inspected artifact expired 90 days after workflow creation, rather than
+90 days after artifact creation. That is an observation about that release,
+not a guarantee about GitHub retention behavior or a universal policy-window
+anchor. Record and inspect these timestamps for every release.
 
 Every retry records its run ID, attempt, artifact ID, and manifest. Evidence
 from different artifact sets may never be combined.

{sdr_visualizer-1.2.3 → sdr_visualizer-1.2.4}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "sdr-visualizer"
-version = "1.2.3"
+version = "1.2.4"
 description = "Static-output visual catalog generator for Adobe Customer Journey Analytics and Adobe Analytics implementations."
 readme = "README.md"
 license = "MIT"

{sdr_visualizer-1.2.3 → sdr_visualizer-1.2.4}/src/sdr_visualizer/__init__.py

@@ -1,3 +1,3 @@
 """sdr-visualizer: visual catalog generator for CJA / AA implementations."""
 
-__version__ = "1.2.3"
+__version__ = "1.2.4"

{sdr_visualizer-1.2.3 → sdr_visualizer-1.2.4}/src/sdr_visualizer/adapters/aa.py

@@ -355,7 +355,7 @@ def _walk_segment_definition(definition: Any) -> tuple[int, list[str]]:
 # (bundled fixtures + the private real corpus; re-derive at each release:
 # grep -rho '"Tool Version": "[^"]*"|"tool_version": "[^"]*"' over corpus
 # and fixtures, take the max). The compatibility policy warns — never refuses.
-TESTED_THROUGH_GENERATOR_VERSION = "1.21.15"
+TESTED_THROUGH_GENERATOR_VERSION = "1.21.24"
 
 
 def generator_version_warning(adapter_version: str) -> str | None:

{sdr_visualizer-1.2.3 → sdr_visualizer-1.2.4}/src/sdr_visualizer/adapters/cja.py

@@ -367,7 +367,7 @@ def _walk_for_contexts(node: Any, out: list[str]) -> None:
 # (bundled fixtures + the private real corpus; re-derive at each release:
 # grep -rho '"Tool Version": "[^"]*"|"tool_version": "[^"]*"' over corpus
 # and fixtures, take the max). The compatibility policy warns — never refuses.
-TESTED_THROUGH_GENERATOR_VERSION = "3.12.4"
+TESTED_THROUGH_GENERATOR_VERSION = "3.12.12"
 
 
 def generator_version_warning(adapter_version: str) -> str | None:

{sdr_visualizer-1.2.3 → sdr_visualizer-1.2.4}/src/sdr_visualizer/render/templates/cja_lineage.html.j2

@@ -176,7 +176,7 @@
     <span class="separator">·</span>
     <span>Color pack: {{ color_pack }}</span>
     <span class="separator">·</span>
-    <span>Private CJA lineage POC</span>
+    <span>CJA lineage</span>
   </footer>
 
   <script id="sdr-lineage-data" type="application/json">{{ payload_json | safe }}</script>

{sdr_visualizer-1.2.3 → sdr_visualizer-1.2.4}/tests/test_cli.py

@@ -1096,3 +1096,33 @@ def test_tested_generator_version_does_not_warn(tmp_path, capsys):
     )
     assert rc == 0
     assert "generator version" not in capsys.readouterr().err
+
+
+@pytest.mark.parametrize(
+    ("platform", "version", "warns"),
+    [
+        ("cja", "3.12.12", False),
+        ("cja", "3.12.13", True),
+        ("aa", "1.21.24", False),
+        ("aa", "1.21.25", True),
+    ],
+)
+def test_catalog_generator_warning_boundary(platform, version, warns, tmp_path, capsys):
+    snapshot = json.loads(
+        (FIXTURES / f"{platform}_snapshot_clean.json").read_text(encoding="utf-8")
+    )
+    if platform == "cja":
+        snapshot["metadata"]["Tool Version"] = version
+    else:
+        snapshot["tool_version"] = version
+    source = _write_json(tmp_path / "snapshot.json", snapshot)
+    output = tmp_path / "report.html"
+
+    assert main([str(source), "--output", str(output), "--quiet"]) == 0
+    assert output.is_file()
+    stderr = capsys.readouterr().err
+    if warns:
+        assert f"snapshot generator version {version}" in stderr
+        assert "newer" in stderr
+    else:
+        assert "generator version" not in stderr

{sdr_visualizer-1.2.3 → sdr_visualizer-1.2.4}/tests/test_lineage_renderer.py

@@ -399,6 +399,8 @@ def test_lineage_renderer_uses_visualizer_shell_and_color_pack_contract(code: st
     assert 'class="meta-strip ui"' in html
     assert 'class="view-nav ui"' in html
     assert 'class="footer ui"' in html
+    assert "<span>CJA lineage</span>" in html
+    assert "Private CJA lineage POC" not in html
     assert html.index("/* ---------- Reset & base ---------- */") < html.index(css)
     assert html.index(css) < html.index("</style>")