test: [expected failures] base fixtures needing implementation fixes

conformance-tests/2023-09/base/job_templates/proposed/2--type-lowercase.invalid.yaml

@@ -0,0 +1,15 @@
+# Parameter type names are case-sensitive in base (case-insensitivity is EXPR-only); 'string' must be rejected.
+specificationVersion: jobtemplate-2023-09
+name: TestJob
+parameterDefinitions:
+- name: MyParam
+  type: string
+steps:
+- name: Step1
+  script:
+    actions:
+      onRun:
+        command: python
+        args:
+        - "-c"
+        - "print()"

conformance-tests/2023-09/base/job_templates/proposed/2.3--int-allowedvalues-above-int64-max.invalid.yaml

@@ -0,0 +1,17 @@
+# An INT parameter allowedValues entry of 2^63 exceeds the signed 64-bit integer range and must be rejected.
+specificationVersion: jobtemplate-2023-09
+name: TestJob
+parameterDefinitions:
+- name: MyParam
+  type: INT
+  allowedValues:
+  - 9223372036854775808
+steps:
+- name: Step1
+  script:
+    actions:
+      onRun:
+        command: python
+        args:
+        - "-c"
+        - "print('{{Param.MyParam}}')"

conformance-tests/2023-09/base/job_templates/proposed/2.3--int-default-above-int64-max.invalid.yaml

@@ -0,0 +1,16 @@
+# An INT parameter default of 2^63 exceeds the signed 64-bit integer range and must be rejected.
+specificationVersion: jobtemplate-2023-09
+name: TestJob
+parameterDefinitions:
+- name: MyParam
+  type: INT
+  default: 9223372036854775808
+steps:
+- name: Step1
+  script:
+    actions:
+      onRun:
+        command: python
+        args:
+        - "-c"
+        - "print('{{Param.MyParam}}')"

conformance-tests/2023-09/base/job_templates/proposed/2.3--int-default-below-int64-min.invalid.yaml

@@ -0,0 +1,16 @@
+# An INT parameter default of -2^63-1 is below the signed 64-bit integer range and must be rejected.
+specificationVersion: jobtemplate-2023-09
+name: TestJob
+parameterDefinitions:
+- name: MyParam
+  type: INT
+  default: -9223372036854775809
+steps:
+- name: Step1
+  script:
+    actions:
+      onRun:
+        command: python
+        args:
+        - "-c"
+        - "print('{{Param.MyParam}}')"

conformance-tests/2023-09/base/job_templates/proposed/2.3--int-maxvalue-above-int64-max.invalid.yaml

@@ -0,0 +1,16 @@
+# An INT parameter maxValue of 2^63 exceeds the signed 64-bit integer range and must be rejected.
+specificationVersion: jobtemplate-2023-09
+name: TestJob
+parameterDefinitions:
+- name: MyParam
+  type: INT
+  maxValue: 9223372036854775808
+steps:
+- name: Step1
+  script:
+    actions:
+      onRun:
+        command: python
+        args:
+        - "-c"
+        - "print('{{Param.MyParam}}')"

conformance-tests/2023-09/base/job_templates/proposed/2.3--int-minvalue-above-int64-max.invalid.yaml

@@ -0,0 +1,16 @@
+# An INT parameter minValue of 2^63 exceeds the signed 64-bit integer range and must be rejected.
+specificationVersion: jobtemplate-2023-09
+name: TestJob
+parameterDefinitions:
+- name: MyParam
+  type: INT
+  minValue: 9223372036854775808
+steps:
+- name: Step1
+  script:
+    actions:
+      onRun:
+        command: python
+        args:
+        - "-c"
+        - "print('{{Param.MyParam}}')"

conformance-tests/2023-09/base/job_templates/proposed/README.md

