Native-author minimal runnable PrintToSingleFileHtml payload from authoring packet

[svelderrainruiz]

Summary

#1621 now has deterministic bootstrap and native-authoring packet support, but the remaining blocker is still the actual repo-owned LabVIEW payload authoring step.

The supported NI custom-operation workflow is native LabVIEW authoring through Operations.lvproj / Toolkit-Operations.lvproj, not shell-side synthesis of runnable .vi files. This issue tracks the minimal human/native authoring slice that turns the current PrintToSingleFileHtml bundle from source-only into a runnable repo-owned payload.

Acceptance

• Author minimal repo-owned runnable payload files for fixtures/headless-corpus/operation-payloads/PrintToSingleFileHtml/.
• Add GetHelp.vi and RunOperation.vi plus only the support VIs required for them to execute.
• Keep the payload repo-owned and BSD-3 aligned; do not vendor installed NI files verbatim.
• Update payload provenance/docs/tests so the bundle no longer reports source-only once the runnable files are checked in.
• Keep public proof separate; this issue ends at runnable, not publicly proven.

Why now

• #1619 added installed-operation scaffolding.
• #1622 made the source-only bundle fail closed.
• #1623 adds the native-authoring packet with installed LabVIEW.exe, Operations.lvproj, Toolkit-Operations.lvproj, a checklist, and a launch helper.
• The remaining gap is no longer hidden automation debt; it is explicit native LabVIEW authoring.

Related

• Standing bootstrap/inspection lane: #1621
• Current partial PR: #1623
• Final public proof lane: #1617

[svelderrainruiz]

Activated as the next standing-priority slice after PR #1626 merged.

Prepared implementation branch already exists and is validated locally:

• branch: issue/origin-1624-minimal-runnable-print-payload
• commit: 353b9550
• focused inspection tests passed
• full tools/PrePush-Checks.ps1 passed

This slice sharpens the native-authoring boundary by requiring the expected payload files to inspect as real LabVIEW binaries before the bundle can report runnable.

[svelderrainruiz]

PR #1627 is now the active standing slice for this issue:

• PR: Update for standing priority #1624 #1627
• current head: a4a880d1

What this slice tightens:

• expected payload files must now inspect as real LabVIEW binaries before the bundle can report runnable
• placeholder text files no longer satisfy the executable-state contract

Local validation completed cleanly before PR promotion:

• pwsh -NoLogo -NoProfile -File tests/Inspect-OperationPayloadSourceBundle.Tests.ps1
• pwsh -NoLogo -NoProfile -File tools/Inspect-OperationPayloadSourceBundle.ps1 -BundlePath fixtures/headless-corpus/operation-payloads/PrintToSingleFileHtml -PassThru
• pwsh -NoLogo -NoProfile -File tools/PrePush-Checks.ps1

[svelderrainruiz]

Merged partial automation support in PR #1627 at commit d957b6ca2c41c36bd4e7ab3888704fdc242e2445.

What that slice finished:

• fail-closed runnable-payload inspection now requires real LabVIEW binary signatures
• placeholder .vi files no longer masquerade as a runnable payload bundle

What remains open here:

• the actual repo-owned native-authored GetHelp.vi / RunOperation.vi files are still not checked in
• this issue remains the native-authoring blocker and is no longer the best standing automation lane

I’m rotating standing-priority to #1628 so the active coding queue can keep moving on the NI Linux custom-operation runner and public-proof execution path while this native-authoring blocker stays explicit.

[svelderrainruiz]

Progress update: PR #1733 is open. This slice adds a deterministic post-authoring finalization helper instead of leaving the native LabVIEW handoff with manual manifest edits. The new helper, tools/Finalize-OperationPayloadSourceBundle.ps1, inspects the checked-in payload bundle, flips declared executable state to runnable only when real LabVIEW binary files are present, and emits a machine-readable finalization receipt. The current repo-owned PrintToSingleFileHtml bundle still blocks honestly as source-only, and the helper now records that blocked state without pretending the payload is runnable. This advances #1624 by turning the native-authoring completion path into a repeatable contract while keeping the actual LabVIEW binary authoring step explicit.