Moving an asset is only half of a folder reorganization. The manuscript must point to the new location, the old path must disappear, and the new target must exist. This text editor folder hierarchy image link paths procedure follows one image and one ordinary link through separate moves. The retained STUDIO-357 artifact includes the final Markdown, command log, new files, and a digest-backed readback.
Number the Two References Before Moving Anything
The starting chapters/chapter.md referred to the image ../assets/figure.png and the text file ../assets/note.txt. Run reference usage for each target and record the source line. Keep image syntax and ordinary link syntax on separate rows; a total of two references cannot reveal whether both rows belong to the same kind.
Record each asset digest, the starting manuscript digest, and the relative path. Moving the file first creates a temporary broken-reference state. That state is understandable during an uninterrupted operation, but it must be marked clearly if the work pauses. Otherwise another editor may treat an incomplete move as an accepted hierarchy.
Move the Image and Rewrite One Occurrence
The image was moved to moved/renamed-figure.png. A reference plan then identified one occurrence in chapter.md. Only after that path and count matched the inventory was the rewrite applied. The response recorded rewrittenFiles=1 and occurrenceCount=1.
The saved Markdown now contains ../moved/renamed-figure.png. Do not rely on a picture that remains visible in a preview; a cache can display the old asset after the source path is broken. Read the stored string and confirm that the new file exists as separate checks.
Move the Text Link in Its Own Trial
Next, move note.txt to moved/renamed-note.txt. Rebuild the reference plan instead of reusing the image result. The plan should identify one ordinary link in chapter.md. After the rewrite, the stored line points to ../moved/renamed-note.txt.
Separating the trials reveals a rule that updates image syntax but ignores ordinary links, or vice versa. A combined report that says “two changes” could describe two image occurrences while leaving the link broken. Each row therefore carries its own source kind, old path, new path, planned count, and applied count.
Reopen the Saved Eighty-Three-Character File
The final manuscript has SHA-256 8a0974544a66517c231a351427b346484ff24dd74cf50de252065000fcf61863. A UTF-8/LF readback returned characterCount=83 and lineCount=4. The content consists of a heading, the rewritten image line, and the rewritten link line.
Searching for the old prefix ../assets/ returned zero matches. Both new targets existed, producing new_targets_exist=true. The zero result alone is not sufficient because deleting a path would also make the old prefix disappear. Acceptance combines the two new stored paths with two existing target files.
Preserve a One-Sided Failure
One useful failure moves the image file but leaves the old manuscript reference. The new file exists, yet old-path search still returns one. Another failure changes the Markdown before the file move succeeds; the new reference then points to nothing. Keep these states under separate names so the diagnostic difference remains visible.
Recovery starts with reference usage against the failed copy, confirms a one-occurrence plan, applies the rewrite, and saves to a new path. Then test old-prefix count, both new-path strings, and both targets. Do not accept the repair until the old count is zero, the new references are present, and the files exist.
Recalculate Paths When the Manuscript Also Moves
If the destination is nested another level down, the number of parent segments may change. Calculate the relative path from the manuscript's own directory. Do not paste an operating-system absolute path into publishable Markdown. When both the manuscript and assets move, perform them as separate trials and resolve references after each move.
Names containing spaces or non-ASCII characters add Markdown escaping and URL-encoding questions. This ASCII specimen does not establish those display rules. Build a dedicated sample for each new character class and repeat the stored-string and target-existence checks.
Score Rendering and Clicking Separately
The command evidence verifies rewritten paths, disk persistence, old-prefix search, and target existence. It does not record a named graphical preview rendering the image or a click opening the text link. Structural reference acceptance must remain separate from interface behavior.
A later visual run should record application build, manuscript digest, visible image region, selected link, and destination file. Close and reopen the manuscript to reduce cache ambiguity. Attach that result as a new observation; do not overwrite the command receipt.
Hand Off Two Resolved Paths
The release card contains old and new paths, one planned occurrence, and one applied occurrence for both the image and the link. It also contains the final eighty-three-character, four-line manuscript digest, zero old-prefix matches, and confirmation that both targets exist.
Another operator can reopen the artifact and find ../moved/renamed-figure.png and ../moved/renamed-note.txt. When those strings resolve to the retained files without consulting the old directory, the hierarchy repair passes. Preview rendering and click behavior remain separate environment-specific tests.
Keep the destination asset digests beside the manuscript receipt. Existence alone could point to a different file that reused the same name. A passing row therefore combines rewritten relative path, target existence, and expected target digest. If any one differs, classify the reference as unresolved and repeat the move from the preserved source copy.