@@ -0,0 +1,57 @@
+# Proposed conformance fixtures (expected failures) — base/job_templates
+
+Every fixture in this directory is parked because it **fails against at least
+one current reference implementation**. Placement is kind-level
+(`<component>/<kind>/proposed/`) so promotion is a mechanical move up one
+directory once the underlying issue is resolved. The conformance runner does
+not scan `proposed/` directories.
+
+Verification environment: `openjd` CLI = openjd-rs release build from
+upstream/main (post range-cap fix); cross-checks with openjd-model-for-python
+0.11.x via `decode_job_template`.
+
+## INT 64-bit boundary rejects
+
+Spec §2.3 types these fields as `<integer>` with **no stated bound** — the
+base 2023-09 document never mentions 64-bit anywhere; the int64 range exists
+only in the Expression Language type table (an EXPR document). Both reference
+implementations nonetheless *store* INT as a signed 64-bit integer, so
+accepted values outside [-2^63, 2^63-1] cannot round-trip and silently
+corrupt.
+
+| Fixture | Construct | Observed |
+|---|---|---|
+| `2.3--int-default-above-int64-max.invalid.yaml` | `default: 9223372036854775808` (2^63) | accepted by **both** (openjd-rs and python) |
+| `2.3--int-minvalue-above-int64-max.invalid.yaml` | `minValue: 9223372036854775808` | accepted by both |
+| `2.3--int-maxvalue-above-int64-max.invalid.yaml` | `maxValue: 9223372036854775808` | accepted by both |
+| `2.3--int-allowedvalues-above-int64-max.invalid.yaml` | `allowedValues: [9223372036854775808]` | accepted by both |
+| `2.3--int-default-below-int64-min.invalid.yaml` | `default: -9223372036854775809` (-2^63-1) | accepted by both |
+
+Classification: **spec question first, then implementation fix** — because the
+base spec states no integer bound, a bignum implementation accepting these is
+arguably conformant as the text stands. Promotion is gated on a base-spec
+integer-bounds erratum (pin `<integer>` to int64 in §2.3); once that lands,
+these become straightforward validation-bug pins, one branch per field. The
+matching accept-twins at 2^63-1 and -2^63 are added by the base-gaps PR
+(`job_templates/2.3--int-*-int64-max.yaml` etc.).
+
+Related, different axis: the *supplied value* case lives in
+`../../jobs/proposed/2.3--int-value-above-int64-max.invalid.test.yaml` — that
+one is **Python-only** (openjd-rs rejects a supplied 2^63 at job creation;
+openjd-model 0.11.x `create_job` accepts it).
+
+## Type-name case sensitivity
+
+| Fixture | Construct | Observed |
+|---|---|---|
+| `2--type-lowercase.invalid.yaml` | `type: string` in base (no `extensions:`) | openjd-rs: **accepted**; python: rejected ("Input tag 'string' ... does not match any of the expected tags") |
+
+Spec §2: `type: "STRING"` is a literal, and the spec states type names become
+case-insensitive only "When the `EXPR` extension is enabled" (see RFC 0007).
+Base is case-sensitive.
+
+Classification: **openjd-rs implementation bug** (unconditional
+case-insensitive type parsing); python is spec-conformant. Note: the
+param-types expected-failures PR previously carried an identical pin
+(`2--type-lowercase-string.invalid.yaml`); it was dropped in favor of this
+one — this fixture is the single copy.

conformance-tests/2023-09/base/jobs/proposed/1.2.1--constraint-widening-int-range.invalid.test.yaml

@@ -0,0 +1,32 @@
+# Spec 1.2.1: each constraint must become MORE constrained in template processing order.
+# The job template (processed last) widens the environment template's INT range, so the
+# merge must be rejected. The default satisfies both ranges, isolating the widening rule.
+template:
+  specificationVersion: jobtemplate-2023-09
+  name: TestJob
+  parameterDefinitions:
+  - name: Count
+    type: INT
+    minValue: 0
+    maxValue: 1000
+    default: 50
+  steps:
+  - name: Step1
+    script:
+      actions:
+        onRun:
+          command: python
+          args:
+          - -c
+          - print(r'Count={{Param.Count}}')
+environments:
+- specificationVersion: environment-2023-09
+  parameterDefinitions:
+  - name: Count
+    type: INT
+    minValue: 10
+    maxValue: 100
+  environment:
+    name: TestEnv
+    variables:
+      COUNT: '{{Param.Count}}'

conformance-tests/2023-09/base/jobs/proposed/1.2.1--constraint-widening-minlength.invalid.test.yaml

