Turning a broken Hangul form into a reusable skill repair

Cross-checked the May 2026 Codex repair/test records with the installed HWPX generator and skill. The article distinguishes the original repair tests from the September 9 archive/XML check of a retained document.

In May 2026, document work required replacing content in an existing Hangul form while retaining its tables and formatting. Writing good prose was not sufficient. A generated HWPX could pass archive and XML checks while its text arrangement still behaved incorrectly in the form. Structural validity and an editable document were separate concerns.

The May 17 record traced the problem to paragraphs that enclosed tables. Collecting all descendant text from such a paragraph joined several cells into one long string. Replacing paragraphs sequentially could then mishandle content that needed to remain distributed across cells.

Codex inspected the secretary’s HWPX generator and added a filter for table-enclosing paragraphs. Only text-bearing paragraphs inside the actual cells entered the editable set. The same rule was used by replacement, paragraph rebuilding, inspection, and preview generation, so other paths would not retain the original mistake.

The OpenClaw skill was updated to prefer semantic replacement or visible fields for fixed, table-heavy forms. The secretary prepares content after inspecting the template; the generator enforces the editing boundary. The main output is a reusable editing rule, rather than the content of one document.

The same day’s record also contains a correction to the destination file. The intended target was backed up and updated, and the mistakenly changed current copy was restored. This exposed a separate operational requirement: clearly distinguish the input template, intended output, and preserved original.

Earlier work on May 10 improved preservation of ZIP members, their order, compression types, and metadata. The mimetype entry was kept first and uncompressed, and preview text was regenerated after content changes. Otherwise, an edited body could coexist with outdated preview or search text.

Existing line-layout caches were cleared so Hangul could recalculate layout. The requested character-width ratio of 95% and spacing of -5 were applied without further automatic squeezing. Those values were specific formatting choices for this workflow, not a universal recommendation for Hangul documents.

The May 17 repair record includes Python syntax checking, archive validation of a generated test file, and inspection through the new editable-paragraph logic. The test reported zero merged paragraphs above 500 characters and a longest editable paragraph of 99 characters. That supports removal of the observed table-text aggregation symptom in that test.

A retained HWPX artifact was also checked for this case study. It existed, passed ZIP and section-XML parsing checks, and included preview text plus a first, uncompressed mimetype entry. That retained artifact predates the specific repair. The new check confirms only its archive and XML condition; it is not a test of the repaired output or a visual inspection in Hangul. Evidence of the repair comes from the historical tests and installed code described above.

Repairing one output would have left the next form exposed to the same problem. Here, the cause was expressed as an editing-unit rule and applied to both implementation and instructions. Codex’s diagnosis became a rule OpenClaw could reuse when preparing another document.

The transferable sequence is to inspect the original structure, define editable fields, preserve surrounding structure, and check packaging, XML, previews, and the rendered page separately. HWPX generation must also be distinguished from binary HWP conversion. The verified output of this tool is HWPX; producing HWP requires a separate conversion step in Hangul.