SDE 1.2.5 — self-update UAT candidate

SDE 1.2.5 permission-migration candidate

This signed prerelease contains the Windows legacy parent-permission migration
merged in PR #55 and the Linux history correction accepted in 1.2.4 UAT.
Existing releases and assets remain immutable. App/engine identity is 1.2.5;
the development-tool baseline remains 1.2.1. Keep application updates paused.
No stable promotion or classroom resume is authorized by candidate publication.

Included correction and validation

An elevated application installation can remove the reported legacy BUILTIN
Users Write grant from the fixed Skyview ProgramData parent, including its
container-inherited form, only when existing descendants are already protected.
It pins the directory during validation/migration, preserves private child
permissions and baseline contents, and rejects broader grants, writable files,
links and unexpected owners. Unknown layouts still require mentor review.
The unattended worker continues to reject an untrusted parent; its trust checks
are not bypassed to perform this migration.

CI reproduces the owner's legacy DACL for actual SYSTEM application installation,
then tests the protected signed native upgrade, customized task preservation and
student write denial. Candidate CI additionally upgrades native Windows and Mint
packages through 1.2.2, 1.2.3, 1.2.4 and 1.2.5 without changing the tool baseline.
Private signing keys remain in the existing protected signing environment.
Only new 1.2.5 assets are published; earlier builds are unpublished CI fixtures.

Owner candidate verification

Download all five release assets into a separate v1.2.5 folder on each known-good
PC. Verify the complete folder using the installed pinned worker and tag v1.2.5.
Keep both PCs at their accepted 1.2.4 version and application policy paused until
the automatic pilot plan is approved. Do not recreate writable legacy permissions
on the owner PCs; the adversarial migration tests belong on disposable CI runners.
Windows browser download warnings remain separate from Minisign verification.

Automatic installation and recovery pilot — separate approval required

Production discovery and recovery retention exclude GitHub prereleases. Merely
resuming policy while 1.2.5 is a prerelease cannot demonstrate its installation.
CI covers signed automatic installation and native failure handling, but actual
laptop acceptance remains outstanding.

With only the two known-good PCs, preserve both at 1.2.4 for a reserved 1.2.4→1.2.5
pilot. Before any release edits, obtain explicit owner approval for promoting the
accepted signed 1.2.4 release as historical (not latest) recovery source and
promoting the exact verified 1.2.5 assets as the latest stable pilot target.
Explain that GitHub stable release visibility is repository-wide even though
only the reserved PCs are resumed. Existing signed bytes must not be rebuilt or
replaced during promotion. School machines remain paused.

After approval, resume only one reserved PC at a time and use the existing
coordinated maintenance task/service. First test open-SDE deferral, then close
SDE and test the actual discovery, signed staging, native upgrade and next-run
engine. Capture maintenance outcome, native exit, application/engine identity,
baseline, settings and schedule. Verify retained signed installers using
verify-recovery, including exact current 1.2.5 and previous 1.2.4 evidence.
Pause again after each pilot. Do not kill native installers, manufacture broken
packages, delete locks or force a downgrade on the owner PCs; CI owns failure
injection. Unexpected results require protected-log diagnosis before proceeding.

Successful reserved-PC installation and recovery verification still do not
establish school-network/student-account acceptance or approve classroom resume.
Record those remaining checks explicitly before broader rollout. If stable
promotion is not approved, stop at signed candidate verification and CI evidence.

SDE 1.2.4 — self-update UAT candidate

SDE 1.2.4 correction candidate

This is an unaccepted prerelease for the Linux schedule-history finding from
owner UAT of 1.2.3. Existing 1.2.2/1.2.3 releases remain immutable, and stable
1.2.1 remains unchanged. Application and maintenance engine identify as 1.2.4;
the applied development-tool baseline remains 1.2.1. Production discovery ignores
prereleases. Keep application installation paused during manual testing.

On October 12, both owner PCs completed protected tool maintenance successfully
with SDE installation paused. Windows' Schedule page reported that success.
Mint's app receipt correctly reported the completed attempt, but the schedule
summary showed an older timer trigger and an unavailable result because systemd
no longer supplied service execution timestamps. The journal independently
confirmed the successful Mint attempt. These results do not accept automatic
installation, signed recovery, or classroom rollout.

Correction

Two root-only systemd hooks persist the latest service start and completion in a
bounded, non-secret, student-readable maintenance-history receipt. Starting an
attempt replaces old success with an incomplete result. The completion hook also
records launcher/startup failures; it does not rely on an older tool receipt.
The read-only Schedule inspector uses this protected record when appropriate,
rejects linked/writable/invalid history, and defers to evidence of a newer service
invocation or timer trigger. Missing history never means success. Unavailable
history no longer claims that the computer restarted.

