Version 1.0 readiness coordination and final release gate

[Jumpstile]

Purpose

Coordinate the work required to move from the current RC7 release-candidate state to an explicit final Version 1.0 release decision.

This is a coordination and release-governance issue. It does not itself authorize code changes, documentation rewrites, release asset replacement, tag movement, or final Version 1.0 publication. Child fixes or documentation updates must remain separately scoped, reviewed, validated, and merged before this issue can be closed.

Current baseline

As of 2026-08-22:

• Current public latest release: TeknoParrot Manager v1.0 RC7
• Tag: v1.0-RC7
• RC7 tag target: 456cc21
• Current main after post-publication roadmap/documentation governance updates: 7355dc9
• GitHub release visibility: RC7 is visible as Latest on the repository front page
• RC7 asset: TeknoParrot.Manager.v1.0.RC7.zip
• RC7 asset size: 4,862,794 bytes
• RC7 asset SHA-256: 45D14469CF750AC14B0F4113FB4117E2DA1C80F612C335D66B61C6E3FE5ABF84
• Final v1.0 is unpublished

Required final-publication wrap-up before 1.0 planning can be called clean

• Verify Scripts mirror contains the exact RC7 GitHub asset bytes or explicitly record if mirror publication is deferred.
• Verify mirror hash and size against the GitHub asset.
• Confirm wiki publication state and any staged wiki changes that were published.
• Run or review final stale-release wording sweep: RC7 current, RC6 historical, final v1.0 unpublished.
• Run or review attribution sweep across repo files, release notes, wiki publication notes, issue/PR/release comments where applicable.
• Confirm no tag movement, asset replacement, or hidden final v1.0 publication occurred.

Version 1.0 readiness workstream

Before final Version 1.0 can be authorized, review and classify all remaining Version 1.0 work:

1. Open release:version-1.0 issues.
2. Open release:rc-required issues.
3. Open issues in Milestone 1.
4. Open high/critical priority bugs.
5. Open documentation/onboarding issues that affect first-time users.
6. Issues whose closure status or release disposition conflicts with current evidence.

Each item must be classified as one of:

• Required before final Version 1.0.
• Defer to post-1.0 with explicit rationale and labels/milestone corrected.
• Already satisfied by merged work, with evidence and closure update required.
• Duplicate/superseded, with relationship recorded.
• Needs more evidence before a release decision.

Known items to include in the review

• Feature Request - Rebind controls #59 Rebind controls — open tracked Version 1.0 backlog item, requested ASAP before final 1.0.
• Pre-1.0 first-run onboarding decision audit and workflow coordination #249 first-run onboarding decision audit and workflow coordination.
• Clarify RetroBat, TeknoParrot, and mouse/keyboard controls onboarding #272 RetroBat/TeknoParrot mouse-keyboard/lightgun onboarding documentation.
• Launch can succeed after controls setup is skipped or unverified #255 controls readiness, if any follow-up remains after RC7.
• Enforce release-document consistency in CI #237 release-document consistency, already verified/closed but should remain part of final release evidence.
• Remove the normal Eggman recognition-data save-path decision from first-run setup #252 recognition-data path, already verified/closed but should remain part of final release evidence.
• Generalize contract-backed missing component warnings beyond pcsx2x6 #268 contract-backed missing component warnings, already verified/closed but should remain part of final release evidence.

Post-1.0 design tracks such as #267 and #273 should remain visible in the roadmap but must not block final Version 1.0 unless an explicit current-release defect is proven.

Final Version 1.0 release gate

Final Version 1.0 requires a separate explicit approval after:

• all required pre-1.0 issues are closed or deliberately deferred;
• release notes and documentation identify final v1.0 accurately;
• package validation passes under Windows PowerShell 5.1 and PowerShell 7;
• full Quality suite passes under both PowerShell versions;
• markdown/link/release-state checks pass;
• attribution sweep is clean;
• release asset hash, size, contents, and mirror state are recorded;
• GitHub release visibility behavior is correct;
• final v1.0 tag and release plan are approved before publication.

