6 verbs have no headless kernel implementation (quickTime.*, string.nthChar); misclassified as broken in #879 #882

Rationale

6 verbs referenced by Virgin.root scripts have NO kernel implementation in the headless build. Their scripts "fail to compile" with "Error in kernel call. The verb X does not exist, or isn't set up to handle messages" — NOT stored corruption (control: string.upper has byte-identical kernel(...) shape and compiles). These were misclassified as broken scripts in #879. Disposition needed per verb: implement headless, or document as intentionally absent.

Current State

Missing kernel implementations (headless build, verified 2026-08-10):

1. quickTime.isPlaying — no kernel implementation
2. quickTime.open — no kernel implementation
3. quickTime.play — no kernel implementation
4. quickTime.stop — no kernel implementation
5. window.quickTime — no kernel implementation
6. string.nthChar — no kernel implementation

Error signature:

• "Error in kernel call. The verb X does not exist, or isn't set up to handle messages"
• NOT stored corruption (control test: string.upper has byte-identical kernel(...) call shape and compiles successfully)

Impact:

• Scripts referencing these verbs fail at compile time in headless build
• Misclassified as "genuinely broken scripts" in 12 Virgin.root scripts genuinely broken in DB (fail to compile in place); webBrowser.openURL + cleanRoot block #855 #879 (should be "missing headless implementations")
• Blocks scripts that call these verbs (e.g., any script using string.nthChar or quickTime.*)

Desired Outcome

For each missing verb, decide:

1. Implement headless: Add kernel implementation (especially string.nthChar, which is presumably trivial)
2. Document absent: quickTime verbs on headless don't make sense; document as intentionally GUI-only

Recommendation

string.nthChar (HIGH priority):

• Presumably straightforward string utility (return Nth character)
• Used in active scripts
• Recommendation: implement in headless build

quickTime. (LOW priority)*:

• GUI/multimedia operations (play, stop, etc.)
• Questionable value on headless server
• Recommendation: document as GUI-only; no headless implementation needed
• Alternative: stub implementations that return errors or no-op

window.quickTime (LOW priority)**:

• Related to quickTime operations
• Likely GUI-only
• Recommendation: document as GUI-only

Exit Criteria

• For each verb: decision made (implement or document)
• string.nthChar implemented in headless build (if decision is "implement")
• quickTime verbs documented as GUI-only (if decision is "document")
• Scripts referencing these verbs compile successfully (after decision applied)
• 12 Virgin.root scripts genuinely broken in DB (fail to compile in place); webBrowser.openURL + cleanRoot block #855 #879 corrected: reclassify these as "missing headless implementations" not "genuinely broken"

Related Context

• Found by: langscan comment-strip scanner ignored single-quoted char constants: 0xC7 inside 'x' literals corrupts scripts cumulatively on install (was misattributed to newScriptObject size/reinstall) #866 investigation, 2026-08-10
• Related issues: 12 Virgin.root scripts genuinely broken in DB (fail to compile in place); webBrowser.openURL + cleanRoot block #855 #879 (misclassified as broken scripts), webBrowser.openUrl fails to compile headless; blocks first-run finishInstall flow #865 (webBrowser issues)
• Code: Headless kernel implementation, Virgin.root scripts referencing quickTime and string.nthChar
• Build: Headless vs GUI build configurations
• Verification: Control test shows string.upper compiles (kernel implementation present)

Misclassification Note

#879 incorrectly classified these as "genuinely broken scripts" (stored corruption). They are actually "missing kernel implementations in headless build" — a build/configuration issue, not a data integrity issue. The distinction matters: stored corruption requires data repair; missing implementations require build decisions.