# CMIS OpenCMIS TCK Evidence - Release Readiness - 2026-05-13T22:35:37Z

## Run Summary

- Run ID: `run-20260513T223537Z`
- Local date: 2026-05-14 Europe/Berlin
- Harness: `guide-board` with `open-cmis-tck` extension
- Assessment: `cmis-browser-baseline`
- Target: `kontextual-cmis-compat`
- Endpoint: `http://127.0.0.1:8010/cmis/compat-tck/browser`
- OpenCMIS TCK: CMIS 1.1.0, revision `1789681`
- Result: `completed`
- Policy: `0` unexpected findings, `0` applied waivers
- Run directory: `/tmp/kontextual-cmis-release-20260514-toolchain`
- Internal verification: `.venv/bin/python -m pytest -q` -> `166 passed`,
  `14 skipped`

This run was executed after adding Browser Binding `appendContent` /
`appendContentStream` support through the existing content representation
service.

## Normalized Results

| Group | Result | Counts | Remaining non-green findings |
| --- | --- | --- | --- |
| `repository-type` | `warning` | `38 pass`, `2 info`, `1 skipped`, `1 warning` | Local loopback endpoint uses HTTP rather than HTTPS. |
| `object-content` | `pass` | `10 info`, `5 skipped` | None. |

Guide Board summary:

- `pass`: 2
- `warning`: 1

## Score

This is a compatibility-infrastructure score for the selected Browser Binding
baseline, not a CMIS certification score.

| Metric | Score | Basis |
| --- | ---: | --- |
| Selected baseline completion | 100.0% | Guide Board result `completed`; both selected groups returned `0`. |
| Unexpected finding clearance | 100.0% | `0` unexpected findings, `0` fail, `0` infrastructure_error. |
| Warning-adjusted normalized case score | 99.1% | `(56 accepted + 0.5 * 1 warning) / 57 normalized cases`. |
| Strict no-warning normalized case score | 98.2% | `56 accepted / 57 normalized cases`. |

Digest versus `run-20260513T210255Z`:

- OpenCMIS selected-baseline infrastructure score improved from `98.3%` to
  `99.1%`.
- `object-content` improved from warning to pass.
- The previous `appendContentStream()` warning is closed.
- The only remaining warning is local HTTP transport in the loopback harness.

## Interpretation

The selected Browser Binding repository/type and object/content baseline is now
release-ready for a controlled preview. The remaining HTTP warning should be
handled as a deployment gate: released access points need HTTPS termination,
while loopback TCK runs may keep the warning as an accepted local harness
condition.

Skipped object/content cases remain aligned with declared capability
boundaries:

- Relationship, policy, and item creation are not advertised as creatable.
- Folder-name change-token subcases are skipped by the TCK.

This evidence still does not cover full CMIS 1.1 certification, AtomPub, Web
Services, PWC/checkin/checkout, full CMIS SQL, renditions, retention, or policy
mutation depth.