Non-goals

• No RC7 asset replacement.
• No force-moving v1.0-RC7.
• No final v1.0 tag or release until explicitly authorized.
• No cabinet-control, LEDBlinky, lightgun calibration, or other post-1.0 roadmap feature implementation as part of this coordination issue.
• No broad refactor unless separately scoped and justified.

Acceptance criteria

• RC7 publication wrap-up evidence is complete or deferrals are explicit.
• All open Version 1.0 / RC-required / Milestone 1 issues are classified.
• Labels and milestones are corrected where needed.
• Required pre-1.0 work has child issues or PRs with validation evidence.
• Deferred work has clear rationale and post-1.0 tracking.
• A final Version 1.0 release checklist is ready for independent review.
• Final Version 1.0 remains unpublished until an explicit final release decision is recorded.

[Jumpstile]

PR cleanup pass started for Version 1.0 readiness.

Open PRs reviewed:

• Phase 0: native LaunchBox plugin feasibility spike #245 — Phase 0 native LaunchBox plugin feasibility spike

  • Current state: open, non-draft, mergeable false.
  • Cleanup disposition: post-1.0 feasibility evidence for EPIC: Native LaunchBox / Big Box plugin for TeknoParrot Manager #242; not a final Version 1.0 blocker.
  • Labels added: release:post-1.0, status:needs-review.
  • Comment added: 5381092884.