An application upgrade installs the hooks for an existing coordinated baseline
without changing timer enablement, frequency, random delay, pause policy, or the
existing schema-1 launcher. App-only and legacy uncoordinated installations do
not acquire a weekly task. Historical attempts are not fabricated: run the
existing maintenance service once after upgrading to establish new history.

Focused owner retest

1. Download the complete five-file 1.2.4 prerelease asset set into its own folder.
   Verify it with the installed pinned worker before launching an installer.
2. Close SDE and wait for native package work to finish. Manually upgrade each
   existing 1.2.3 test PC using the owner UAT procedure, with app updates paused.
   Another baseline Repair is unnecessary on these already migrated test PCs.
3. Confirm About 1.2.4, unchanged project/editor settings, preserved schedule and
   paused policy. Run existing protected maintenance with SDE closed; inspect
   independent tool success and paused app outcome.
4. On Mint, disable/stop and restore the existing timer after maintenance, as in
   the reported reproduction, then reopen SDE and refresh Schedule. The latest
   run and successful result must remain visible even if systemd drops its live
   timestamps. Reboot and refresh to check durability. Restore the timer to its
   originally enabled state and confirm its next run.
5. On Windows, confirm the Schedule page still shows the successful tool result,
   paused app outcome and preserved weekly task. Report any Windows download
   warning separately; Minisign is not Windows Authenticode signing.

CI covers absent timestamps, interrupted/newer attempts, protected-file rejection
and real systemd success followed by failure without running development tools.
Candidate CI tests native Windows and actual Mint userland upgrades through
1.2.4. Booted-laptop UAT remains required. Publish only through the protected
reviewed-main workflow with its correction option; it signs and publishes only
new 1.2.4 assets, using earlier versions solely as unpublished CI fixtures.
Signing requires the existing human environment approval. Stable promotion and
application-policy resume require separate explicit owner instructions.

SDE 1.2.3 — self-update UAT candidate

Self-update UAT candidates 1.2.2 and 1.2.3

These are unaccepted prereleases, built from the same reviewed commit with
different application version identities. Development-tool baseline versions do
not change. 1.2.2 is the test starting point; 1.2.3 is the upgrade target. Do not
promote 1.2.2 merely to make testing easier. Existing stable 1.2.1 stays unchanged.

Both versions include the implemented self-update trust, protected discovery and
staging, session/maintenance coordination, Windows/Mint native installation,
administrator pause/resume, separate application/engine/baseline status, and
retained-installer verification. New installations start paused; upgrading
preserves an existing policy. App installation does not apply a tool baseline,
create a new weekly schedule, or launch the GUI/reboot.

Each release must contain both native installers, SHA256SUMS.txt, signed
sde-update.json and sde-update.json.minisig. The protected workflow authenticates
both installers before publication. Minisign authentication is separate from
Windows Authenticode; no SmartScreen exemption is promised.

Use the owner UAT procedure. These packages support a real,
verified manual two-version upgrade while production remains paused. Production
discovery ignores them because they are prereleases. Native CI separately tests
the production installation components and deferral/failure contracts; it does
not replace Windows 11, booted Mint, or school-network acceptance.

Record findings with Codex. Acceptance and stable promotion remain pending your
explicit instructions. See migration and rollout.

SDE 1.2.2 — self-update UAT candidate

Self-update UAT candidates 1.2.2 and 1.2.3

These are unaccepted prereleases, built from the same reviewed commit with
different application version identities. Development-tool baseline versions do
not change. 1.2.2 is the test starting point; 1.2.3 is the upgrade target. Do not
promote 1.2.2 merely to make testing easier. Existing stable 1.2.1 stays unchanged.

Both versions include the implemented self-update trust, protected discovery and
staging, session/maintenance coordination, Windows/Mint native installation,
administrator pause/resume, separate application/engine/baseline status, and
retained-installer verification. New installations start paused; upgrading
preserves an existing policy. App installation does not apply a tool baseline,
create a new weekly schedule, or launch the GUI/reboot.

Each release must contain both native installers, SHA256SUMS.txt, signed
sde-update.json and sde-update.json.minisig. The protected workflow authenticates
both installers before publication. Minisign authentication is separate from
Windows Authenticode; no SmartScreen exemption is promised.

Use the owner UAT procedure. These packages support a real,
verified manual two-version upgrade while production remains paused. Production
discovery ignores them because they are prereleases. Native CI separately tests
the production installation components and deferral/failure contracts; it does
not replace Windows 11, booted Mint, or school-network acceptance.

