feat(profile): add --profile flag for isolated instances

[TimeToBuildBob]

Part of ActivityWatch/activitywatch#1399 (isolated profiles per edition/mode).

Lets prod, --testing and e.g. a Research Edition build run side by side on one machine. --profile NAME picks the instance; --testing is now an alias for --profile testing, so existing behaviour is unchanged — with no flag, and with --testing, every path is byte-identical to today.

aw-qt only launches things, so its part is deliberately small:

• Resolve + validate the profile (aw_qt/profile.py) — same rule as aw-server-rust's validate_profile: lowercase alphanumeric plus -/_, max 32 chars, so a profile is always a safe path segment.
• Export AW_PROFILE for spawned modules, so the profile propagates without threading a flag through every module's CLI.
• Profile-suffixed single-instance lockfile (aw-qt-research.lock) — otherwise the second profile is refused as "already running".
• Config section [aw-qt-<profile>], falling back to [aw-qt] when the profile has no section of its own.
• Port lookup reads the profile's own server config (config-<profile>.toml for aw-server-rust, [server-<profile>] for aw-server), mirroring aw-server-rust's config path. A custom profile with no port configured logs a warning, since it would collide with 5600.
• Tray tooltip and menu show the profile (ActivityWatch (research), "Running in profile: research"). testing keeps its existing "Running in testing mode" wording.

Not in this PR

Full data/config isolation lives in the dirs implementations — ActivityWatch/aw-server-rust#652 and its follow-up do the Rust half, the aw-core half is separate. Until those land, a custom profile isolates what aw-qt owns (lockfile, config section, port) but still shares aw-core's data dir. Nothing regresses in the meantime: without --profile, no behaviour changes at all.

Verification

• pytest tests/ — 97 passed (36 new, covering resolution/validation, suffixes, env propagation, per-profile port lookup, config-section fallback)
• mypy aw_qt — 8 errors, identical to the pre-existing master baseline (all PyQt6 QAction | None stubs in trayicon.py)
• flake8 — clean on changed files
• Manual: --help shows both flags; --profile Research and --profile research --testing fail with clear usage errors

[greptile-apps]

Greptile Summary

Adds named ActivityWatch profiles so separate editions or modes can run concurrently while preserving default and testing behavior.

• Resolves and validates profile names, exports AW_PROFILE, and assigns profile-specific lockfiles.
• Loads profile-specific aw-qt and server configuration with legacy fallbacks.
• Displays the active profile in the tray and adds focused profile/configuration tests.

Confidence Score: 5/5

The PR appears safe to merge.

No blocking failure remains.

Important Files Changed

Filename	Overview
aw_qt/profile.py	Introduces profile validation, CLI resolution helpers, environment propagation, and filename suffix generation.
aw_qt/main.py	Integrates profile resolution into startup, locking, configuration, child-module launch, and tray initialization.
aw_qt/config.py	Adds profile-specific configuration sections and server-port lookup while preserving default and testing fallbacks.
aw_qt/manager.py	Resolves server probe ports from the inherited profile when starting or reusing server modules.
aw_qt/trayicon.py	Displays the active profile in the tooltip and tray menu while retaining testing-mode wording.
tests/test_profile.py	Covers profile validation, resolution, suffixes, testing detection, and environment propagation.
tests/test_profile_config.py	Covers profile-specific server ports, server implementation filtering, and aw-qt configuration fallback.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart LR
    CLI[CLI profile options] --> Resolve[Resolve and validate profile]
    Resolve --> Env[Export AW_PROFILE]
    Resolve --> Lock[Acquire profile lock]
    Resolve --> Config[Load profile configuration]
    Config --> Port[Resolve server port]
    Env --> Manager[Start selected modules]
    Port --> Tray[Profile-aware tray and links]
    Manager --> Tray

Loading

_{Reviews (3): Last reviewed commit: "fix(profile): keep default profile on le..." | Re-trigger Greptile}

[TimeToBuildBob]

Greptile 4/5, one P1 addressed in-thread: the Rust-first port lookup vs. module-specific probe divergence is pre-existing on master and unchanged here, so it's split out as #129 rather than folded into a flag-addition PR. All CI green (ubuntu/macos/windows).

[TimeToBuildBob]

@greptileai review

[TimeToBuildBob]

Fixed the default-profile root regression in 584d626. export_profile("default") now removes AW_PROFILE instead of exporting the literal value default, so aw-core keeps the legacy bare activitywatch root. The regression test starts from AW_PROFILE=research and verifies default startup clears it. Local verification: 30 profile tests passed, mypy clean, scoped flake8 clean; Ubuntu, macOS, and Windows CI are green on the new head.

[TimeToBuildBob]

@greptileai review