• Fix stale AutoSync extraction progress overlay (#243) #246 — Fix stale AutoSync extraction progress overlay (AutoSync extraction progress leaves stale console artifact before registration scan #243)

  • Current state: open draft, mergeable false.
  • Cleanup disposition: possible Version 1.0 candidate, but stale and not mergeable as-is.
  • Labels added: release:version-1.0, status:needs-rebase.
  • Comment added: 5381093313.

• Add guarded ReShade runtime updates and effects research #248 — Add guarded ReShade runtime updates and effects research (Existing ReShade runtime updates route to manual instructions #247)

  • Current state: open draft, mergeable false.
  • Cleanup disposition: possible Version 1.0 candidate, but stale and not mergeable as-is.
  • Labels added: release:version-1.0, status:needs-rebase.
  • Comment added: 5381093776.

General conclusion:

• No open PR is currently merge-ready.
• Phase 0: native LaunchBox plugin feasibility spike #245 should not block final 1.0 unless separately authorized.
• Fix stale AutoSync extraction progress overlay (#243) #246 and Add guarded ReShade runtime updates and effects research #248 require rebase/revalidation or replacement PRs before they can be considered.
• None of these PRs authorizes a tag, release, asset replacement, wiki publication, or final Version 1.0 release action.

[Jumpstile]

Arcade validation agent real-machine validation request

Owner request: run a full TPM validation pass on the arcade machine using the desktop app with computer-use.

Purpose:

• Validate the current RC7/latest-public-release experience on the real arcade machine.
• Collect real UI, launch, controls-readiness, frontend, and evidence observations for the Version 1.0 readiness gate.
• Do not perform development, speculative fixes, release publication, tag movement, or asset replacement.

Scope:

• Use the existing installed/current TPM state and the current published RC7 asset where appropriate.
• Confirm TPM starts cleanly and clearly identifies the current release state.
• Exercise the main user-facing paths that matter for final 1.0 readiness: startup, saved settings reuse, health/check summaries, Action Required output, read-only warnings, controls-readiness messaging, LaunchBox/Big Box/RetroBat-facing expectations where present, and at least one known game launch path.
• Prefer observe-first validation. Change only when an approved workflow explicitly asks for user confirmation and the test objective requires it.

Evidence rules:

• Use computer-use for real UI observation, screenshots, launch behavior, and attended interaction.
• Record TPM version/source, current repo/release state if visible, command used, PowerShell host, Windows version if practical, and paths sanitized as needed.
• For any write-capable action, record before/after SHA-256, size, LastWriteTimeUtc, and file counts for affected TPM/TeknoParrot files before changing anything.
• Preserve existing backups and note backup paths.
• Capture screenshots/log snippets where useful.
• Report observed facts separately from inference.
• Confirm clean game/emulator exit and remaining processes after launch tests.

Boundaries:

• Do not hand-edit TeknoParrot XML.
• Do not edit game files directly.
• Do not change Windows-global settings, drivers, firmware, device software, LaunchBox, Big Box, RetroBat, or controller software unless a separately approved test step requires it.
• Do not merge, tag, package, publish, replace assets, edit wiki pages, or mark final Version 1.0 released.
• Do not implement post-1.0 features such as LaunchBox plugin work, LEDBlinky, cabinet inventory, or aiming-device calibration.

Required report back:

• Exact TPM entry point used.
• Current TPM release/version shown.
• Whether startup/onboarding messaging is understandable.
• Whether advanced-user value is visible or still under-documented from the installed experience.
• Whether Action Required output distinguishes launch, registration, controls readiness, and compatibility warnings.
• Any games tested, launch result, controls result, and exit/process cleanup result.
• Any frontend path tested and whether behavior differs from direct TeknoParrot launch.
• Files changed, with before/after evidence, or explicit confirmation no tracked/runtime files changed.
• Screenshots/log excerpts collected.
• Defects found, grouped as release-blocking, pre-1.0 should-fix, post-1.0, or evidence-needed.

This validation feeds #274. It does not itself authorize final Version 1.0 publication.

[Jumpstile]

Version 1.0 audit accepted — tracker cleanup pass started

Accepted the Desktop implementation agent audit at current main/origin main 7355dc95ae9b26e9cf63432c3095f890a11208a7 with current Quality CI passing and current baseline 656/656 under both Windows PowerShell 5.1 and PowerShell 7.

Release-state constraints remain unchanged:

• RC7 remains the current public latest release.
• Final Version 1.0 remains unpublished.
• No tag movement, release publication, release asset replacement, PR merge, branch change, or package change is authorized by this comment.

Initial cleanup direction:

• Close or verify only items the audit classified as already satisfied by merged work.
• Defer cosmetic/hygiene work out of Version 1.0 where appropriate.
• Keep implementation blockers open: First-run advisory/handoff UX for TeknoParrot's own setup wizard (#253) #260, Detect RawInput and RawInputTrackball profile capabilities #42, and focused Existing ReShade runtime updates route to manual instructions #247 replacement work if Existing ReShade runtime updates route to manual instructions #247 remains in 1.0 scope.
• Keep Reproduce the reported R/B staging-folder recovery crash #251 open as evidence-needed unless a concrete reproduction appears.
• Keep Version 1.0 readiness coordination and final release gate #274 open until final Version 1.0 release gate evidence is complete.

[Jumpstile]

RC7 Scripts mirror gap reported

User reported on 2026-08-22 that there is no RC7 ZIP in the W: Scripts folder.

Treat this as an incomplete publication-wrap-up/mirror step, not a new RC7 package-content defect.

Known canonical RC7 GitHub asset:

• Release: v1.0-RC7
• Asset filename: TeknoParrot.Manager.v1.0.RC7.zip
• Size: 4,862,794 bytes
• SHA-256: 45D14469CF750AC14B0F4113FB4117E2DA1C80F612C335D66B61C6E3FE5ABF84

Required follow-up:

1. Locate the intended W: Scripts mirror directory.
2. Confirm whether any RC7 ZIP exists under an alternate filename.
3. If absent, copy the exact GitHub-verified RC7 asset bytes to the Scripts mirror.
4. Preserve the canonical GitHub asset filename unless the Scripts mirror has a documented naming convention requiring a separate display name.
5. Verify mirror size and SHA-256 after copy.
6. Record the final mirror path, size, SHA-256, LastWriteTimeUtc, and whether the bytes match the GitHub asset.

Do not create a new GitHub release, move the tag, replace the release asset, publish final v1.0, or modify the RC7 package contents as part of this mirror correction.

[Jumpstile]

Correction to prior mirror-gap note: user rechecked the W: Scripts folder and confirmed the RC7 ZIP is present.

Do not treat the earlier missing-file report as an active blocker.

Still required for final wrap-up evidence:

• record the exact Scripts mirror path;
• confirm filename;
• verify size;
• verify SHA-256 equals 45D14469CF750AC14B0F4113FB4117E2DA1C80F612C335D66B61C6E3FE5ABF84;
• record LastWriteTimeUtc if practical.

Canonical RC7 asset remains TeknoParrot.Manager.v1.0.RC7.zip, 4,862,794 bytes.

[Jumpstile]

Roadmap push status update — LaunchBox / Big Box native plugin track

Desktop implementation agent pushed the ROADMAP.md-only update after rebasing on the current remote state.

Current pushed commit:

• 91403cb

Scope:

• ROADMAP.md only
• Adds the post-1.0 LaunchBox / Big Box native plugin roadmap track using PR Phase 0: native LaunchBox plugin feasibility spike #245 as Phase 0 feasibility evidence
• Does not merge PR Phase 0: native LaunchBox plugin feasibility spike #245
• Does not authorize final Version 1.0 work
• Does not affect RC7 package, release, tag, wiki, or Scripts mirror state

Reported state:

• Branch: main
• origin/main matches 91403cb
• Worktree clean
• No untracked release/package files
• No force-push used
• GitHub reported direct-push branch-protection requirements were bypassed for this push

Validation before/around push:

• Markdown/local links: 43 docs, 6 links, 0 missing
• ReleaseConsistency: 18/18 passed
• Stale active-release guidance: 0
• Attribution sweep: 1/1 passed
• git diff --check: clean

Hosted Quality CI:

• Run: https://github.com/Jumpstile/teknoparrot-manager/actions/runs/32582018309
• Status at report time: in progress

Do not record this as a passed hosted CI run until the run completes successfully.

[Jumpstile]

RC7 arcade install/package validation update

Arcade validation agent copied RC7 into the real TeknoParrot install directory and verified the installed package byte-for-byte across all 337 package files.

Evidence reported:

• Install path: C:\Users\EliSi\LaunchBox\Emulators\TeknoParrot
• Backup: W:\Emulators\TeknoParrot\Scripts\RC7-real-validation-backup-20260822-112951
• Package-file verification: byte-for-byte match across all 337 package files
• TPM log confirms startup: Script started (v1.0)
• Runtime log changed only from startup
• Repository tracked files changed: none

Interactive validation status:

• Blocked for Arcade validation agent computer-use because TPM runs as a PowerShell console application and computer-use cannot automate or target terminal windows under its safety rules.
• This is not a TPM runtime failure and not a package-content defect.
• Remaining real-machine validation requires manual observation of the TPM console flow, screenshots, or TPM log/output excerpts.

Disposition:

• RC7 install/package deployment on the arcade machine: verified.
• RC7 interactive menu/onboarding/Action Required/game-launch flow: still needs manual-observation evidence.
• No repository, PR, release, tag, package, wiki, or mirror change is authorized by this evidence.

[Jumpstile]

Validation harness path for Arcade validation agent

Owner instruction: pursue a way for computer-use to test TPM even though it cannot safely operate the PowerShell terminal window directly.

Decision:

• Do not treat terminal-control limitations as a TPM failure.
• Revise the arcade validation approach so TPM is driven by a PowerShell validation harness where safe.
• Use computer-use for GUI/game observation only: TeknoParrot UI, game windows, screenshots, control-response observation, clean-exit/process checks.

Current RC7 arcade validation status remains:

• RC7 package deployment to the arcade TeknoParrot install is verified byte-for-byte across 337 package files.
• Interactive menu/onboarding/game-launch validation still needs evidence.

Required revised validation approach:

1. Record baseline file counts, hashes, sizes, and LastWriteTimeUtc for likely affected TPM/TeknoParrot files.
2. Create any temporary validation harness outside the repository or clearly mark it as disposable validation evidence.
3. Run TPM with scripted input only for safe flows such as startup, menu display, dry-run/preview, health/readiness checks, and exit.
4. Capture stdout/stderr, transcript where available, TPM logs, Action Required output, exit code, and changed-file evidence.
5. Use computer-use only for non-console observation: TeknoParrot UI/game launch, screenshots, controls behavior, exit/process cleanup, and frontend comparisons.
6. If a prompt cannot be scripted safely, report exact prompt text, expected input, reason it cannot be automated, and manual evidence needed.
7. Do not hand-edit TeknoParrot XML, rebuild packages, publish releases/tags/wiki/mirror changes, or make code changes as part of the validation pass.

This feeds the Version 1.0 readiness gate and does not authorize final Version 1.0 publication.

[Jumpstile]

Re-evaluation after new open issues — 2026-08-22

Re-checked the open issue set after new work was added.

New / newly relevant Version 1.0 item

• Add non-interactive validation report mode for release and arcade testing #276 — Add non-interactive validation report mode for release and arcade testing
  • Classification: Required before final Version 1.0 if it can remain narrow, read-only/dry-run, and non-disruptive.
  • Rationale: RC7 arcade package deployment was verified, but console-menu validation exposed a real release-testability gap. A non-interactive validation report mode would make final 1.0 evidence stronger, reduce manual terminal dependence, and support advanced users.
  • Guardrail: If implementation requires broad refactor or destabilizes interactive behavior, defer implementation and use a temporary validation harness for final 1.0.

Confirmed still post-1.0, not current blockers

• Reimplement auto-updater SHA-256 verification on current main #234 — Reimplement auto-updater SHA-256 verification on current main

  • Current labels/milestone show release:post-1.0, priority:medium, milestone 3.
  • Security-relevant hardening, but not a final 1.0 blocker unless owner explicitly promotes it.

• Re-evaluate real-hardware certification cadence #235 — Re-evaluate real-hardware certification cadence

  • Current labels/milestone show release:post-1.0, priority:medium, milestone 3.
  • Governance/certification policy work; not a final 1.0 blocker.

Updated practical final-1.0 blocker list

Required / active:

1. Version 1.0 readiness coordination and final release gate #274 — final coordination and release gate.
2. Add non-interactive validation report mode for release and arcade testing #276 — non-interactive validation/report mode, narrow read-only/dry-run scope.
3. First-run advisory/handoff UX for TeknoParrot's own setup wizard (#253) #260 — TeknoParrot UI first-run handoff advisory.
4. Clarify RetroBat, TeknoParrot, and mouse/keyboard controls onboarding #272 — RetroBat / direct TeknoParrot / mouse-keyboard onboarding docs.
5. Clarify advanced-user value in 1.0 messaging and documentation #275 — advanced-user value documentation wiring.
6. Detect RawInput and RawInputTrackball profile capabilities #42 — RawInput / RawInputTrackball profile capability detection.
7. Existing ReShade runtime updates route to manual instructions #247 — focused ReShade runtime update fix, if retained for 1.0.
8. Pre-1.0 first-run onboarding decision audit and workflow coordination #249 — onboarding umbrella, remains open until remaining children are resolved or explicitly deferred.

Conditional:

• Reproduce the reported R/B staging-folder recovery crash #251 — only blocks final 1.0 if the staging crash reproduces or concrete defect evidence appears.

Deferred / not final-1.0 blockers:

• Standardize Prettier formatting before 1.0 #233, AutoSync extraction progress leaves stale console artifact before registration scan #243, Reimplement auto-updater SHA-256 verification on current main #234, Re-evaluate real-hardware certification cadence #235 and post-1.0 roadmap/strategic tracks unless owner explicitly promotes them.

No release action

This re-evaluation did not authorize or perform final v1.0 publication, RC7 asset replacement, tag movement, package rebuild, wiki publication, mirror changes, PR merge, or branch changes.

Needs response from: nobody unless new issues are added or owner changes priority.