Please approve the snap declaration/installation permission and automatic connection of jackmeow:dot-config-jackmeow for the jackmeow snap. Publisher: sachinewx. Candidate version: 0.2.1, core24, strict confinement, ARM64. The candidate has been validated locally and has not been uploaded.
name: jackmeow
description: Terminal chat with OpenAI-compatible services and OpenSearch exploration
snapcraft: PRIVATE; relevant declaration included below
upstream: PRIVATE
upstream-relation: upstream maintainer and snap publisher
plugs:
dot-config-jackmeow:
interface: personal-files
attributes:
write:
- $HOME/.config/jackmeow
request-type: auto-connection
reasoning: >-
Jack Meow reads its own user-edited configuration at
~/.config/jackmeow/config.toml and needs write access to create a sanitized
first-run template or migrate its previous Snap-owned configuration.
This application-owned directory provides one stable, host-editable path
shared with native installations and preserved across Snap reinstall.
Auto-connection avoids requiring a privileged manual connection command
before ordinary first-run configuration can succeed.
The request includes the required installation/declaration approval as well as the auto-connection grant. The actual snapcraft.yaml fragment is:
plugs:
dot-config-jackmeow:
interface: personal-files
write:
- $HOME/.config/jackmeow
apps:
jackmeow:
command: usr/bin/jackmeow
plugs: [network, dot-config-jackmeow]
The sole requested personal-files path is $HOME/.config/jackmeow, owned by Jack Meow. Directory write access supports private temporary files and atomic no-overwrite publication of config.toml. The app creates its directory with 0700 permissions and config with 0600; existing config is preserved. Config can contain service credentials, or refer to credentials through environment variables. Migration and CLI validation were tested to avoid exposing credential values. Saved presets remain in Snap-owned common storage. No broad home access or classic confinement is requested.
Local Ubuntu 24.04 ARM64 strict-confinement validation passed: canonical first run, read/write access, denial of an unrelated hidden directory, migration from installed revision 2, no overwrite, restart, and uninstall/reinstall preservation. Canonical-config TUI, mock networking, presets and JSONL export passed. Native Debug and Release suites passed 82/82 each; ASan/UBSan/LSan selection passed 34/34.
Fresh reinstall leaves this plug disconnected. Startup then reports the precise manual connection command. This verifies why auto-connection is requested; manual local connection is not presented as proof of Store approval.
Please grant the declaration and auto-connection for this exact application-owned path, or advise what additional evidence is required for review.
