AuraScan v0.7.0

AuraScan v0.7.0

Contextual Follow-Up Assistant

• Added aurascan ask, aurascan ask --latest, direct retained context and
  incident IDs, and --facts-only.
• Added interactive follow-up after foreground upgrade preflight/aftercare,
  Incident Recovery, Resolve System Findings, weekly maintenance, and Config
  Drift results.
• Existing confirmation prompts accept ? to open questions and then return to
  the unchanged decision.
• AI may select only AuraScan-owned fact, diagnostic-probe, and verified-action
  IDs. It cannot provide commands, package targets, paths, scripts, or edits.
• Requested actions are rebuilt from current local state, shown as one plan,
  and confirmed independently. Parent --yes never authorizes them.
• Sessions are bounded to eight questions, twelve provider requests, a
  60-second request timeout, and 12,000 characters per request.
• Redacted source contexts are fingerprinted and retained privately for 30 days
  or 50 records. Follow-up questions and answers are not persisted.
• Added Doctor checks and regression coverage for private storage, tampering,
  redaction, TTY/service gating, stale plans, provider failures, and workflow
  exit-code isolation.

Contextual follow-up is excluded from recovery mode, package scans, pacman
hooks, root collectors, background services, JSON output, --yes, and
--no-ai workflows in this release.

Hardware-Aware Incident Follow-Up

• Added automatic read-only hardware enrichment for questions about CPU, GPU,
  memory, OOM events, temperatures, fans, BIOS, firmware, microcode, and
  drivers.
• Added bounded CPU/RAM/mainboard/BIOS inventory, GPU and driver state, DIMM
  topology where SMBIOS permits it, hwmon and NVIDIA telemetry, memory
  pressure, and normalized current-boot hardware-error counts.
• Added installed-versus-repository checks for relevant microcode and graphics
  packages plus supported firmware-update discovery through fwupd.
• Added evidence-based Intel 13th/14th Gen desktop microcode guidance without
  treating runtime microcode as proof that motherboard firmware is current.
• Excluded serials, UUIDs, raw SPD/I2C data, raw firmware tables, and arbitrary
  files from retained and AI-visible hardware context.
• Stopped proposing persistent-service restarts for transient desktop
  application units such as app-chromium@....service.

Full-Control Repair Agent

• Added aurascan agent, retained context/incident selection, --access,
  --approval, --output-sharing, --session-timeout, and --facts-only.
• Kept guarded as the default. Optional user-shell and root-shell modes
  accept only strict, visibly previewed command objects from the foreground AI
  session.
• Added each-command, immutable whole-plan, and typed session approval
  modes, with 30-command, 40-provider-request, and session-expiry limits.
• Added a root-owned policy ceiling at /etc/aurascan/agent.conf. Root sessions
  also require the exact per-session phrase GRANT AI FULL ROOT CONTROL.
• Added a root broker with private 0600 requests, UID/process/start-time/TTY/
  context binding, short-lived capabilities, exact plan hashes, and no access
  to AI credentials.
• Added Btrfs/Snapper pre-session snapshots. Continuing without supported
  rollback requires the exact phrase CONTINUE WITHOUT ROLLBACK.
• Added redacted terminal-output sharing by default and a separate
  SHARE FULL TERMINAL OUTPUT grant for bounded raw output.
• Added private user and root audits, 30-day/50-session retention, Doctor
  checks, setup-wizard controls, /agent, /status, and /stop.
• Kept the agent foreground-only. It cannot start from JSON, noninteractive,
  --yes, hooks, root collectors, background services, or Recovery v1.

Unrestricted root mode is explicitly documented as user-authorized remote code
execution. Its commands can defeat AuraScan's own safeguards after execution
begins; snapshots and audit controls do not make that authority safe.

Recovery Image

The application and Arch package advance to v0.7.0. The separately downloadable
Recovery image remains the validated v0.6.0 hybrid BIOS/UEFI image referenced by
the packaged recovery manifest; this release does not claim that a replacement
ISO was built or revalidated.

Validation

• All 885 tests passed.
• Python compilation, strict MEDIUM+ presenter coverage, wheel-content checks,
  systemd unit verification, package metadata generation, and Git diff checks
  passed.
• A package-managed local build was installed and the KDE tray applet was
  restarted successfully.
• Live read-only hardware probing verified DIMM, GPU, sensor, driver,
  microcode, and fwupd categorization without persisting serials or UUIDs.