Introduction
The supported Harbour Loop guide needs one download-link correction. Development already contains that fix, alongside an unapproved Explorer redesign. The original main working tree still has staged photo-plan work, a further unstaged cover draft and an untracked private note.
Use the worktree technique from the first guided lab to give the existing maintenance branch a clean working directory. Read actual patches, select the one self-contained fix and replay only that change with cherry-pick. Then test the useful old-edition download and verify that neither the redesign nor your unfinished work moved into the release.
This unit initializes its own repositories and files; it does not reuse the previous VM. Prerequisites are basic terminal/commit/branch/log/diff skills plus the linked-worktree and small file concepts taught in the first guided lab. No website code or hosted account is needed. Use Workspace and Release Desk. The real Git/HTTP preview is local to one training machine and reads branch commits, not working-file edits. All routes and identities are synthetic. The 40-minute duration is an author estimate.
Identify the Fix and Open the Maintenance Worktree
In this step, see the expected download, distinguish the isolated fix from the redesign and open the existing old branch without disturbing main.
Open Release Desk, then Open supported release. Verify Harbour Loop, Pocket Edition 1.0, 3.2 km and North Pier. Use Download quick start, open quick-start.txt from the browser's Downloads list and check the original meeting point and short preparation list.
Use Download full guide. Expect the actual 404 Guide not found page, then click Back to release. The service is reachable, but this release's link points at a file it does not contain.
Use All releases, then Open development preview. Explorer Edition 2.0 is unapproved. Its Download full guide already works: open harbour-guide-v1.txt from your Downloads list and read the original three directions, North Pier start, 3.2 km distance and path/litter reminder. Keep that useful fix while leaving the redesign out. Use All releases to return.
Switch to Workspace, and explicitly enter the original working directory:
cd /home/labex/project/release-desk/editor
For ordinary path mistakes, use pwd and ls, then repeat this complete cd; do not reset the VM. Set a repository-local author identity. --local affects this repository and its linked worktrees, not global configuration. Quoted synthetic examples may be replaced:
git config --local user.name "Guide Editor"
git config --local user.email "guides@example.com"
Read the unfinished state before doing maintenance:
git branch --show-current
git status --short
git --no-pager diff --cached -- preview.txt
git --no-pager diff -- preview.txt
cat private-note.txt
As in the first lab, expect main, MM preview.txt and ?? private-note.txt. The first diff shows the staged Plan: add dusk photographs. addition. The second shows the further unstaged Draft: try the violet cover. addition. Keep their distinct contents and the private note. --cached selects the index-to-commit comparison; the plain diff compares working files to the index. --no-pager prints directly and -- separates the following path.
Read development's committed history. --oneline shortens each entry and --decorate labels the pointers and tags:
git --no-pager log --oneline --decorate dev-start
The fixed tag dev-start marks the inherited main tip. From newest to oldest, the prepared history contains Plan the Explorer photo collection, Correct the Harbour Loop download link, Introduce the Explorer redesign and Prepare the supported Harbour Loop guide. Keep the tag and main tip unchanged.
Inspect the latest change before choosing it. show displays a selected commit and its patch:
git --no-pager show dev-start
It changes explorer-plan.txt. That is unrelated future work. The fix is one parent before this fixed bookmark. ~1 selects that parent without changing your checkout:
git --no-pager show dev-start~1
Its complete patch changes only the one-line full-guide.path: /downloads/harbour-guid-v1.txt becomes /downloads/harbour-guide-v1.txt. This fix is self-contained; it does not require the redesign. Inspect that earlier redesign too. ~2 selects two parents before the fixed bookmark:
git --no-pager show dev-start~2
It changes release identity and adds Explorer plans. Merging the whole development branch would import those unapproved changes as well as the useful fix.
Open the existing supported branch beside main. .. names the parent directory, and the second argument explicitly chooses the existing branch rather than creating a new one from main:
git worktree add ../supported-v1 release/1.0
git worktree list
cd ../supported-v1
git branch --show-current
git status --short
cat release.txt
Expect the native worktree list to include both directories, branch release/1.0, a clean maintenance state and the Pocket Edition 1.0 identity. Its separate index gives cherry-pick the clean target it needs while main's draft remains in place. If you mistakenly ask to add main again, the already-checked-out refusal taught in the first lab needs no force or reset: inspect git worktree list and use the existing supported branch.
Apply the Fix and Verify the Preserved Release
In this step, replay only the selected patch onto the old release, test the real guide and confirm the original development work is intact.
Stay in Workspace, in /home/labex/project/release-desk/supported-v1. A cherry-pick takes the change introduced by a selected commit and applies it on your current branch, normally recording a new commit. It does not merge all the selected commit's ancestors. In this scene the old branch has a different parent from the source fix, so the new correction has its own commit ID.
Read the old link once, then apply the inspected isolated fix. The tag remains visible from either linked worktree because repository objects and references are shared:
cat full-guide.path
git cherry-pick dev-start~1
Expect one new commit with the download-link subject and a one-file change, without a conflict. This prepared patch changes the same small setting on the supported baseline; it has no dependency chain. Your commit ID may differ.
Review exactly what the maintenance branch gained. The fixed supported-start tag marks the inherited old tip, HEAD is this worktree's current commit, and diff compares those snapshots:
git --no-pager diff supported-start HEAD
Expect only the full-guide path correction. There should be no change to release.txt, guide content or the original preview text, and no Explorer-only file. Inspect actual history and the clean target state:
git --no-pager log --oneline --decorate
git status --short
cat release.txt
There should be one correction directly after the original supported commit. The development redesign and photo-plan commits are absent from this branch's ancestry. Exact message spelling is not the success criterion; the isolated patch, correct baseline and preserved files are.
Switch to Release Desk, click Release Desk in the header to return to the overview, then Open supported release. It must retain Pocket Edition 1.0, Harbour Loop, 3.2 km and North Pier. The local preview reads the branch commit you just advanced; no remote or production deployment is being simulated.
Click Download full guide. Open the real harbour-guide-v1.txt from your browser's Downloads list. Compare the complete content with the development download you read earlier: North Pier start; all three directions via Clock Steps, the old boathouse and Anchor Square; 3.2 km; and the final path/litter reminder. The fix delivers the original supported guide, not a new Explorer route. The download link alone or a successful status code would not prove complete content.
Use Download quick start and retain its original checklist. From All releases, open the development preview and confirm Explorer Edition 2.0 is unchanged. Return with All releases.
Switch to Workspace and re-enter main's original directory. Being in another directory changes which worktree's index your commands inspect. The -1 log option limits output to the newest commit:
cd /home/labex/project/release-desk/editor
git branch --show-current
git --no-pager log -1 --oneline --decorate
git status --short
git --no-pager diff --cached -- preview.txt
git --no-pager diff -- preview.txt
cat private-note.txt
The newest commit must still be the original photo-plan commit marked dev-start. Expect main's original MM preview.txt and ?? private-note.txt, the same staged photo-plan sentence, the separate unstaged violet-cover sentence and the unchanged private note. Do not commit or discard them just to make status clean. Leave the supported worktree available. The checkpoint checks the linked relationship, supported history and every required file together with real downloads and preservation of main.
Summary
You inspected the actual development patches, selected the isolated link correction and replayed it with cherry-pick in the clean maintenance worktree. The old release received one useful correction without inheriting the redesign.
The full guide and quick-start downloads remained complete, while development's branch tip, staged and unstaged draft versions and private note stayed intact. The independent challenge changes the supported branch, guide and fix position, so select from evidence rather than copying an offset.
