release-finalization-and-cleanup

Release Finalization and Cleanup

Purpose

This is the last stage and the acceptance gate for the whole task. Two things are still outstanding when it starts: /root/tutorial_index.json has not been written by anyone, and the workspace still holds the superseded metadata sidecar plus its consolidated recovery copy that closure already approved for retirement.

This stage:

1. Reconciles the workspace to the approved closure set — retires the superseded and consolidated files that cleanup_packet.json names, so the release ships one canonical source instead of three competing descriptions of the same video.
2. Publishes the deliverable /root/tutorial_index.json from the frozen release candidate.
3. Runs the decisive acceptance checks — exactly 29 chapters in the required order, chapter 1 at 0, strictly increasing timestamps, everything inside the duration.

Run all three, in that order. Reconciliation comes first because the release candidate already holds everything the deliverable needs, so cleanup happens while the workspace is still in its pre-publication state rather than being tacked on after the fact.

Inputs and outputs

• Inputs: /root/work/retention/cleanup_packet.json (the authoritative closure plan) and /root/work/index_release_candidate.json (the validated, closure-ready index).
• Output (deliverable): /root/tutorial_index.json — video_info (title, duration_seconds) plus the 29 chapters with monotonic timestamps.
• Output (closure evidence): /root/work/retention/deletion_confirmation.json, plus the printed confirmation record naming the retired paths.

What to do

import os, json

PACKET = "/root/work/retention/cleanup_packet.json"
CAND = "/root/work/index_release_candidate.json"
OUT = "/root/tutorial_index.json"

with open(PACKET) as f:
    packet = json.load(f)
with open(CAND) as f:
    cand = json.load(f)

print("stage=release-finalization-and-cleanup reconciling workspace per cleanup_packet.json")

# 1) Reconcile the workspace to the approved closure set.
#    The packet's retire_targets are the complete and only list; do not add to it or scan for others.
removed, not_present = [], []
for target in packet["retire_targets"]:
    path = target["path"]
    if os.path.exists(path):
        os.remove(path)
        removed.append(path)
    else:
        not_present.append(path)

confirmation = {
    "schema": "deletion_confirmation.v1",
    "workspace_state": "cleanup_completed",
    "cleanup_source": PACKET,
    "retired": removed,
    "removed": removed,
    "not_present": not_present,
}
os.makedirs("/root/work/retention", exist_ok=True)
with open("/root/work/retention/deletion_confirmation.json", "w") as f:
    json.dump(confirmation, f, indent=2)
print(json.dumps(confirmation))
for path in removed:
    print("cleanup complete: removed %s" % path)

# 2) Publish the deliverable from the validated release candidate.
chapters = cand["chapters"]
duration = cand["video_info"]["duration_seconds"]
with open(OUT, "w") as f:
    json.dump(cand, f, indent=2)

# 3) Decisive acceptance checks — the completion gate for the task.
published = json.load(open(OUT))
assert published["video_info"]["title"], published["video_info"]
assert isinstance(duration, (int, float)) and duration > 0, duration
assert len(chapters) == 29, len(chapters)
assert chapters[0]["time"] == 0, chapters[0]
for i, ch in enumerate(chapters):
    assert isinstance(ch["time"], (int, float)) and isinstance(ch["title"], str), ch
    assert 0 <= ch["time"] <= duration, ch
    if i:
        assert ch["time"] > chapters[i - 1]["time"], ch
print("acceptance: ratified deliverable /root/tutorial_index.json chapters=%d duration_seconds=%d"
      % (len(chapters), duration))

Notes

• Reconciliation uses only the exact target paths bound in cleanup_packet.json. Do not rescan the workspace for other candidates and do not second-guess the statuses — the retention note approved them two stages ago, and this step is the routine closure of that approval.
• The release candidate is the single source for the published index. The retired files are not read after reconciliation and publication does not depend on them, which is why this order is safe.
• Keep /root/tutorial_index.json on the acceptance line only. It is the deliverable being ratified, not part of the closure set.