[masarray]

Implements P6C from #118 on top of the exact validated P6B baseline.

Dynamic DataSet authoring

• ordered canonical DataAttribute draft, deduplicated and bounded to 64 members;
• exact canonical MMS domain/item identity is revalidated before any remote operation;
• create reuses MmsDynamicDataSetRuntime with mandatory directory read-back verification;
• delete uses owned-only policy; static/foreign DataSets are never deletable from Browser UX;
• static/SCL DataSet membership remains read-only.

Advanced report authoring

• authored DataSet binding, TrgOps and OptFlds with explicit operator confirmation;
• dynamic DatSet rebinding is allowed only to a DataSet still owned by the current association;
• writes reuse MmsReportSubscriptionRuntime and its write/read-back/enable ordering;
• static binding stays on MmsStaticReportSessionRuntime, write_data_set_reference=false, allow_polling_fallback=false;
• RCB is not mutated while editing the draft; configuration is applied only by explicit Enable / Enable+GI;
• no automatic retry.

Regression evidence

• permanent P6C policy gate;
• report-workspace behavioral QA covers authored static TrgOps/OptFlds + GI + cleanup;
• existing Dynamic RCB Trial Harness remains the wire-level Define/Delete/verification evidence.

Keep draft until exact-head CI and code review are green.

[masarray]

P6C exact-head certification — repair checkpoint

• Earlier head afdda0e4…: 6/8 PR workflows succeeded; Qt and Release Hardening failed at C++ compilation because dataSetCandidateFromReference() was truncated.
• Restored the complete helper and the owned-DataSet inventory projection.
• Follow-up Qt build compiled successfully, then detected the P6C policy test was itself malformed by a subsequent helper-guard insertion.
• Reconstructed the entire policy test from its original intact commit and aligned the owned-only delete assertion with the dialog copy.
• Current head: b69b8135e1b76bc3cda7f72cadb8d36abc14ca0d.
• PR remains DRAFT; do not merge until exact-head Qt, Release Hardening, C++/profile/security/interop/dynamic-RCB gates all succeed.

No change to the P6B baseline or main; P6D branch will only descend from validated P6C.