From 59026d008bcf711fda929e48d891434f1fdc2e29 Mon Sep 17 00:00:00 2001 From: Torsten Wierschin Date: Wed, 11 Nov 2026 10:31:05 +0000 Subject: [PATCH] Adds clean up step --- ...release-qt6-release-2-post-copy-cleanup.md | 49 +++++++++++++++++++ 1 file changed, 49 insertions(+) create mode 100644 prompts/release-qt6-release-2-post-copy-cleanup.md diff --git a/prompts/release-qt6-release-2-post-copy-cleanup.md b/prompts/release-qt6-release-2-post-copy-cleanup.md new file mode 100644 index 000000000..f2bd662b0 --- /dev/null +++ b/prompts/release-qt6-release-2-post-copy-cleanup.md @@ -0,0 +1,49 @@ +# Prompt: Release 2 Post-Copy Scope Cleanup + +The Release 2 work described in `./prompts/release-qt6-migrated-modules-second-phase.md` has already been completed successfully. Its source tree was copied here, including files that may not belong to Release 2. Your task is only to remove copied files that are proven to be outside Release 2's scope. + +## Hard limits + +- Do not execute or resume the Release 2 implementation prompt. +- Do not search, list, fetch, or switch branches. Work only from the current checkout and the Release 2 evidence already present in it. +- Do not perform new release implementation, refactoring, dependency upgrades, builds, packaging, or unrelated cleanup. +- Do not commit changes. +- Preserve all pre-existing user changes. If a candidate removal overlaps a pre-existing change or its scope is unclear, stop and report it. + +## Establish the cleanup scope + +1. Read the completed Release 2 report, scope audit, manifests, package allowlists, and customer/release documentation produced by the prior execution. Use their verified `M`, `S`, and `R \ S` lists and file-level evidence as the cleanup authority. +2. Record the current checkout identity without querying branches, its working-tree status, and a complete inventory of files. Do not overwrite or discard existing changes. +3. If the prior execution's report or equivalent evidence does not establish the included scope and file dependencies, make no deletions. Report exactly which evidence is missing. +4. Classify each candidate file against the evidence. A file is removable only when it is proven outside `S` and not needed for Release 2 build, tests, generators, runtime, installation, packaging, CI, legal compliance, or customer-facing documentation. + +## Verify Qt 6 migration and customer handover requirements + +Use the existing source, build configuration, Docker configuration, scripts, and customer documentation as evidence. These are inspection requirements only: do not run builds, alter the build pipeline, or make changes to satisfy a failed check. + +1. Verify the retired Grantlee template engine has no remaining references in the project tree, including source, build files, dependency manifests, scripts, and documentation. The Qt 5-to-Qt 6 migration replaced it with KDReports. Exclude this prompt itself from the search. +2. Verify all CMake build configurations used for the project build with `RelWithDebInfo`. Check the relevant CMake presets, toolchain/build scripts, CI configuration, and customer instructions; report any conflicting configuration or missing evidence. +3. Verify Qt 6 is installed using `aqtinstall`, not Ubuntu `apt` packages. Inspect dependency installation and setup instructions, and report any Qt 6 installation through `apt` or any missing evidence. +4. Verify the customer handover uses Ubuntu 26.04 in the Docker container and `new_docker_build.sh` for the step-by-step source-code handover. The customer will transfer the source code and build pipeline into their own Jenkins CI/CD pipeline, where the binaries must be produced. Check the Docker configuration, script, and customer-facing instructions for consistency; report conflicts or missing evidence. + +## Remove only proven out-of-scope files + +- Physically remove the individual proven-out-of-scope files from the copied Release 2 tree. Do not merely exclude them from packages. +- Review source files, Markdown files, and configuration files, but never delete by extension, directory, filename similarity, or assumption. Release 2 source/test sources, headers, manifests, required build and CI configuration, legal notices, and its customer guide/release notes must remain when supported by the scope evidence. +- Before each deletion, check references from source and headers, CMake/build files, tests, generators, resources, runtime setup, install rules, packaging manifests, CI, and documentation. Record each removed path and the evidence/reason that it is outside scope. +- Avoid broad directory deletions. If a directory contains both in-scope and out-of-scope content, remove only individually verified files. +- Do not edit unrelated files or alter files just to make the repository look smaller. + +## Verify and report + +After cleanup, review the complete deletion list and current diff. Check that no remaining Release 2 file references a removed path and that the Release 2 manifests and documentation still agree with the retained tree. Run only non-destructive, relevant checks that do not rebuild or re-run the release. + +Report concisely: + +- Whether cleanup completed or stopped for insufficient evidence. +- The scope evidence used. +- Results of each Qt 6 migration and customer handover verification, including any conflicts or missing evidence. +- Every removed file and its evidence-backed reason. +- Any candidates retained because they are required or ambiguous. +- The final working-tree status and checks performed. +