rcpanel 0.2.0 - native OpenBSD acceptance checklist

Status: these are tests to run, not a claim that native acceptance passed.
Use a disposable OpenBSD 7.8 VM with console access, a snapshot, and test data.
Do not run package removal, kernel changes, cron experiments, or destructive
native-program checks on a production machine. Record actual results and any
unsupported commands or ownership constraints; do not replace failure with a
simulated success.

System/architecture: __________________  Python: __________________
Terminal: ____________________________  Date: ____________________
Tester: _________________________________________________________

1. Install, upgrade, and command-line output

   Run the unittest suite with the intended installed Python. Install 0.2.0
   with that interpreter; verify --version, --help, and man 8 rcpanel. On a VM
   with 0.1.0 installed, confirm the same launcher now runs 0.2.0 and the old
   version directory remains. Reinstall identical code successfully; reject
   changed code under the same version. Verify the launcher uses -I and the
   intended exact interpreter. Confirm privileged actions require root and
   explicitly invoked native programs retain the account's ordinary permissions.

   Exercise --map, --map network, --programs, --programs ssh, --packages, and
   --status without curses. Compare live output to the VM. Exercise all with
   --demo; native host inventories/services/package records must not be read
   or changed by simulated administration. EDITOR remains a real editor on a
   temporary file. Verify live mode refuses a non-OpenBSD host.

   Outcome: _____________________________________________________

2. Map, numeric navigation, and terminal restoration

   Walk all 12 categories; compare the static listing to SYSTEM-MAP.txt. Confirm 8/2
   move, 5/6 open, 4 returns, and 0 returns to the top map. Exercise arrows,
   j/k, Enter, Escape, Home/End, and paging. Return to long menus and verify
   each retains its own selection and scroll position. Search with /.

   Jump with : to 3*1*1 and 3*1*1#; both must only open the endpoint, with no
   command executed. Try malformed and missing codes. Type digits including
   0/2/4/5/6/8 into text fields; they must remain data. In a text viewer,
   Left/Right must scroll long lines, while Escape/4 returns. Resize through
   small and normal sizes in menus, fields, forms, and viewers. Exit normally
   and through an error; terminal input/echo must be restored.

   Outcome: _____________________________________________________

3. Program inventory, manuals, and exact reports

   Inspect all ten inventory groups, including base/local libexec, X11, and
   games where installed. Compare executable paths to the VM's files. Check
   duplicate basenames display distinct full paths. Missing optional groups,
   missing manuals, access failures, and truncated inventory must remain clear.
   Confirm inventory itself does not launch discovered executables.

   Read a synopsis and full manual. Review a harmless command with quoted
   arguments and a specific existing absolute working directory. Cancel once,
   then run it and confirm exact argv/cwd and terminal restoration. Ensure
   invalid quoting fails before launch and shell substitutions stay literal.
   Refresh/remove a disposable executable between review and run; reject a
   stale selection. Test unsafe executable ownership in an isolated directory.

   Run available fixed reports and compare their results to the displayed
   native commands, especially netstat -R, smtpctl show status/queue/stats,
   swapctl -lk, vmctl status, mount without arguments, and syspatch -c/-l.
   Confirm no report changes state. Missing daemons, privileges, hardware,
   or tools must show native failure instead of invented empty success.

   Outcome: _____________________________________________________

4. Runtime kernel settings and persistent file

   Compare the browsable hierarchy with sysctl -a. Search, refresh, and read
   individual names; inspect a multiline value such as kern.version. Using
   an expendable VM setting, record the old value, review a runtime change,
   and compare native sysctl output. Confirm /etc/sysctl.conf is unchanged.
   Restore the original runtime value explicitly. Attempt a documented
   read-only value and an invalid assignment; display the native failures.
   Reject writes as an ordinary account.

   Separately stage, review, and cancel an edit to /etc/sysctl.conf. If testing
   installation, confirm no sysctl command applies it automatically. Test boot
   persistence only after recording a console recovery method and VM snapshot.

   Outcome: _____________________________________________________

