AuraScan v0.4.0

AuraScan v0.4.0

Incident recovery and Arch-family compatibility release focused on making
system maintenance calmer, safer, and easier to act on.

Highlights

• Added aurascan incidents for bounded current-boot, previous-boot, history,
  coredump, and deterministic crash diagnostics.
• Added field-limited coredump collection that never reads core memory, process
  environments, or complete command lines.
• Added redacted, user-opened incident AI review with strict evidence/action ID
  validation and a total 12,000-character input bound.
• Added confirmed repair recipes with fresh root-side precondition checks,
  exact kernel/header version proof, manifests, bounded redacted output, and
  rollback where supported.
• Added an optional hardened previous-boot monitor and one grouped tray
  notification per boot. Package installation leaves the monitor disabled.
• Added coupled weekly incident maintenance with incremental journal/coredump
  checkpoints, a persistent randomized timer, silent clean scans, and no
  background AI or repairs.
• Added dynamic tray states for overdue maintenance, actionable findings, and
  critical incidents, refreshed without restarting the applet.
• Replaced overlapping incident tray entries with one Resolve System
  Findings workflow. It applies verified repairs when available or clearly
  acknowledges reviewed historical evidence so the tray returns to normal.
• Added live stage and elapsed-time feedback to interactive incident scans so
  journal collection, coredump analysis, repair verification, and AI correlation
  no longer leave the terminal looking idle.
• Added package-manager handoff boundaries, repository-transition explanations,
  and a post-upgrade mirror-fallback summary gated by deterministic installed
  version verification. AI is instructed not to mislabel repository metadata as
  an AuraScan error or require manual conflict resolution without concrete evidence.
• Removed the redundant Config Drift Assistant tray entry; upgrade runs still
  invoke config-drift handling automatically, and the standalone CLI remains.
• Removed AuraScan Doctor from the routine tray menu while retaining
  aurascan doctor as the installation and configuration troubleshooting CLI.
• Removed the redundant Dry-run Preflight tray action because the normal
  upgrade action always runs preflight; the report-only CLI remains available.
• Fixed installed-wizard hook discovery so it recognizes the release-safe
  /usr/share/libalpm/hooks/aurascan.hook and does not prompt for a redundant
  local override or resolve a template through Python's packaging module.
• Distinguished NVIDIA NV_ERR_NO_MEMORY allocation failures from confirmed
  kernel/systemd OOM-kill evidence and tightened AI package-causation guidance.
• Added wizard and Doctor coverage for monitoring, journal/coredump access,
  repair tools, private storage, and tray notification readiness.

Package Path

The tagged Arch package installs these additional assets:

• /usr/lib/systemd/system/aurascan-incident-monitor.service
• /usr/lib/systemd/system/aurascan-incident-maintenance.service
• /usr/lib/systemd/system/aurascan-incident-maintenance.timer
• /usr/lib/tmpfiles.d/aurascan-incidents.conf

The package must not enable or start either service or the timer. Users opt in through
aurascan init --enable-incident-monitor.

Safety Notes

The boot and weekly monitors have no network access, make no AI requests, and
never apply repairs. AI cannot generate executable actions. Privileged recipes are rebuilt
from trusted current state and revalidated as root. AuraScan does not automate
filesystem repair, partition or bootloader changes, authentication policy,
firmware operations, user-data deletion, AUR rebuilds, or rebooting.