fix(traceability): align optional and status table contracts

[kreneskyp]

Summary

• declare Coverage Status for the functional-coverage table while retaining Status for test summaries
• mark suite and inspection targets optional, matching the existing adoption contract
• strengthen tests so both declarations are explicit and current Quire stays silent for a non-adopting repository

Verification

• composed against quire-rs#383 and spec-artifacts-iso#32/Declare the Task track property (FR-005) #33: 89 passed, 1 expected xfail
• ruff passed; every Python file passed black --check (the aggregate black invocation stalled in this environment, so files were checked individually)
• Engineering Assurance composed coverage: 45/46 backed; no status lies, undeclared statuses, unbacked references, status-column diagnostics, or optional evidence-target diagnostics

Dependencies

• fix(coverage): honor per-reference and optional targets quire-rs#383
• feat(schema): admit current trace-target selectors and postures spec-artifacts-iso#32
• feat(schema): support per-reference status columns spec-artifacts-iso#33

Keep draft until those dependencies merge and released pins are updated.

[kreneskyp]

Closing: superseded by #87, which collapses Coverage Status and Status into a single Status column in the contract.

These two names had byte-identical vocabularies and were used inconsistently across sibling tables — Functional Requirement Coverage took Coverage Status, Non-Functional Requirement Coverage took Status. There was no distinction to preserve, so a per-declaration status_column override would have made the duplicate naming permanent and supported rather than fixing it.

It also would not have worked yet: it needs quire-rs#410, and no released engine carries it. Published quire 0.32.0's changelog claims the pin advanced to 616a7e97, but the v0.32.0 tag pins a874fb64, which predates that commit — which is why this work sat in draft.

#87 needs no engine change; its suite passes on released quire 0.32.0. Merged to the cohort as 375fc2a.

Thanks for the diagnosis in these branches — the status-column-matches-nothing finding is what made the root cause visible.