Conversation
|
PostgreSQL evidence correction (fresh RC8 runtime): current runtime classification is CAUSE_EVIDENCED / UX_VERIFICATION_REQUIRED. The active failure is database backup verification failure affecting GoldenTeeLive2019, PowerPuttLive2012, PowerPuttLive2013, SilverStrikeBowlingLive, TargetTossProBags, and TargetTossProLawndarts. Setup blocks before profile population. The fresh run did not reproduce the historical Argument types do not match fatal. Historical classification remains NOT_REPRODUCED_WITH_CURRENT_INSTALLED_BUILD / CODE_LEVEL_PROOF_MISSING. The uploaded script hash is 0FB84ABDA625AA83ED7BC085A9865BE5E58D09E0536CDA4913EDB01B7703EF5B; line 4955 is the hardware environment volume loop, not New-PostgresRecoveryBackup. PostgreSQL remains UX/runtime blocking until visible Retry / Skip / Details / Back, backup-incomplete and nothing-changed wording, affected friendly names plus identifiers, and no profile population after incomplete backup are verified. |
|
ReShade review correction: current PR implements a Windows Forms preview with Before/After/Split buttons, not a slider. No TrackBar or slider control is present in the preview window implementation. Classification: preview window IMPLEMENTED_LOCALLY / NEEDS_VISUAL_RUNTIME_PROOF; fallback UX IMPLEMENTED_LOCALLY / NEEDS_CI_AND_RUNTIME_VERIFICATION; ReShade slider NOT_IMPLEMENTED / NEEDS_RELEASE_MANAGER_DECISION. ARCADE proof remains required for preview opening, selected image display, comparison controls, safe missing-assets fallback, no pre-confirmation deployment, and bulk behavior. |
|
FFB real-caller mutation proof completed under Windows PowerShell 5.1. With the production plugin Start-TpmWorkflowStep call removed, the real Invoke-TpmFfbSetupMode regression failed exactly at Complete-TpmWorkflowStep with: Workflow can only skip its active step. The committed fix was restored from e4894e8 and the same focused test then passed: 1 passed, 0 failed. The passing test exercises the production callable with plugin choice N, asserts plugin StepSkipped, Closed lifecycle, no terminating exception, and zero Invoke-FFBPluginSetup calls. |
|
ReShade slider status correction: the earlier comment said the slider was not implemented. That was true at the earlier head only. Head |
Slice 0 final exact-head CI review — Pester version mismatch blocks certification-quality acceptanceDecision: Verified exact-head run:
Blocking compatibility issue: Authorized next action is narrowly limited to CI/toolchain pinning:
Do not begin Slice 1. Do not package, owner-smoke, use Arcade, merge, tag, publish, certify, or release. PR #321 remains HOLD. |
Slice 0 Pester pin repair reviewedDecision: Accepted local repair commit: Accepted scope:
GitHub PR #321 is still open/draft and remote head remains Next authorized action:
Do not begin Slice 1 until that exact-head run is accepted. No package, owner smoke, Arcade, merge, tag, publish, certification, or release is authorized. PR #321 remains HOLD. |
Slice 0 immutable current-release snapshot — FINAL ACCEPTANCEDecision: Accepted exact head: Accepted hosted run: Verified directly on GitHub:
Accepted certification-quality evidence:
Slice 0 is closed. Next authorized engineering phase is Slice 1: migrate the static GameSupport contract corpus from the historical 695-profile snapshot to the accepted immutable 925-profile current-release snapshot. Constraints remain:
Known tester/runtime findings remain hard pre-owner-smoke blockers and are not considered closed by Slice 0 acceptance. |
Slice 1 current-release GameSupport migration — implementation reviewDecision: The implementation direction is broadly correct, but the packet does not yet satisfy the authorized Slice 1 acceptance gate. Accepted evidence so far:
Blocking gaps before commit review:
No commit is authorized yet. PR #321 remains HOLD. No runtime phase, package, owner smoke, Arcade, merge, tag, publish, certification, or release is authorized. |
Documentation screenshot requirement — owner directiveOwner requirement: TPM documentation must include real screenshots, not text-only walkthroughs. This is now a standing release/documentation requirement for RC8 and later work. Required surfaces:
Screenshot policy:
This requirement does not authorize package/owner-smoke/Arcade/merge/tag/publish/release by itself. It should be incorporated into the current PR #321 documentation acceptance criteria and future screenshot capture should use an exact-head validated candidate. |
Screenshot documentation gate — Desktop capture blocked; authorize Arcade screenshot-only captureDesktop OMP correctly stopped without launching a stub runtime. Accepted evidence:
Decision: authorize a narrow Arcade OMP screenshot-only capture phase. Arcade authorization is limited to:
If Arcade does not have a genuine matching runtime root, STOP and retain the screenshot documentation HOLD. No package rebuild, merge, tag, publish, certification, or release is authorized. |
Arcade screenshot exact-head recovery — advisor finding requires proof before acceptanceCurrent disposition remains The recovery packet claims the exact-head worktree and candidate hash are correct, but Advisor 1 raised a concrete provenance concern: the verification output immediately after worktree creation may have been read from the OLD checkout rather than from the new screenshot worktree, and the worktree path may have been parsed/nested unexpectedly. Standing advisor rule applies: this finding must be PROVEN or DISPROVEN with direct evidence before the recovery gate is accepted. Required evidence from ARCADE:
Expected exact values:
If those values are proven from the exact new worktree path, Advisor 1 is DISPROVEN and the only remaining blocker is the absence of a genuine TeknoParrot runtime on ARCADE. If they are not proven, Advisor 1 is PROVEN and the recovery worktree must be recreated correctly before any screenshot/runtime work. Do not launch runtime, capture screenshots, or modify docs until this provenance concern is closed. No package, owner-smoke, merge, tag, publish, certification, or release is authorized. |
Arcade screenshot worktree provenance — acceptedDecision: Advisor 1 finding is DISPROVEN by direct evidence from the Git-registered screenshot worktree. Accepted proof:
The provenance gate is therefore closed. Next blocker: establish whether ARCADE has a genuine TeknoParrot runtime root suitable for documentation capture. Runtime discovery is now authorized, but launch remains blocked until runtime identity, GameProfiles, containment, and reparse/junction safety are proven. No owner-smoke, broad runtime reproduction, package rebuild, merge, tag, publish, certification, or release is authorized. |
Arcade runtime discovery — accepted for screenshot-only launchDecision: Accepted runtime root: Accepted evidence:
Advisor note is accepted as ALREADY SATISFIED / DISPROVEN AS A BLOCKER: the known specific runtime path was revalidated, and the runtime-side manager-script hash mismatch is not a launch-eligibility requirement under the screenshot-only authorization because the accepted candidate is executed from its isolated exact-head worktree without overwriting the runtime. Important documentation caveat: the external TeknoParrot runtime is version 1.0.0.2132 with 929 profiles, while the accepted immutable TPM release-support snapshot is 1.0.0.2128 / 925 profiles. Screenshots must not imply that 929-profile runtime state is the same immutable catalog evidence. Avoid or clearly caption any visible profile-count/version discrepancy. Authorized next action:
If launch reveals a product defect, stop and report it rather than hiding it in documentation. |
Arcade runtime launch review — approved for screenshot-only captureDecision: Accepted prior gates:
Advisor finding: Next authorization is limited to launching the exact accepted TPM candidate only as needed to capture genuine documentation screenshots in full-screen mode where useful. This remains a documentation-only runtime exception. No general owner-smoke, broad runtime reproduction, package rebuild, merge, tag, publish, certification, or release is authorized. If launch exposes any genuine UI/runtime defect, stop and record it; do not conceal it with alternate screenshots. |
Screenshot documentation capture — sensitive desktop-wide capture rejected; use isolated TPM-window captureDecision: The capture attempt was handled correctly:
Advisor findings are accepted:
Next authorized action is narrower: capture the TPM UI as an isolated application/window region rather than a desktop-wide screenshot. Use a capture method that excludes terminal/tooling and personal paths. If the current TPM interface is terminal-based, frame only the TPM console window or crop to the TPM UI after capture, provided sensitive content is fully excluded and context remains beginner-readable. No mock/synthetic UI is allowed. Do not alter the product solely to make screenshots prettier. If a clean isolated TPM-window screenshot cannot be produced with available tools, retain HOLD and report the capture-method limitation explicitly. |
Screenshot gate — retry with real standalone console windowDecision: The PTY-based isolated-window attempt correctly returned HOLD because Advisor finding:
Required next test:
If the standalone process still has no capturable HWND, retain HOLD and report that the advisor fix hypothesis is disproven on ARCADE. No README/docs update until one clean sanitized proof screenshot is reviewed. No owner-smoke, broad runtime reproduction, package, merge, tag, publish, certification, or release is authorized. |
Screenshot standalone-window retry — advisor bug PROVEN; previous Handle=0 result invalidDecision: Advisor finding is PROVEN. Root cause:
Required correction:
Do not capture screenshots or update docs until the corrected PID-specific window proof succeeds. No owner-smoke, broad runtime reproduction, package, merge, tag, publish, certification, or release is authorized. |
Screenshot gate — non-interactive ARCADE session now strongly evidencedDecision: Accepted findings:
Advisor 1's new finding is accepted as PROVEN AS A STRONG HYPOTHESIS, WITH ONE DIAGNOSTIC STILL NEEDED: the automation session appears non-interactive / detached from a real desktop, so HWND-based capture may be structurally unavailable regardless of launch technique. Next authorized action is diagnostic only:
If the automation process is not in an interactive desktop session, the screenshot gate should remain HOLD and capture must move to a human-visible interactive session/manual capture workflow rather than more automation tricks. No owner-smoke, broad runtime reproduction, package, merge, tag, publish, certification, or release is authorized. |
Screenshot gate — interactive session confirmed; stop HWND debugging and use Computer UseDecision: Accepted findings:
Advisor's conhost/Windows Terminal ownership theory is plausible, but further HWND/process-owner debugging is no longer the preferred path because Computer Use is available in the active interactive session. Next action:
If Computer Use cannot see the TPM UI, then return HOLD with that exact evidence. Do not restart HWND/conhost experiments unless Computer Use fails and a new diagnostic is explicitly authorized. No owner-smoke, broad runtime reproduction, package, merge, tag, publish, certification, or release is authorized. |
Screenshot capture clarification — full-screen TPM UI requiredOwner requirement clarified: retained documentation screenshots must show TPM in full-screen / maximized presentation, not as a small floating console. Interpretation:
The first proof image should therefore be a full-screen TPM main-menu screenshot, sanitized for privacy, with README/docs still unchanged until review. |
Screenshot proof accepted; add window-cleanup requirementDecision: Accepted proof:
New standing screenshot/runtime cleanup rule from owner: This includes:
Required end-state:
Next authorized documentation step may map the accepted proof image into README/QuickStart and continue the screenshot set using the same capture/privacy/maximize rules. No owner-smoke, broad runtime reproduction, package, merge, tag, publish, certification, or release is authorized. |
Screenshot cleanup verification — advisor self-match finding PROVEN; rerun cleanup scan correctlyDecision: Advisor finding is PROVEN. The cleanup scan used a command line containing the exact TPM script path as the search needle. That checker process can therefore match itself, so the raw match count is not authoritative. Required correction:
Only after this corrected self-excluding scan returns zero may Do not modify README/QuickStart or continue screenshot mapping until cleanup verification is closed. No owner-smoke, package, merge, tag, publish, certification, or release is authorized. |
Screenshot cleanup gate — PASSDecision: Accepted evidence:
Standing cleanup rule is satisfied: Next permitted step is documentation mapping/review of the already accepted screenshot asset. README/QuickStart/package/merge/tag/publish/certification/release remain untouched so far. |
Screenshot documentation integration reviewDecision: Accepted:
Advisor image-asset convention finding is PROVEN. Direct repository evidence at exact accepted HEAD
Required correction before commit review:
No commit/push/package/owner-smoke/merge/tag/publish/certification/release is authorized yet. |
Screenshot documentation final review — one validation gap remainsDecision: Accepted:
Remaining gap:
Before commit review, perform one true rendered preview of both edited files using any safe local method (for example, a temporary Markdown-to-HTML render outside the repo, or another Markdown renderer already available). Verify headings, screenshot embedding, sizing, surrounding caption/text, and no broken layout. Do not add renderer artifacts to the repository. If true rendering cannot be produced with available tools, return that explicitly and keep HOLD rather than claiming a visual pass. No commit/push/package/owner-smoke/merge/tag/publish/certification/release is authorized yet. |
Render-validation blocker — use GitHub's own Markdown API, no commit requiredDecision: The packet is correct to retain HOLD: no local Markdown renderer is installed, so rendered review remains unresolved. Advisor dispositions accepted:
Next authorized validation method: use GitHub's Markdown rendering API through This is preferable to installing arbitrary Markdown tooling and gives a preview close to GitHub's actual rendering. Do not add temporary HTML/request files to the repository. Close browser/helper windows afterward. No commit/push/package/owner-smoke/merge/tag/publish/certification/release is authorized yet. |
GFM render failure review — request-construction bug must be proven/disprovenDecision: Advisor blocker is PROVEN AS A VALID CONCERN / NOT YET PROVEN AS ROOT CAUSE. Reason:
Required next step:
Do not classify No commit/push/package/owner-smoke/merge/tag/publish/certification/release is authorized yet. |
GFM render packet review — two advisor claims require explicit final dispositionDecision: The documentation/render work is otherwise in good shape:
Advisor finding 1 (request encoding/round-trip):
Advisor finding 2 (actual image rendering):
Do not change README, QUICKSTART, or the image unless these checks reveal a real defect. Do not commit/push yet. No package, owner-smoke, merge, tag, publish, certification, or release is authorized. |
Screenshot documentation commit review — final image-selector advisor finding must be closedDecision: The packet claims the exact rendered element for Under the standing advisor rule, this discrepancy must be explicitly proven or disproven before commit authorization. Required final proof:
If exact selector proof passes, Advisor 1 is DISPROVEN and the screenshot documentation can move to commit review. If it fails, Advisor 1 is PROVEN and the docs/render evidence must be corrected. No commit/push/package/owner-smoke/merge/tag/publish/certification/release is authorized yet. |
Screenshot documentation advisor proof — closedDecision: Advisor target-image concern is now DISPROVEN by corrected exact-target extraction from fresh GitHub GFM responses. Accepted evidence:
The earlier bad extraction is explicitly understood: it selected the first The screenshot documentation work may now move to commit review, subject to the final source diff/content review and preservation of the standing cleanup/advisor rules. |
Screenshot documentation commit review — accepted for push + exact-head CIDecision: Accepted local commit: Parent: Accepted commit boundary:
Accepted evidence:
GitHub PR #321 is still open/draft and remote head remains Next authorized action:
No package, owner-smoke, merge, tag, publish, certification, or release is authorized. |
Screenshot documentation — FINAL ACCEPTANCEDecision: Accepted exact head: GitHub verification:
Advisor findings:
Accepted documentation commit:
Screenshot documentation gate is CLOSED. This acceptance does not authorize package build, owner smoke, merge, tag, publish, certification, or release. Overall RC8 remains gated by the remaining Slice 1/runtime/release work. |
1 participant
Status: HOLD
PR #321 current local candidate head: d0f7659.
Follow-up changes
ReShade's five bounded choices retain their beginner-friendly names and descriptions, while the terminal chooser, Details view, setup listing, and preview gallery now show a canonical
Techniques:line. The line is generated from each profile's orderedTechniqueOrderand the approved effect catalog'sRelativeFilesandTechniqueNamefields. It shows shader filenames without internal paths, preserves the approved order, fails closed on missing catalog metadata, and does not imply that live-fetched runtime files are bundled.FFB overlap ownership is now exclusive. The plugin workflow resolves overlaps before third-party mutation, treats native FFB Blaster as the safe default, accepts only an explicit
Nfor plugin ownership, and treats blank or invalid input as native. An explicit plugin choice creates a fresh verified profile backup, clears native FFB Blaster fields for exactly the overlap set, verifies the saved values, and blocks third-party deployment if the transition or rollback cannot be completed safely. Documentation, architecture, wiki staging, and the RC8 invariant inventory record the same behavior.Changed files
The complete PR changes these 26 files:
Verification
PSScriptAnalyzerSettings.psd1: 0 findingsNo candidate ZIP was built from this current head. Approved-runtime validation, package creation, runtime certification, merge, tag, release, certification publication, PR approval, wiki publication, GitHub release, and monitor unpause remain unauthorized.
This push/CI authorization does not authorize package or owner-runtime work. PR #321 remains HOLD pending hosted CI result, approved-runtime validation, and Release Manager authorization.