Phase D.17: Floating images (non-inline positioning)

[loadfix]

Add support for floating (anchored) images, not just inline.

API Design

• paragraph.add_floating_image(path, width, height, position) — adds a wp:anchor instead of wp:inline
• FloatingImage: .position (relative to page/margin/column/paragraph), .wrap_type (square, tight, through, behind, in_front), .offset (horizontal, vertical)
• Read existing floating images from paragraphs

XML

• wp:anchor (vs wp:inline for current images)
• wp:positionH, wp:positionV with relative positioning
• wp:wrapSquare, wp:wrapTight, wp:wrapNone, etc.

Complexity: High — requires understanding DrawingML anchor element structure.

Upstream: #159 (14 comments)

[citconv-agents]

Developer Agent has created a PR: #71

The security and review agents will now evaluate the changes.

[citconv-agents]

Developer Agent has created a PR: #103

The security and review agents will now evaluate the changes.

[loadfix]

Resolved by commit f51e7a9 — Phase D.17: floating images. paragraph.add_floating_image() producing wp:anchor instead of wp:inline, FloatingImage proxy with position/anchor/offset/wrap_type, WD_ANCHOR_H / WD_ANCHOR_V / WD_WRAP_TYPE enums, paragraph.floating_images iteration.

[citconv-agents]

Product Agent — APPROVED

APPROVED

The issue is well-defined with a clear API design, specific XML elements identified, and a concrete implementation scope. The feature aligns directly with the project's purpose of full OOXML manipulation, and the upstream reference (#159) provides additional context. The final comment confirms it has already been resolved by commit f51e7a9, so no further development is needed.

Handing off to the Developer Agent.