engineering-process 1.2.3__tar.gz → 1.2.4__tar.gz

{engineering_process-1.2.3/engineering_process.egg-info → engineering_process-1.2.4}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: engineering-process
-Version: 1.2.3
+Version: 1.2.4
 Summary: A small agent-neutral engineering lifecycle with managed adoption
 License-Expression: MIT
 Project-URL: Homepage, https://github.com/phuongnse/engineering-process
@@ -352,6 +352,10 @@ URL; without it, the review remains pending. Earlier plan and review documents r
 readable, and their runs remain registrable or finishable with the version selected by
 the authority that started the relevant phase.
 
+The [finding priority definitions](process_assets/skills/review-change/SKILL.md#finding-priority)
+are the canonical P0-P3 impact convention for this process, including examples and
+their relationship to blocking decisions.
+
 ## Running a change
 
 Create and validate a change contract, then register it:

{engineering_process-1.2.3 → engineering_process-1.2.4}/README.md

@@ -328,6 +328,10 @@ URL; without it, the review remains pending. Earlier plan and review documents r
 readable, and their runs remain registrable or finishable with the version selected by
 the authority that started the relevant phase.
 
+The [finding priority definitions](process_assets/skills/review-change/SKILL.md#finding-priority)
+are the canonical P0-P3 impact convention for this process, including examples and
+their relationship to blocking decisions.
+
 ## Running a change
 
 Create and validate a change contract, then register it:

{engineering_process-1.2.3 → engineering_process-1.2.4}/engineering_process/__init__.py

@@ -1,3 +1,3 @@
 """Agent-neutral engineering process."""
 
-VERSION = "1.2.3"
+VERSION = "1.2.4"

{engineering_process-1.2.3 → engineering_process-1.2.4/engineering_process.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: engineering-process
-Version: 1.2.3
+Version: 1.2.4
 Summary: A small agent-neutral engineering lifecycle with managed adoption
 License-Expression: MIT
 Project-URL: Homepage, https://github.com/phuongnse/engineering-process
@@ -352,6 +352,10 @@ URL; without it, the review remains pending. Earlier plan and review documents r
 readable, and their runs remain registrable or finishable with the version selected by
 the authority that started the relevant phase.
 
+The [finding priority definitions](process_assets/skills/review-change/SKILL.md#finding-priority)
+are the canonical P0-P3 impact convention for this process, including examples and
+their relationship to blocking decisions.
+
 ## Running a change
 
 Create and validate a change contract, then register it:

{engineering_process-1.2.3 → engineering_process-1.2.4}/process_assets/skills/review-change/SKILL.md

@@ -62,3 +62,28 @@ Follow-up scope is only carried findings, remediation diffs, and regressions aga
 the frozen contract. A new blocker must be either remediation-caused or a P0/P1 late
 violation with a rationale. After two correction cycles, another changes-requested
 verdict blocks the change; it never turns into approval or permission to skip review.
+
+## Finding priority
+
+P0-P3 are this process's review-impact convention. Assess the consequences if the
+finding remains unresolved in a supported scenario. Consumer scheduling and incident
+response deadlines remain consumer-owned.
+
+| Priority | Impact | Illustrative example |
+| --- | --- | --- |
+| P0 - critical | Catastrophic loss of essential operation, authoritative data, or a critical security guarantee. | Irrecoverable loss of the only authoritative dataset. |
+| P1 - high | Severe failure of a core workflow or guarantee, below P0's catastrophic consequences. | A primary workflow produces wrong results that can be regenerated from intact inputs. |
+| P2 - medium | Material but contained incorrect behavior or operational or maintenance cost; core workflows remain usable. | A recoverable failure in a secondary workflow with a safe alternative. |
+| P3 - low | Minor inconvenience or clarity or consistency defect with little effect on behavior or reliability. | An unclear optional explanation when all required steps remain unambiguous. |
+
+Choose the highest level whose consequences the evidence supports. Explain affected
+guarantees, reach, preconditions, recoverability, and safe alternatives. Examples are
+illustrative, not an exhaustive classifier; file type, finding category, keywords,
+and ease of repair do not determine priority.
+
+Severity follows whether the reviewed snapshot violates the accepted contract or an
+applicable production invariant; priority is not a waiver. A P2 or P3 finding can
+therefore be blocking. The existing P0/P1 restriction on a new `critical-late` blocker
+is an eligibility condition, not permission to block without the required bounded
+late rationale. Preserve carried finding priorities and historical reports under the
+existing correction-cycle rules.

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

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "engineering-process"
-version = "1.2.3"
+version = "1.2.4"
 description = "A small agent-neutral engineering lifecycle with managed adoption"
 readme = "README.md"
 license = "MIT"

{engineering_process-1.2.3 → engineering_process-1.2.4}/tests/test_lifecycle.py

@@ -793,6 +793,34 @@ class LifecycleTests(unittest.TestCase):
                     (self.root / ".process" / "runs" / "sample-change").exists()
                 )
 
+    def test_live_producer_policy_requires_its_accepted_issue(self) -> None:
+        project = json.loads((PROCESS_ROOT / ".process" / "project.json").read_text())
+        self.project["lifecycle"]["processChanges"] = project["lifecycle"]["processChanges"]
+        self.contract["consumerEvidence"] = [
+            {"repository": "engineering-process", "incident": "Deferred issue handoff enablement."}
+        ]
+        for source in (
+            "issue-110",
+            "https://github.com/other/process/issues/110",
+            "https://github.com/phuongnse/engineering-process/pull/118",
+        ):
+            with self.subTest(source=source):
+                self.contract["source"] = source
+                write_json(self.contract_path, self.contract)
+                with self.assertRaisesRegex(ProcessError, "numbered issue"):
+                    start_change(
+                        self.root, PROCESS_ROOT, self.project, self.contract_path,
+                        actor_id="author", context_id="author-context", kind="agent",
+                    )
+                self.assertFalse((self.root / ".process" / "runs").exists())
+        self.contract["source"] = "https://github.com/phuongnse/engineering-process/issues/110"
+        write_json(self.contract_path, self.contract)
+        state = start_change(
+            self.root, PROCESS_ROOT, self.project, self.contract_path,
+            actor_id="author", context_id="author-context", kind="agent",
+        )
+        self.assertEqual("specified", state["phase"])
+
     def test_evidence_only_process_change_policy_remains_compatible(self) -> None:
         self.project["lifecycle"]["processChanges"] = {
             "requireConsumerEvidence": True