5. Package information and preview/confirmation

   Confirm /etc/installurl is correct for the disposable VM. Compare installed
   names/comments with pkg_info -A, manual-install tags with pkg_info -m, and
   details/files/dependents/messages with their displayed native commands.
   Search a harmless package by plain fragment and select an exact result.
   Check malformed names, paths, URLs, and option-like queries are rejected.
   Run a dry run, inspect the native output and exact command, then cancel;
   no package change may be applied. Preview requires root.

   In this VM only, exercise install, single-package update, remove, upgrade
   all, and unused-dependency removal where applicable. Choose disposable
   packages and retain the panel's Python interpreter. Compare every outcome
   to native inventory and inspect package messages. A failed or truncated
   preview must not offer application. A used plan must not be reusable.

   Change installed inventory between preview and apply from another session;
   require a new preview. Also change a disposable package's manual/automatic
   tag with native pkg_add -m/-a, without changing its name; require a new
   preview. Try two panel instances; package operation overlap must be refused.
   Native external-client locks remain authoritative; do not claim the preview
   freezes repository contents or every package DB record.

   Outcome: _____________________________________________________

6. Package progress, failures, and disconnect handling

   Observe progress during a real test-VM package operation. Verify native
   output/exit status and final inventory. Confirm there is no automatic
   mutation timeout. During a disposable operation, Ctrl+C must not abandon
   the package writer. Send SIGHUP or SIGTERM while it runs; the panel must
   wait for completion before closing. Reconnect and inspect the actual state.

   Exercise an unreachable mirror or unavailable package without force flags.
   Show the failure and require fresh review; no retry or rollback is automatic.
   Do not forcibly interrupt a package writer merely to satisfy this checklist.
   Test slow/large-output and observer-error paths with the portable harmless
   child-process tests, not by corrupting a package database. Confirm inherited
   PKG_PATH/PKG_DBDIR do not redirect panel package operations.

   Outcome: _____________________________________________________

7. Editor, configuration roots, validation, and recovery

   Carry EDITOR through doas explicitly. Edit a staged file and independently
   check the live contents remain unchanged before installation. Inspect the
   full diff and cancel. Repeat with malformed EDITOR, missing executable,
   nonzero editor exit, and Ctrl+C inside the editor. Use a wait option for
   editors that detach. Confirm terminal restoration and no implicit install.

   Exercise supported root-owned files below /etc, /var/unbound/etc, and
   /var/nsd/etc. Record refusal of unsupported daemon-owned directories/files;
   do not weaken ownership to hide it. Compare backup bytes, mode 0600, private
   directory mode 0700, and preserved installed metadata. Test a live-file
   conflict, competing panel lock, and restore through the target's menu.

   Exercise all available registered validators, including both DNS checkers,
   with valid and invalid disposable candidates. No validator should apply
   configuration. Check relative includes and report files without validators.
   Use an alternate daemon configuration path explicitly rather than assuming
   the catalog default is active. Keep includes stable during a transaction.

   In the VM only, test a harmless temporary /etc/crontab entry and confirm the
   effect notice explains automatic reload. Remove it and restore the original
   file afterward. Verify a file install issues no rcctl action while acknowledging
   that a native reader can use new contents immediately or on its next read.

   Outcome: _____________________________________________________

8. Existing services and structured forms

   Compare service Boot/Now states with rcctl ls all/on/started and get for a
   base daemon, package daemon, disabled daemon, and boot-only setting. Confirm
   disable does not stop a daemon and stop does not disable startup. Check
   rc.conf.local backup before enable/disable/flag changes. Show actual nonzero
   results for unsupported reload/configtest actions. Use a disposable slow
   rc.d test script for timeout output; refresh state and verify no retry.

   Generate the default HTTP configuration, validate it, supply test content
   in /var/www/htdocs, explicitly enable/start httpd, and test loopback port
   8080. Exercise listing off/on. Add an unfamiliar comment and verify the form
   refuses silent adoption; test explicit replacement and typed confirmation.

   Save the original smtpd.conf. Validate both local mbox/Maildir variants and
   test delivery to a disposable account. Check lo0 binding and outbound-rule
   off/on behavior; no public listener or IMAP setup should be implied. Restore
   the test machine's original files and service state when finished.

   Outcome: _____________________________________________________

Acceptance decision and unresolved issues:

_________________________________________________________________
_________________________________________________________________
_________________________________________________________________
