Skip to content

P01: Persist scoped rail diagnostics through the existing logger #3092

Closed

Description

@mblua

Parent: #3083. Phase P01, design-bearing. Owner: ac-dev-rust-v5. No dependencies.

Outcome

Provide an additive append_rail_diagnostic command shared by Tauri and Web dispatch. Each valid enabled rail diagnostic record goes to the existing backend logger as one bounded line; preserve filters, redaction, append/rotation and existing APIs.

Scope

Modify only src-tauri/src/commands/config.rs, src-tauri/src/web/commands.rs, src-tauri/src/lib.rs and test-only code in src-tauri/src/logging.rs.
Use the approved Option boundary, fixed private errors and shared typed validation/emission seam. No logger/dependency/setting, global logger test mutation, GUI action or version bump.

Acceptance and verification

Prove production validation/emission through a local real gate/formatter to an actual temporary log file. Cover Debug/Trace, Info/invalid negatives, second append, rotation, Tauri/Web parity and bounded private payloads. Run approved Rust checks/integration guards and structural PRE/POST evidence; shipper owns compilation.
No claim of fsync, loss-free shutdown, native click reproduction or original bug repair.

Frozen specification

Shared canonical plan root: D:/0_repos/AgentsCommander_iac/.ac/plans/3083-rail-click-diagnostics/
Master plan-v3-rail-click-diagnostics.md: 3C05355B89CE4D0EBE882EABC9130884189BB3747CBE1EAE99901D3653B479BC
Index v3/epic.md: D81C50B661E439AF8582C4D2666E8390069172BB53E74C04157765ED5D8077ED
Sole cold-start phase specification v3-P01-backend.md:
BADDB49D18EE497D56761D54B637C7FC689E2219620CF98836818BAF52EE8A00
All five exact-version participants approved in round3; execution identity/branch/base are recorded separately by coordinator. This issue does not close the parent.

Activity

  1. added a commit that references this issue on Oct 18, 2026
  2. mblua commented on Oct 18, 2026

    @mblua
    OwnerAuthor

    Delivered backend phase P01 through PR #3094, merged at 9813d6a59ec67e67905331fd492ec57c63e2024b. This child is CLOSED; parent #3083 remains open for frontend phase #3093.

    The shared validated Tauri/Web ingress now emits scoped Debug records to the existing logger. Six focused tests passed, including actual-file gate/append/rotation proof; locked all-targets check and all three layering guards passed (1/5/3 tests). Both independent code/positive-proof reviewers PASS. Rust SCC member sets and module arcs unchanged.

    All triggered CI succeeded on reviewed head bdc8a018829c3085061f3530570cc556a426971f, including Windows regression, Linux clippy, format, debt and Sonar. Full-tier jobs were not selected (ci-tier run3401/full=false); their skips are explained by workflow conditions. Incoming main delta was unrelated profile TypeScript metadata/tests, documented on the PR. Initial local linker failure is preserved; the single permitted continuation passed with repository-confined process-only build/temp outputs, without changing source/global build configuration or establishing the old failure's cause.

    Local repository is clean on main == origin/main == 9813d6a59ec67e67905331fd492ec57c63e2024b; merged branch removed locally/remotely. No packaged build requested or produced, no GUI/input test or installation. Frontend logging is not enabled until P02 lands and the app is updated. Evidence remains in room25 room-shared/3092-P01/ and canonical plan execution receipts.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions