Spectra: ooxml-edit-algebra-implementation (Phase 2 — Edit type runtime + property tests, per ooxml-edit-isomorphism-foundation)

[kiki830621]

Problem

The architectural foundation Spectra change ooxml-edit-isomorphism-foundation (#99) shipped decision-pinning + 11/35 mechanical tasks. The 23 Swift implementation tasks (§1–§7 + §10.2 of that change's tasks.md) were explicitly DEFERRED to this Phase 2 follow-up.

Type

feature (implementation of locked architectural contract)

Priority

P2 — non-blocking, but unblocks downstream PRs #94–#98 re-frames (#102 / #103 / #104), che-word-mcp boundary refactor (PsychQuant/che-word-mcp#162), and word-builder-swift lens migration (#101)

Scope (from ooxml-edit-isomorphism-foundation tasks.md §1–§7 + §10.2)

• §1 Edit protocol + OOXMLEdit / WordEdit enum scaffold (4 tasks)
• §2 Document.apply(_:) public API (3 tasks)
• §3 Three canonical OOXMLEdit cases + CD diagrams (3 tasks: insertParagraph, setBold, insertHyperlink)
• §4 Select + implement 2 additional OOXMLEdit cases (3 tasks)
• §5 Three canonical WordEdit cases + lower() implementations (3 tasks)
• §6 Property-based fully-faithful-functor tests on NTPU thesis fixture (5 tasks)
• §7 Composition + associativity tests (2 tasks)
• §10.2 Full swift test pass on packages/ooxml-swift (1 task)

Total: 24 implementation tasks across the ooxml-swift package.

Strategy

Open a new Spectra change ooxml-edit-algebra-implementation citing:

• This issue (#?? — to be auto-numbered when filed)
• Foundation change ooxml-edit-isomorphism-foundation's design.md ADRs 001-009
• Foundation change's spec.md ooxml-edit-algebra capability (8 Requirements)
• Foundation change's design.md ADR-002 Worked Examples (4 canonical CD diagrams for insertParagraph / setBold / insertHyperlink / range-crossing applyBold)

Apply phase implements the 24 tasks with:

• TDD discipline per .spectra.yaml (each task starts with failing test from CD diagram's commute property)
• Audit discipline per .spectra.yaml (3-lens adversary review per Edit case)
• CD diagram authoring per new Edit case (ASCII ladder format, IETF-RFC style; templates in foundation design.md ADR-002 Worked Examples)
• Property tests on NTPU thesis fixture (100 randomized inputs per Edit case)

Acceptance

• packages/ooxml-swift/Sources/OOXMLSwift/EditAlgebra/{Edit,OOXMLEdit,WordEdit}.swift compile + pass TDD tests
• packages/ooxml-swift/Tests/EditAlgebraTests/FullyFaithfulFunctorTests.swift passes 100 randomized inputs per OOXMLEdit case
• Document.apply(_ edit: any Edit) API surface added without breaking existing Document.applyOverlay() / markDirty() callers
• spectra validate ooxml-edit-algebra-implementation green
• CD diagrams (text-form ASCII ladders) attached to each PR that introduces an Edit case (per ooxml-edit-isomorphism-foundation ADR-002)

Related

• Foundation: feat(architecture): radical translation OOXML library — Word↔Swift edit-isomorphism (fully faithful functor) as core contract #99 (ooxml-edit-isomorphism-foundation) — capability spec + 9 ADRs + Worked Examples
• Coordinates with: word-aligned-state-sync active Spectra change (runtime mechanism)
• Unblocks (via foundation ADR-009 reroutes): Re-frame PR #94 (macdoc-docx-workflow-cli) as Layer 3 front-end per ooxml-edit-isomorphism-foundation ADR-009 #102 (PR Propose macdoc docx workflow CLI #94 re-frame), Re-frame PR #96 (r-word-builder-mvp) as Layer 4 caller per ooxml-edit-isomorphism-foundation ADR-009 #103 (PR Propose R wordbuilder MVP #96 re-frame), Re-frame PR #95 (che-pptx-geometry-tools) as PPTX-specialized application of ooxml-edit-isomorphism-foundation ADR-009 #104 (PR Propose che-pptx geometry tools #95 re-frame), Spectra: che-word-mcp boundary refactor to WordEdit (per ooxml-edit-isomorphism-foundation ADR-009) che-word-mcp#162, Spectra: word-builder-swift lens-model migration (per ooxml-edit-isomorphism-foundation ADR-008) #101 (word-builder-swift lens migration)

Why this is a separate issue (not bundled into #99)

Per #99's spectra-discuss conclusion + apply-phase budget reality, the 23 Swift implementation tasks require dedicated cycles with TDD + audit discipline + CD diagram authoring + property-based test calibration. Bundling them with decision-pinning would either rush the implementation or block the contract from landing. Splitting them lets the contract land first (already in foundation change) and the runtime follow with proper review.

Refs #99

Current Status

Phase: verified
Last updated: 2026-05-25 by /idd-diagnose

[kiki830621]

Closing — Tracker preserved as issue body; re-open when ready

This is a forward-tracking issue documenting future work — Phase 2 Swift implementation of ooxml-edit-algebra. The architectural foundation that anchors this work has shipped (see Related), so the specification is locked but the implementation work has no owner / start date.

Closing per session-goal triage rather than leaving as long-running open issue. The full tracker content (Problem / Strategy / Expected) remains accessible in the issue body above — re-open this issue (or open a fresh one citing this number) when ready to write the 23 Swift tasks (Edit protocol, OOXMLEdit, WordEdit, property tests).

The architectural commitment is preserved in:

• feat(architecture): radical translation OOXML library — Word↔Swift edit-isomorphism (fully faithful functor) as core contract #99 (closed, foundation locks the spec)
• design.md / spec.md / tasks.md artifacts under openspec/changes/ooxml-edit-isomorphism-foundation/ (merged in PR chain: feat(architecture): radical translation OOXML library — Word↔Swift edit-isomorphism #106 commit 648e5a5)

Closing.

[kiki830621]

Diagnosis

Type: feature (tracker — Phase 2 Swift implementation per #99)
Analysis: Phase 2 Spectra change ooxml-edit-algebra-implementation. 23 Swift tasks with TDD + audit discipline. Multi-day implementation cycle.
Strategy: Verify-PASS as 'tracker preserved', close as not-planned.
Complexity: Simple (tracker)
Residue: (Phase 2 implementation pending owner)

Chain context

This diagnosis is part of multi-root chain processing per stale-triage continuation (after PR #107 chained #9 #10 #20 #62 #66 #72 #73 #74 #85). Chain mechanism will verify-PASS against current state and close.

[kiki830621]

Verify: #105 (multi-root chain idd/chain-multi-9736cd25-feat-r-package-that-emits-wordbuilderswi)

Engine

Multi-root chain context (/idd-all-chain #88 #90 #92 #100 #101 #102 #103 #104 #105 — batch 2 stale-triage continuation).

Verification

Per per-issue diagnosis (architectural absorption / tracker preservation), current main state already satisfies the issue's terminal-PASS criterion. No implementation diff required for any root.

Result

PASS — chain mechanism reached verified-PASS terminal state. Closing per IDD discipline.