Record findings with Codex. Acceptance and stable promotion remain pending your
explicit instructions. See migration and rollout.

Skyview Student Development Environment 1.2.1

Skyview Dev Setup 1.2.1

This release fixes Linux Mint Install and Repair stopping at the Node.js version selection step with exit 141. Scheduled updates used the same selector and receive the same correction.

The selector consumes the complete APT version listing while selecting its first Node.js 24.x candidate. Missing approved candidates and genuine package-reader failures still stop the operation. Node remains on 24.x; Python remains on 3.14.x. Regression tests cover large listings, missing candidates, and reader errors.

Includes the version-aware tool list, independent update and validation counts, read-only Schedule page with run history and maintenance logs, and About page with app information and repository/program links.

Both native installers and automated checks passed. On 2026-10-08, the project owner accepted all release checklist items and authorized merge and stable publication. PR #3 is merged. See the acceptance record and successful candidate build. The supplied Mint 22.3 installation and subsequent validation logs each show 35 passed, 0 warnings, 0 failed.

Accepted limitation: PowerShell can show identical installed/available versions when Chocolatey's package record lags behind the executable. This reporting defect remains a future correction and was accepted for this release.

Stable promotion preserves tag v1.2.1 at 40c2177c5916002db2e8da45143784b1ac6ad114 and the tested installer/checksum assets. Verify downloads against the attached SHA256SUMS.txt. Windows installers ship unsigned by project decision.

On a Mint machine that encountered the earlier failure, install this GUI package, choose Install or Repair, then Validate.

Skyview Student Development Environment 1.2.0

Skyview Dev Setup 1.2.0

This release candidate adds version-aware update status and makes scheduled maintenance visible in the GUI.

• Overview says Updates available when tools pass validation and managed updates exist. Passes, failed checks, and available updates have separate counts.
• Development tools show Ready · installed version or Update available · installed version → available version. Skipped or unavailable update checks are explicit. Versions come from installed tools or package metadata; Linux package versions can include distribution revisions.
• Windows checks the pinned Node 24 family independently of newer Node majors. Linux uses the same APT Node 24 resolver as its updater and checks the managed PyCharm release with JetBrains.
• Schedule displays the system task/timer, actual frequency, next/last run, last result, catch-up policy, managed scope, maintenance log folder, and Refresh. It is read-only and runs without elevation. Missing tasks and inaccessible history are explicit; it never treats missing history as success.
• About describes the app and Skyview Robotics, shows the app version/platform, and links to GitHub and skyviewrobotics.com in the system browser.
• Navigation, loading states, local timestamps, focus, narrow layouts, and reduced motion remain accessible.

Supported platforms: Windows 11 x64 and Linux Mint Cinnamon 22.x amd64. Node stays on 24.x; Python stays on 3.14.x. Windows installers ship unsigned by project decision.

Both native installers must pass CI before publication. Manual Windows/Mint acceptance for 1.2.0 is pending; see the feature acceptance checklist. The existing 1.1.5 manual sign-off remains historical evidence for that version. This candidate is not yet promoted to stable.

Skyview Student Development Environment 1.1.5

Skyview Dev Setup 1.1.5

Windows validation now checks the exact maintenance task through Task Scheduler and reports missing, disabled, inaccessible and other query failures separately. Previously, validation suppressed task-query errors and showed a generic "Weekly maintenance enabled" failure even after Repair successfully registered the task.

Install and Repair now set explicit permissions on the Skyview-managed maintenance task: SYSTEM and administrators retain full control; normal users receive read access so the desktop app can validate it without elevation. Read access does not grant permission to run, edit, delete or change the task's security. Other scheduled tasks are unaffected. The weekly SYSTEM schedule is retained.

The Windows backend package is 1.1.5 so the task-permission helper and revised validator are installed and copied to the maintenance directory. The Linux baseline is unchanged. The startup spinner and automatic live details from 1.1.4 remain included.

Windows CI reproduces the access-denied failure with a temporary standard account and a harmless task, applies the permission fix, checks enabled/disabled/missing results, and verifies that the account cannot execute the SYSTEM task or change its permissions. Full system provisioning then verifies the real maintenance task from a standard-user process. Machine-changing tests run only on disposable GitHub runners.

Follow the Windows installer's update/reinstall flow, relaunch Skyview Dev Setup, and run Repair once to update the existing task's permissions. Then run Validate; all installed software can be reused. Updating the application alone does not change the task.