@@ -0,0 +1,30 @@
+# Spec 1.2.1: each constraint must become MORE constrained in template processing order.
+# The job template (processed last) relaxes the environment template's minLength, so the
+# merge must be rejected. The default satisfies both, isolating the widening rule.
+template:
+  specificationVersion: jobtemplate-2023-09
+  name: TestJob
+  parameterDefinitions:
+  - name: Value
+    type: STRING
+    minLength: 2
+    default: test-value
+  steps:
+  - name: Step1
+    script:
+      actions:
+        onRun:
+          command: python
+          args:
+          - -c
+          - print(r'Value={{Param.Value}}')
+environments:
+- specificationVersion: environment-2023-09
+  parameterDefinitions:
+  - name: Value
+    type: STRING
+    minLength: 5
+  environment:
+    name: TestEnv
+    variables:
+      VAL: '{{Param.Value}}'

conformance-tests/2023-09/base/jobs/proposed/2.3--int-value-above-int64-max.invalid.test.yaml

@@ -0,0 +1,18 @@
+# A supplied INT parameter value of 2^63 exceeds the signed 64-bit integer range and must be rejected at job creation.
+template:
+  specificationVersion: jobtemplate-2023-09
+  name: TestJob
+  parameterDefinitions:
+  - name: MyParam
+    type: INT
+  steps:
+  - name: Step1
+    script:
+      actions:
+        onRun:
+          command: python
+          args:
+          - -c
+          - print(r'OUTPUT:{{Param.MyParam}}')
+parameters:
+  MyParam: 9223372036854775808

conformance-tests/2023-09/base/jobs/proposed/README.md

@@ -0,0 +1,46 @@
+# Proposed conformance fixtures (expected failures) — base/jobs
+
+Every fixture in this directory is parked because it **fails against at least
+one current reference implementation**. Placement is kind-level
+(`<component>/<kind>/proposed/`) so promotion is a mechanical move up one
+directory. The conformance runner does not scan `proposed/` directories.
+
+## Merge widening (§1.2.1)
+
+Spec §1.2.1: "each constraint must become more constrained as a subsequent
+definition is merged with the previous ones in processing order" (Job
+Template last). These fixtures have a Job Template that *widens* the
+Environment Template's constraint while the default satisfies both ranges,
+isolating the direction rule from the merged-consistency rule.
+
+| Fixture | Construct | Observed |
+|---|---|---|
+| `1.2.1--constraint-widening-int-range.invalid.test.yaml` | env `[10,100]`, job template `[0,1000]` | accepted by both; job runs |
+| `1.2.1--constraint-widening-minlength.invalid.test.yaml` | env `minLength: 5`, job template `minLength: 2` | accepted by both; job runs |
+
+Cross-check: `openjd.model.merge_job_parameter_definitions` returns the
+*intersection* (`minValue=10, maxValue=100`) rather than rejecting — both
+implementations merge by intersection and never enforce the narrowing
+direction.
+
+Classification: **spec decision needed, then (possibly) implementation fix**.
+The stated sentence supports rejection on a literal reading, but both
+implementations implement intersection semantics, and enforcing
+reject-on-widening is a behavioral change for any scheduler that merges
+externally-supplied environment parameter definitions into customer templates
+(e.g. queue environments). Until the spec either affirms the narrowing rule
+or is revised to define intersection semantics, these stay parked.
+
+## INT 64-bit supplied value (Python-only)
+
+| Fixture | Construct | Observed |
+|---|---|---|
+| `2.3--int-value-above-int64-max.invalid.test.yaml` | supplied INT parameter value `9223372036854775808` (2^63) | openjd-rs: **rejects at job creation (fixture passes)**; python (openjd-model 0.11.x `create_job`): **accepts** |
+
+Moved here from the base-gaps PR's live `jobs/` directory: the base spec
+states no int64 bound on `<integer>` (see the job_templates/proposed README),
+and the reference Python implementation accepts the value, so as a live
+fixture it failed the reference implementation. Same promotion gate as the
+template-side int64 family: a base-spec integer-bounds erratum, plus the
+openjd-model fix. Its accept twin (`jobs/2.3--int-value-int64-max.test.yaml`,
+supplied 2^63-1 resolves exactly) is in the base-gaps PR and passes both.