Manual acceptance was completed on fresh Windows and Linux machines on 2026-10-07, with all checks reported as passing. This includes installation, validation, keyboard navigation, 200% scaling, Narrator/Orca, repair and data preservation, reboot, updates and maintenance. See the acceptance record for the test procedure and evidence.

Stable promotion retains the existing v1.1.5 tag at ec58ad147a938f6f596632691b3b3ce46724425b and the tested installer assets; no rebuild is required. Verify downloads against the attached SHA256SUMS.txt. Windows installers ship unsigned by project decision. Keep operating-system protections enabled.

Skyview Student Development Environment 1.1.4

Skyview Dev Setup 1.1.4

Startup validation now shows a prominent spinner and a clear message while checking installed tools. The spinner also accompanies operation progress. Reduced-motion preferences disable rotation while retaining the visible status and screen-reader announcements.

Install, Repair, Validate and Update show live details directly below their progress bar, without requiring a separate disclosure to be found or expanded. The running view brings progress and output forward, and focuses the progress status when an operation starts. Output follows new lines automatically; scrolling upward lets you read earlier output without being pulled back to the bottom. Details remain visible on the overview after completion or failure, and full logs remain available through Open log folder.

Frontend checks cover pending startup validation, streaming output, operation completion and failure, keyboard focus, desktop/mobile layouts, reduced motion and automated WCAG AA accessibility rules. Native packaging and backend checks run on disposable CI runners. This UI release retains the Windows 1.1.3 backend and its guarded Node 24 migration.

Follow the installer's update/reinstall flow and relaunch Skyview Dev Setup. This remains an unsigned mentor-testing prerelease; physical-laptop and assistive-technology acceptance testing remain required. Earlier releases remain available.

Skyview Student Development Environment 1.1.3

Skyview Dev Setup 1.1.3

Windows installation now handles existing Chocolatey-managed Node.js packages before installing the required Node 24 LTS runtime. Previously, a machine with Node 26 through nodejs/nodejs.install stopped with MSI error 1603: a later Node version was already installed. Install, Repair and managed updates share the migration policy, check package ownership, resolve the approved version before removal, and verify Node 24 afterward. Unmanaged or mismatched runtimes receive a specific remediation message. Chocolatey's dependent-package checks remain enabled.

The Windows backend package is now 1.1.3 so the new migration helper is included in both initial setup and maintenance. Download progress percentages are suppressed; status heartbeats and package results remain visible.

CI tests install the actual Node 26.1.0 MSI, migrate to Node 24.21.0 using the app's clean helper environment, retry the operation, and check the package channel and pin. The same test then runs the full Windows system setup, including the real development dependencies and maintenance configuration. These machine changes run only on disposable GitHub runners. User-profile/editor configuration and physical-laptop behavior still require acceptance testing.

Follow the Windows installer's update/reinstall flow, relaunch Skyview Dev Setup, and retry Install Development Environment. Successfully installed packages from a previous attempt are reused. Node 26 is replaced with the required Node 24; student projects and existing editor settings are preserved.

This remains an unsigned mentor-testing prerelease. Physical-laptop provisioning, reboots, maintenance and accessibility acceptance checks remain required. The Linux baseline and earlier releases remain available.

Skyview Student Development Environment 1.1.2

Skyview Robotics Student Development Environment 1.1.2 — Windows installation environment fix.

Windows

Download Skyview-Dev-Setup-Windows-x64.exe, open it, and follow the installer to update Skyview Dev Setup. If it offers to remove the previous app version before installing, follow that flow. Installed development tools and student projects are separate from the app.

Relaunch Skyview Dev Setup and retry Install Development Environment.

This fixes Chocolatey stopping at its system-cache permissions check before installing any development packages. The restricted administrator environment now includes SYSTEMDRIVE so Windows resolves the shared application-data directory correctly. Script and temporary paths use the spelling supported by PowerShell and older .NET tools. The helper still clears user environment variables and uses system-only executable/module paths; it does not relax cache permissions or disable Chocolatey's checks.

Windows CI now performs a real local Chocolatey fixture-package install/uninstall using this same environment builder. The fixture installs no development tools and runs only on the disposable GitHub runner. Another test checks Windows known-folder resolution, temporary-file operations and removal of inherited user variables.

Linux Mint

Download Skyview-Dev-Setup-LinuxMint-amd64.deb, open it, install it, then launch Skyview Development Environment Setup. Linux provisioning behavior is unchanged.

Both installers and SHA256SUMS.txt are built and verified by CI. This remains a mentor-testing prerelease, with physical-laptop package installation and UAC/PolicyKit acceptance still required. Windows installers remain unsigned. Earlier releases remain available unchanged.