[ { "productId": "a-shell", "storyId": "agent-pr-analysis", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "a-Shell is a mobile terminal emulator/shell environment, not an AI agent or code-review platform; there is no evidence of AI agent integration or PR analysis capability, and this is a category mismatch rather than a missing feature.", "evidenceIds": [] }, { "productId": "a-shell", "storyId": "agentic-agent-docs", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "Probe of llms.txt returns 404 and no agent-oriented docs or API spec are found anywhere in the evidence pack; a-Shell provides only standard shell/vim/help docs.", "evidenceIds": [ "a-shell-probe-1", "a-shell-probe-2", "a-shell-gh-6" ] }, { "productId": "a-shell", "storyId": "agentic-ai-insights", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "a-Shell is a terminal/shell app for iOS providing Unix commands, Python, Vim, and Shortcuts integration, but no evidence shows any AI-generated insights, suggestions, or data analysis features.", "evidenceIds": [] }, { "productId": "a-shell", "storyId": "agentic-autonomous-automation", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "a-Shell is an iOS terminal app with no evidence of background execution, scheduling, or autonomous automation capability—Shortcuts integration allows manual triggering but not persistent background automation, and iOS sandboxing generally prevents apps like this from running unattended tasks.", "evidenceIds": [] }, { "productId": "a-shell", "storyId": "agentic-builtin-assistant", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "a-Shell is a terminal/shell app for iOS with Unix commands, Python, Vim, etc., but no evidence anywhere in the pack of a built-in AI assistant or any AI delegation capability.", "evidenceIds": [] }, { "productId": "a-shell", "storyId": "agentic-headless", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "a-Shell is an iOS-only interactive terminal app with no headless/CI execution mode or server component; running it in automated CI pipelines is outside its product category as a touch-device app shell.", "evidenceIds": [] }, { "productId": "a-shell", "storyId": "agentic-mcp-client", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence a-Shell supports MCP server integration; it is a mobile terminal/shell app with no mention of MCP protocol or plugin tool-use capability.", "evidenceIds": [] }, { "productId": "a-shell", "storyId": "agentic-mcp-server", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "a-Shell is a mobile terminal/shell app, not an AI agent or a service exposing tools; MCP server connectivity is not a relevant axis for this product category and no evidence suggests otherwise.", "evidenceIds": [] }, { "productId": "a-shell", "storyId": "agentic-nl-commands", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "a-Shell is a traditional command-line shell requiring exact command syntax (e.g. clang, vim, pip install, config, bookmark); there is no evidence of natural-language command parsing or AI-native interaction, and llms.txt/openapi probes returned 404.", "evidenceIds": [ "a-shell-gh-6", "a-shell-probe-1", "a-shell-probe-2" ] }, { "productId": "a-shell", "storyId": "agentic-official-cli", "verdict": "partial", "quality": 4, "confidence": "low", "rationale": "a-Shell is itself a full command-line environment on iOS with many built-in commands and Apple Shortcuts integration that lets users script and automate shell tasks, which could be leveraged by an AI-driven automation. However, there is no evidence of any AI-specific CLI features, agent APIs, or documented AI-native workflow support beyond generic shell scripting/Shortcuts. Missing for 10: explicit AI-agent integration, documented programmatic/automation API beyond Shortcuts, any mention of AI-native use cases.", "evidenceIds": [ "a-shell-gh-4", "a-shell-gh-6", "a-shell-docs-2" ] }, { "productId": "a-shell", "storyId": "agentic-public-api", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "a-Shell offers Apple Shortcuts integration and a CLI command set, but there is no documented public API (REST/OpenAPI/SDK) for programmatic control; explicit probes for llms.txt and OpenAPI specs both returned 404.", "evidenceIds": [ "a-shell-probe-1", "a-shell-probe-2", "a-shell-gh-4" ] }, { "productId": "a-shell", "storyId": "agentic-scoped-keys", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "a-Shell is a local iOS terminal/shell app, not an identity/credential-issuing platform or agent-management service; scoped API credential issuance for agents is outside its product category.", "evidenceIds": [] }, { "productId": "a-shell", "storyId": "agentic-sdks", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "a-Shell is a mobile terminal/shell app, not a platform offering an AI or developer SDK for building against; this axis is a category error for this product type.", "evidenceIds": [] }, { "productId": "a-shell", "storyId": "agentic-webhooks", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "a-Shell is a local iOS terminal/shell app; webhook subscription is a server/integration-side capability entirely outside its product category, not a feature a shell app would expose.", "evidenceIds": [] }, { "productId": "a-shell", "storyId": "ai-commit-message-generation", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "a-Shell is a terminal app for iOS; no evidence of any git integration, AI features, or commit message generation. This capability is plausible for a shell tool but no evidence exists.", "evidenceIds": [] }, { "productId": "a-shell", "storyId": "ai-repository-agent-actions", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "a-Shell is an iOS terminal app with git-like commands and vim available, but there is no evidence of any AI agent integration, conversational control, or automation for browsing/searching/editing/committing/pulling/pushing via an AI agent — the evidence only covers manual shell usage, Shortcuts, and UI features.", "evidenceIds": [] }, { "productId": "a-shell", "storyId": "amend-undo-commits", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence a-Shell provides git commit-amend/undo capabilities; the evidence pack covers only shell/terminal features (vim, config, bookmarks, pip) with no mention of git integration or commit history editing.", "evidenceIds": [] }, { "productId": "a-shell", "storyId": "api-interactive-docs", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "a-Shell is a mobile terminal app with a `help` command listing built-ins, but there's no evidence of an interactive API reference with runnable examples; probes for llms.txt and OpenAPI specs both returned 404.", "evidenceIds": [ "a-shell-probe-1", "a-shell-probe-2", "a-shell-gh-6" ] }, { "productId": "a-shell", "storyId": "api-machine-spec", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "a-Shell is a terminal app with no API surface, and probes for OpenAPI/Swagger specs and llms.txt all returned 404, confirming no machine-readable API spec is published.", "evidenceIds": [ "a-shell-probe-1", "a-shell-probe-2" ] }, { "productId": "a-shell", "storyId": "api-sandbox", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "a-Shell is a local iOS terminal/shell app, not a service or agent platform with a production/sandbox data distinction; the concept of testing against a sandboxed environment separate from production data does not apply to this product category.", "evidenceIds": [] }, { "productId": "a-shell", "storyId": "api-versioning-policy", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "a-Shell is an iOS terminal/shell app, not an API-based platform; versioned APIs and deprecation policies are not a relevant axis for this product category.", "evidenceIds": [] }, { "productId": "a-shell", "storyId": "assign-issue-to-agent", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "a-Shell is a terminal/shell app for iOS running Unix commands locally; it has no concept of issue tracking, AI coding agents, or pull request workflows — this axis is a category error for this product type.", "evidenceIds": [] }, { "productId": "a-shell", "storyId": "automation-bulk-operations", "verdict": "partial", "quality": 3, "confidence": "low", "rationale": "a-Shell is a full Unix-like shell environment and its Shortcuts integration is described as enabling users to 'download, process and release files using a-Shell commands,' implying scripting-based batch workflows, but no evidence explicitly documents loop constructs, xargs, or batch file processing across many items. Missing for 10: explicit documentation of scripting/looping over multiple files, examples of bulk file processing, independent corroboration of batch workflows.", "evidenceIds": [ "a-shell-gh-4", "a-shell-gh-6" ] }, { "productId": "a-shell", "storyId": "automation-rules-engine", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "a-Shell is an iOS terminal app; evidence shows shell commands, Shortcuts integration, and window management, but no rule-based automation engine (triggers/conditions/actions on events) is documented anywhere in the pack.", "evidenceIds": [] }, { "productId": "a-shell", "storyId": "automation-scheduled-jobs", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence of any cron-like scheduler or recurring job/workflow mechanism in a-Shell; Shortcuts integration allows triggering commands but no scheduling capability is documented. This is an applicable axis for a shell/terminal app, but no supporting evidence exists.", "evidenceIds": [] }, { "productId": "a-shell", "storyId": "automation-versioned-workflows", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence of any versioning, review, or rollback mechanism for automations/scripts; a-Shell offers command history, bookmarks, and Shortcuts integration but nothing about tracking changes or reverting automation scripts.", "evidenceIds": [] }, { "productId": "a-shell", "storyId": "biometric-connection-auth", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence that a-Shell supports biometric authentication (Face ID/Touch ID) for securing remote connections such as SSH; the docs cover unrelated features like compiling, editing, and shell commands.", "evidenceIds": [] }, { "productId": "a-shell", "storyId": "broadcast-commands", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "a-Shell supports multiple independent windows each with their own context (a-shell-gh-1), but there is no evidence of any mechanism to group sessions and broadcast a single command to all of them simultaneously.", "evidenceIds": [ "a-shell-gh-1" ] }, { "productId": "a-shell", "storyId": "code-search-navigation", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "The evidence pack shows a-Shell as an iOS terminal app with grep, help search, and vim, but no evidence of dedicated fuzzy-matching code search, filters, or regex-based code navigation tooling like fzf, ripgrep, or ctags integration.", "evidenceIds": [ "a-shell-gh-6", "a-shell-docs-3" ] }, { "productId": "a-shell", "storyId": "conversational-repo-agent", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "a-Shell is a terminal/shell app for iOS with Unix commands, editors, and scripting; it has no AI agent conversational feature or repository/PR insight capability, making this an out-of-category axis rather than a missing feature.", "evidenceIds": [] }, { "productId": "a-shell", "storyId": "credential-vault-storage", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "a-Shell is a local iOS terminal/shell app, not a credential/secrets management or vault product; no evidence relates to secure credential storage or multi-host referencing, making this axis a category error for this product type.", "evidenceIds": [] }, { "productId": "a-shell", "storyId": "cross-app-file-access", "verdict": "full", "quality": 7, "confidence": "medium", "rationale": "a-Shell explicitly supports accessing other apps' sandboxed directories via the `pickFolder` command using iOS 13's app sandbox access API, plus bookmarking directories for repeated use, enabling developers to work with files/repos across app sandboxes directly from the shell. Missing for 10: no explicit mention of git/repository workflows using this feature, and no independent/hands-on corroboration of pickFolder working reliably in practice.", "evidenceIds": [ "a-shell-gh-5", "a-shell-gh-3" ] }, { "productId": "a-shell", "storyId": "customizable-terminal-appearance", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "The `config` command explicitly supports changing font, font size, background color, text color, and cursor color/shape (a-shell-gh-2), directly matching the story's customization request. However, there is no documented evidence that these settings persist across sessions/app restarts, and community feedback (unrelated HN comments) doesn't corroborate the persistence or usability of these settings. missing for 10: explicit confirmation that config changes persist across sessions, independent/hands-on corroboration of the customization workflow.", "evidenceIds": [ "a-shell-gh-2" ] }, { "productId": "a-shell", "storyId": "direct-p2p-connection", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "The evidence pack contains no mention of SSH, SFTP, or any direct server-connection capability for a-Shell; it only covers compilation, Python packages, Vim, window management, Shortcuts integration, and accessibility. Since a terminal app plausibly could offer direct server connectivity, the axis applies, but no evidence documents it here.", "evidenceIds": [] }, { "productId": "a-shell", "storyId": "exit-node-routing", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "a-Shell is an iOS terminal/shell app for running commands and scripts locally; VPN/exit-node network routing is entirely outside its category and not a feature space it addresses.", "evidenceIds": [] }, { "productId": "a-shell", "storyId": "file-transfer-scp-sftp", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence pack item mentions scp, sftp, ssh key configuration, or remote file transfer capability in a-Shell; documentation covers compilers, Python packages, Vim, bookmarks, Shortcuts, and accessibility but nothing about SSH-based file transfer.", "evidenceIds": [] }, { "productId": "a-shell", "storyId": "git-clone-protocols", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "No evidence in the pack mentions git clone or any git-related commands/protocols supported by a-Shell; the docs focus on compiling, Python, Vim, and shell UI features.", "evidenceIds": [] }, { "productId": "a-shell", "storyId": "git-commit-graph", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence a-Shell provides any git commit graph visualization capability; the product is a terminal/shell app for iOS with no mentioned git tooling or graph UI.", "evidenceIds": [] }, { "productId": "a-shell", "storyId": "git-commit-push", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence pack mentions git commands or git functionality at all in a-Shell; only Vim, compilers, Python, Shortcuts, and terminal features are documented, with no reference to committing or pushing code.", "evidenceIds": [] }, { "productId": "a-shell", "storyId": "git-commit-signing", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence of GPG or SSH commit-signing support in a-Shell's documentation, GitHub README, or community discussion; the axis applies since a-Shell provides git and shell tooling but no signing capability is documented.", "evidenceIds": [] }, { "productId": "a-shell", "storyId": "git-interactive-rebase", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "a-Shell is an iOS terminal app with basic Unix commands and no evidence of git integration, let alone interactive rebase, commit editing, or history rewriting tools; no mention of git at all in the evidence pack.", "evidenceIds": [] }, { "productId": "a-shell", "storyId": "git-merge-conflict-resolution", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "a-Shell is a terminal app for iOS with basic commands, Vim, and compilers; no evidence of any merge-conflict resolution tool or git integration beyond generic shell usage.", "evidenceIds": [] }, { "productId": "a-shell", "storyId": "git-pull-request-creation", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence a-Shell offers any Git hosting platform integration (e.g., GitHub/GitLab PR creation, gh CLI) — only generic shell, editor, and Shortcuts features are documented.", "evidenceIds": [] }, { "productId": "a-shell", "storyId": "git-pull-request-review", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "a-Shell is a terminal/shell app for iOS with git-like command-line tools, but the evidence pack shows no PR review functionality, no GitHub/GitLab integration for reviewing diffs, comments, or approvals from mobile. Nothing indicates a UI or workflow for browsing/reviewing pull requests.", "evidenceIds": [] }, { "productId": "a-shell", "storyId": "git-stash", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence a-Shell includes git stash/unstash or any git functionality at all; documentation covers only shell tools like vim, clang, pip, config, bookmarks etc.", "evidenceIds": [] }, { "productId": "a-shell", "storyId": "git-submodules", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence pack item mentions git or git submodules at all; a-Shell documentation covers compiling, Python, Vim, window management, and Shortcuts but never git functionality.", "evidenceIds": [] }, { "productId": "a-shell", "storyId": "host-sync-across-devices", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence of any host/connection management feature, let alone cross-device syncing of saved hosts or settings; a-Shell is a local iOS terminal app with no mentioned cloud sync capability for connection profiles.", "evidenceIds": [] }, { "productId": "a-shell", "storyId": "inline-editor-lint", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "a-Shell ships Vim for file editing and explicitly documents running syntax checkers via vim-lsp/ALE, plus compilers (clang) for building/checking C/C++ code. However, evidence lacks detail on lint checker installation/setup specifics, dedicated linters for other languages, or hands-on confirmation of this workflow succeeding. missing for 10: independent/hands-on verification of lint checker setup, broader language linting support beyond vim-lsp/ALE mention.", "evidenceIds": [ "a-shell-docs-3", "a-shell-docs-1" ] }, { "productId": "a-shell", "storyId": "local-unix-commands", "verdict": "partial", "quality": 4, "confidence": "low", "rationale": "The evidence confirms a-Shell is a genuine command-line environment (help/help -l lists commands, and the example 'help -l | grep command' implies grep is a working built-in), and it supports compiling/running code and pip installs, suggesting a real UNIX-like command set. However, the pack never explicitly documents ls, cat, tar, or curl as available commands. Missing for 10: explicit documentation or example usage of ls, cat, tar, and curl, and independent confirmation that these specific commands run natively.", "evidenceIds": [ "a-shell-gh-6", "a-shell-docs-1", "a-shell-docs-2" ] }, { "productId": "a-shell", "storyId": "manage-cloud-agent-tasks", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "a-Shell is a local iOS terminal/shell app for running Unix commands and scripting on-device; it has no concept of cloud-based coding agents or task tracking, making this axis a category error for this product type.", "evidenceIds": [] }, { "productId": "a-shell", "storyId": "mesh-vpn-access", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "a-Shell is an iOS terminal/shell emulator app, not an infrastructure access or networking security tool; there is no mention of Kubernetes, VPN, zero-trust access, or secure infrastructure connectivity in its feature set.", "evidenceIds": [] }, { "productId": "a-shell", "storyId": "multi-session-management", "verdict": "full", "quality": 8, "confidence": "high", "rationale": "First-party GitHub docs confirm each window (multiple terminal sessions) has its own context, appearance, command history, and current directory, with `newWindow` to open additional sessions and `config` to customize appearance per session. Missing for 10: independent hands-on corroboration specifically of multi-window session isolation (community comments are about an unrelated web demo/HN thread, not this feature).", "evidenceIds": [ "a-shell-gh-1", "a-shell-gh-2" ] }, { "productId": "a-shell", "storyId": "nl-to-shell-command", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence a-Shell offers natural-language-to-command generation; it's a traditional shell/terminal app for iOS with no AI or NLP command-generation feature mentioned anywhere in docs, GitHub, or community posts.", "evidenceIds": [] }, { "productId": "a-shell", "storyId": "openness-api-parity", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "a-Shell is a mobile terminal app with no external API surface at all; the story presumes an API/UI parity model that doesn't apply to this product category.", "evidenceIds": [] }, { "productId": "a-shell", "storyId": "openness-full-export", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "a-Shell's evidence pack shows it operates on files, config, and bookmarks, but there is no documentation or claim about an explicit data export mechanism, open-format guarantee, or ability to migrate history/config/bookmarks out of the app. The probes for llms.txt/openapi also returned 404s, showing no additional documentation on this front. Missing for 10: any statement on export formats, data portability tools, or guarantees that user data (history, bookmarks, config) isn't locked into a-Shell-specific formats.", "evidenceIds": [ "a-shell-gh-1", "a-shell-gh-3", "a-shell-probe-1", "a-shell-probe-2" ] }, { "productId": "a-shell", "storyId": "openness-open-license", "verdict": "partial", "quality": 4, "confidence": "low", "rationale": "The evidence confirms a-Shell's source lives in a public GitHub repository (holzschu/a-shell) with visible commands, structure, and documentation, implying the code is readable/inspectable. However, no evidence pack item cites an explicit open-source license (e.g., MIT, BSD, GPL) or license file. missing for 10: explicit license text/name, license badge or LICENSE file citation, confirmation of redistribution/modification rights.", "evidenceIds": [ "a-shell-gh-1", "a-shell-gh-6" ] }, { "productId": "a-shell", "storyId": "openness-self-host", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "a-Shell is a local iOS terminal app, not a hosted service with a server-side 'core product' component that could be self-hosted; the self-hosting axis is designed for SaaS/cloud offerings and doesn't map onto a client-side mobile app architecture.", "evidenceIds": [] }, { "productId": "a-shell", "storyId": "privacy-data-residency", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "a-Shell is a local iOS terminal app that runs entirely on-device with no cloud service or data storage backend, so data residency/region selection is not an applicable axis for this product type.", "evidenceIds": [] }, { "productId": "a-shell", "storyId": "privacy-no-training", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "a-Shell is a local iOS terminal/shell app with no AI model training or cloud data usage component; the story about preventing data use for AI training is a category error for this product type.", "evidenceIds": [] }, { "productId": "a-shell", "storyId": "privacy-retention-controls", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "a-Shell is a local iOS terminal/shell app that runs entirely on-device with no cloud data collection or AI service backend; concepts like 'data retention and deletion controls' for AI-native privacy posture don't apply since there's no server-side data store to manage.", "evidenceIds": [] }, { "productId": "a-shell", "storyId": "privacy-telemetry-optout", "verdict": "na", "quality": 0, "confidence": "low", "rationale": "a-Shell is a local iOS terminal app with no mention of telemetry or network tracking in its evidence; the story presupposes a cloud/AI service with a tracking mechanism to opt out of, which does not apply to this offline shell utility.", "evidenceIds": [] }, { "productId": "a-shell", "storyId": "python-package-install", "verdict": "full", "quality": 7, "confidence": "medium", "rationale": "a-Shell's official docs explicitly state pip install works for pure-Python packages directly on-device, matching the story exactly. missing for 10: independent hands-on confirmation of pip install working, and details on limitations (e.g. packages requiring compiled extensions).", "evidenceIds": [ "a-shell-docs-2" ] }, { "productId": "a-shell", "storyId": "rendered-file-live-preview", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "a-Shell is a terminal/shell app with vim editing and command-line tools, but there is no evidence of any Markdown/HTML preview or live-reload rendering capability.", "evidenceIds": [ "a-shell-docs-3", "a-shell-gh-6" ] }, { "productId": "a-shell", "storyId": "secure-enclave-ssh-keys", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence in the pack mentions SSH key storage, hardware-backed secure enclave, or biometric protection for a-Shell; the docs focus on shell commands, package installation, and appearance customization. This is a plausible security axis for a terminal app dealing with SSH, but absence of any supporting evidence means it must be marked none.", "evidenceIds": [] }, { "productId": "a-shell", "storyId": "session-persistence-mosh", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "a-Shell is a local iOS terminal app running commands on-device, not an SSH client maintaining a remote session; session persistence across network changes/device sleep is a wrong axis for this local shell environment rather than something buyers would compare it on.", "evidenceIds": [] }, { "productId": "a-shell", "storyId": "ssh-key-auth", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence in the pack mentions SSH functionality or key types (Ed25519, ECDSA, RSA) supported by a-Shell; documentation covers compiling, Python, Vim, and window/config features but nothing about SSH connectivity.", "evidenceIds": [] }, { "productId": "a-shell", "storyId": "ssh-key-generation", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence in the pack mentions SSH key generation, ssh-keygen, or SSH functionality at all for a-Shell; the documentation covers compiling, Python, Vim, window management, and Shortcuts integration but nothing about SSH key pairs or passwordless server access.", "evidenceIds": [] }, { "productId": "a-shell", "storyId": "ssh-quick-connect", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence of saved-host SSH profiles, credential storage, or one-tap connect features; only bookmarks for directories and general shell features are documented.", "evidenceIds": [ "a-shell-gh-3", "a-shell-gh-6" ] }, { "productId": "a-shell", "storyId": "subnet-routing", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "a-Shell is a local iOS shell/terminal app, not a networking/VPN product; subnet routing to reach remote network devices is entirely outside its category (wrong axis).", "evidenceIds": [] }, { "productId": "blink-shell", "storyId": "agent-pr-analysis", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Blink Shell is a mobile SSH/mosh terminal client; it provides connectivity and file transfer to remote hosts but has no AI agent, PR analysis, or code-review capability of its own. This is a category error for a terminal client, not a missing feature.", "evidenceIds": [] }, { "productId": "blink-shell", "storyId": "agentic-agent-docs", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "Probe confirms no llms.txt exists (404) and no agent-oriented API docs are found; Blink Shell is a terminal/SSH client with no evidence of agent-friendly documentation.", "evidenceIds": [ "blink-shell-probe-1", "blink-shell-probe-2" ] }, { "productId": "blink-shell", "storyId": "agentic-ai-insights", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Blink Shell is a terminal/SSH/Mosh client; AI-generated insights from data is a wrong-axis capability for this product category, not something a terminal emulator would plausibly ship.", "evidenceIds": [] }, { "productId": "blink-shell", "storyId": "agentic-autonomous-automation", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Blink Shell is a mobile SSH/Mosh terminal client, not an automation/agent platform; there's no concept of background autonomous automations in its feature set. This axis is a category error for a terminal client rather than a missing feature.", "evidenceIds": [] }, { "productId": "blink-shell", "storyId": "agentic-builtin-assistant", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Blink Shell is a terminal/SSH/Mosh client for iOS; nothing in the evidence indicates a built-in AI assistant feature. This story is a category error for this product type — a terminal emulator does not deliver AI-agent delegation itself.", "evidenceIds": [] }, { "productId": "blink-shell", "storyId": "agentic-headless", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Blink Shell is an iOS/iPadOS terminal/SSH client app designed for interactive mobile use; running it headlessly or in a CI pipeline is a category mismatch as it has no server/daemon mode or CI-oriented interface.", "evidenceIds": [] }, { "productId": "blink-shell", "storyId": "agentic-mcp-client", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Blink Shell is a terminal/SSH/mosh client for iOS, not an AI agent or MCP-capable platform; MCP server integration is outside its product category.", "evidenceIds": [] }, { "productId": "blink-shell", "storyId": "agentic-mcp-server", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Blink Shell is a terminal/SSH/Mosh client for iOS, not an AI agent or coding assistant; there is no indication it plays the agent role nor offers an MCP server role. Connecting to AI-coding tools like VS Code Server/Codespaces is client-side usage, not an official MCP server axis, so this story is a category error for this product type.", "evidenceIds": [] }, { "productId": "blink-shell", "storyId": "agentic-nl-commands", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Blink Shell is a terminal/SSH client for iOS; the evidence shows only standard shell commands, key management, and terminal UI features, with no natural-language or AI command interface of any kind. This axis (operating via natural-language commands, agenticness) is a category mismatch for a traditional terminal emulator, not a missing feature it could plausibly ship as part of its product identity.", "evidenceIds": [] }, { "productId": "blink-shell", "storyId": "agentic-official-cli", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Blink Shell is a terminal/SSH client app, not an AI agent or developer platform for which an 'official CLI for AI-native workflows' would be a meaningful axis; it is itself a shell/CLI tool, not something with a separate AI-oriented CLI product to evaluate.", "evidenceIds": [] }, { "productId": "blink-shell", "storyId": "agentic-public-api", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No public API or SDK is documented; probes for llms.txt and OpenAPI/Swagger specs all returned 404, and no evidence pack item describes a programmatic/API interface for driving Blink Shell.", "evidenceIds": [ "blink-shell-probe-1", "blink-shell-probe-2" ] }, { "productId": "blink-shell", "storyId": "agentic-scoped-keys", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Blink Shell is a terminal/SSH client for iOS, not an agent-management or API-credential-issuing platform; there is no concept of scoped API credentials for agents in its feature set. This axis is a category error for this product type.", "evidenceIds": [] }, { "productId": "blink-shell", "storyId": "agentic-sdks", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Blink Shell is a terminal/SSH/Mosh client app, not a platform or service with an SDK/API surface for developers to build against; the story of building against official SDKs is a category error for this product type.", "evidenceIds": [] }, { "productId": "blink-shell", "storyId": "agentic-webhooks", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Blink Shell is a terminal/SSH/Mosh client app, not a service or platform with an event system; webhooks are not a fair capability for this kind of product.", "evidenceIds": [] }, { "productId": "blink-shell", "storyId": "ai-commit-message-generation", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Blink Shell is a terminal/SSH client for iOS, not a git or AI tool; there is no evidence of git integration or AI features at all, and generating commit messages is outside its product category (terminal emulator/SSH client).", "evidenceIds": [] }, { "productId": "blink-shell", "storyId": "ai-repository-agent-actions", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Blink Shell is a terminal/SSH client for iOS, not an AI agent or agentic coding tool; there is no evidence of any AI agent integration for directing conversational browse/search/edit/commit/pull/push workflows. This story presumes an AI-native agent product, which is the wrong axis for a terminal emulator.", "evidenceIds": [] }, { "productId": "blink-shell", "storyId": "amend-undo-commits", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Blink Shell is a terminal/SSH/Mosh client for iOS, not a git tool; git commit editing is a wrong-axis capability for a terminal emulator itself (any git operations would occur via a remote shell's own git binary, not Blink Shell functionality).", "evidenceIds": [] }, { "productId": "blink-shell", "storyId": "api-interactive-docs", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Blink Shell is a terminal/SSH client app, not an API-driven platform or SDK; an interactive API reference with runnable examples is not a relevant capability for this product category.", "evidenceIds": [] }, { "productId": "blink-shell", "storyId": "api-machine-spec", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "Blink Shell is a terminal/SSH client, not an API-providing service, but the axis was probed and no machine-readable API spec exists — probes show 404 for llms.txt and all OpenAPI/swagger candidate paths, and no docs mention any API spec.", "evidenceIds": [ "blink-shell-probe-1", "blink-shell-probe-2" ] }, { "productId": "blink-shell", "storyId": "api-sandbox", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Blink Shell is a terminal/SSH client for connecting to remote hosts; it has no concept of sandbox environments or production/test data separation - that's an axis for testing/dev platforms, not a terminal emulator app.", "evidenceIds": [] }, { "productId": "blink-shell", "storyId": "api-versioning-policy", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Blink Shell is a terminal/SSH client app, not a platform offering a programmatic API for third-party/agent integration; the story of versioned APIs with a deprecation policy is a category error for this product type.", "evidenceIds": [] }, { "productId": "blink-shell", "storyId": "assign-issue-to-agent", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Blink Shell is a terminal/SSH/Mosh client for iOS; it has no agent-assignment or autonomous coding-agent workflow that produces pull requests. This capability is entirely outside its product category (terminal emulator/remote shell), not a failed axis.", "evidenceIds": [] }, { "productId": "blink-shell", "storyId": "automation-bulk-operations", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Blink Shell is a terminal/SSH client for iOS; bulk operations across many items is not a fair capability for this kind of product—it's a terminal emulator, not a batch-processing or automation platform.", "evidenceIds": [] }, { "productId": "blink-shell", "storyId": "automation-rules-engine", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence Blink Shell supports defining rules or triggers for automated actions on events; it is a terminal/SSH/Mosh client with no automation-rule engine documented.", "evidenceIds": [] }, { "productId": "blink-shell", "storyId": "automation-scheduled-jobs", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "Blink Shell is a terminal/SSH/Mosh client; there is no evidence of any scheduling, cron-like, or recurring workflow/job automation capability in the docs or community discussion.", "evidenceIds": [] }, { "productId": "blink-shell", "storyId": "automation-versioned-workflows", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Blink Shell is a terminal/SSH client for iOS, not an automation platform with workflows or agent scripts that could be versioned, reviewed, or rolled back; this axis is a category error for this product type.", "evidenceIds": [] }, { "productId": "blink-shell", "storyId": "biometric-connection-auth", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence anywhere in the pack mentions Face ID, Touch ID, biometric authentication, or fingerprint-based unlock/authentication for Blink Shell; the security features documented are SSH key types and password-less key auth only.", "evidenceIds": [ "blink-shell-docs-1", "blink-shell-docs-12" ] }, { "productId": "blink-shell", "storyId": "broadcast-commands", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "Evidence shows Blink supports multiple shells, split view, and switching between sessions, but there is no mention of grouping sessions or broadcasting a single command to multiple sessions simultaneously.", "evidenceIds": [] }, { "productId": "blink-shell", "storyId": "code-search-navigation", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Blink Shell is a terminal/SSH/Mosh client for iOS, not a code search or navigation tool; it provides basic Unix utilities like grep but no fuzzy matching, code-aware filters, or regex-based code navigation features. This axis is a category error for a terminal emulator app.", "evidenceIds": [] }, { "productId": "blink-shell", "storyId": "conversational-repo-agent", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Blink Shell is an SSH/Mosh terminal client for iOS; it has no AI agent, chat interface, or repository/PR insight capability. This story concerns AI-native conversational agent features, which is entirely outside Blink Shell's product category as a terminal emulator.", "evidenceIds": [] }, { "productId": "blink-shell", "storyId": "credential-vault-storage", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "Blink documents separate 'Keys' and 'Hosts' management features, implying SSH keys can be created once and associated with host entries for password-less access, which aligns with a credential-vault-and-reuse pattern. However, there is no explicit documentation confirming a single stored key can be referenced across multiple distinct hosts, no mention of encryption-at-rest or vault security guarantees, and no independent/community confirmation of this specific reuse workflow. Missing for 10: explicit multi-host key reuse documentation, vault security/encryption details, and independent corroboration of the workflow.", "evidenceIds": [ "blink-shell-docs-11", "blink-shell-docs-12", "blink-shell-docs-15" ] }, { "productId": "blink-shell", "storyId": "cross-app-file-access", "verdict": "partial", "quality": 4, "confidence": "low", "rationale": "Blink Files (docs-8) enables working with local and remote projects, and drag-and-drop selection lets users move content to/from other apps (docs-16), suggesting some file interoperability with other apps' sandboxes, but there's no explicit documentation of Files-app document-provider integration or direct access to another app's sandboxed storage/repos. missing for 10: explicit Files app/document-provider integration details, concrete examples of accessing another app's sandbox, independent corroboration of this capability.", "evidenceIds": [ "blink-shell-docs-8", "blink-shell-docs-16" ] }, { "productId": "blink-shell", "storyId": "customizable-terminal-appearance", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "Docs confirm custom fonts/themes support with Pragmata Pro included by default and that users can 'roll your own' fonts/themes, but there's no explicit mention of persisted settings, cursor appearance customization, or color-scheme granularity beyond fonts/themes. missing for 10: dedicated docs on color scheme/cursor customization, explicit confirmation settings persist across sessions/devices, independent hands-on corroboration of theming.", "evidenceIds": [ "blink-shell-docs-5" ] }, { "productId": "blink-shell", "storyId": "direct-p2p-connection", "verdict": "full", "quality": 8, "confidence": "high", "rationale": "Blink Shell is a direct SSH/Mosh client built on libssh, connecting straight to hosts via hostname/user with no cloud relay or VPN required, and this is corroborated by community reviews praising its solid direct connectivity and open-source transparency. Missing for 10: independent technical audit confirming no telemetry/relay involvement, and no explicit statement ruling out any proxy usage.", "evidenceIds": [ "blink-shell-docs-14", "blink-shell-docs-15", "blink-shell-docs-11", "blink-shell-docs-1", "blink-shell-comm-5", "blink-shell-comm-8" ] }, { "productId": "blink-shell", "storyId": "exit-node-routing", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Blink Shell is a terminal/SSH/Mosh client for iOS/iPadOS, not a VPN or network-routing tool; 'exit node' traffic routing (e.g., VPN mesh networking) is a completely different product category and wrong axis for this kind of tool.", "evidenceIds": [] }, { "productId": "blink-shell", "storyId": "file-transfer-scp-sftp", "verdict": "full", "quality": 8, "confidence": "medium", "rationale": "GitHub docs explicitly show scp and sftp usage examples with remote hosts, and Blink supports configured SSH keys (Ed25519, ECDSA, RSA) for authentication per docs, confirming key-based scp/sftp transfers work. Missing for 10: independent hands-on verification of scp/sftp specifically (community discussion focuses mostly on ssh/mosh) and no detail on edge cases like large file transfer performance.", "evidenceIds": [ "blink-shell-gh-1", "blink-shell-docs-1", "blink-shell-docs-12" ] }, { "productId": "blink-shell", "storyId": "git-clone-protocols", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "Blink Shell's documented built-in commands (cat, grep, wc, cd, ls, etc.) do not include git, and no evidence pack item shows native git clone support over HTTPS, SSH, or git protocol; it only documents scp/sftp for file transfer and ssh/mosh for remote sessions, implying git operations would need to happen on a remote server, not natively in Blink.", "evidenceIds": [ "blink-shell-docs-4", "blink-shell-gh-1" ] }, { "productId": "blink-shell", "storyId": "git-commit-graph", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Blink Shell is a terminal/SSH/Mosh client for mobile devices, not a git tool or GUI for visualizing commit history; git graph visualization is outside its product category.", "evidenceIds": [] }, { "productId": "blink-shell", "storyId": "git-commit-push", "verdict": "partial", "quality": 5, "confidence": "low", "rationale": "Blink is an SSH/Mosh terminal client that connects to remote hosts (including VS Code servers, GitHub Codespaces, GitPod) where a developer could run git commands, but the evidence never mentions git itself, a git client, or any explicit commit/push workflow — it's an indirect capability via a generic shell rather than a documented feature. missing for 10: explicit mention of git support, any documented git commit/push workflow, hands-on confirmation of using git from within Blink.", "evidenceIds": [ "blink-shell-docs-7", "blink-shell-docs-8", "blink-shell-docs-15", "blink-shell-docs-4" ] }, { "productId": "blink-shell", "storyId": "git-commit-signing", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "Blink Shell is an SSH/Mosh terminal client; evidence covers SSH key pair generation for server login, but there is no mention of GPG or SSH commit signing for git operations anywhere in the docs or community discussion.", "evidenceIds": [] }, { "productId": "blink-shell", "storyId": "git-interactive-rebase", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Blink Shell is a terminal/SSH/Mosh client for iOS, not a git tool or version control interface; interactive rebase/history rewriting is a git-code capability entirely outside its product category (though a user could run git commands via a remote shell, that's not a feature of Blink itself).", "evidenceIds": [] }, { "productId": "blink-shell", "storyId": "git-merge-conflict-resolution", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Blink Shell is a terminal/SSH/Mosh client for iOS; it provides shell access to remote machines but has no built-in merge-conflict resolution tooling. Resolving merge conflicts is a git-tooling/IDE feature, not something a terminal emulator would plausibly ship, so this axis is a category error for this product.", "evidenceIds": [] }, { "productId": "blink-shell", "storyId": "git-pull-request-creation", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Blink Shell is a terminal/SSH/mosh client for iOS; it provides shell access and code-editor integrations but has no Git platform integration for creating pull requests. This is a category error—PR creation is a GitHub/GitLab web-workflow feature, not something a terminal emulator app would surface directly (users could only do it via git CLI/gh CLI inside a remote shell, which is the remote host's tooling, not Blink's).", "evidenceIds": [] }, { "productId": "blink-shell", "storyId": "git-pull-request-review", "verdict": "partial", "quality": 4, "confidence": "low", "rationale": "Blink Shell is a mobile terminal/SSH client that lets developers connect to remote dev environments (SSH, Mosh, VS Code for web, GitHub Codespaces, GitPod) where command-line git tools or web-based review could be used, but the evidence pack never mentions git, GitHub, gh CLI, or any PR-review-specific feature. This is a generic terminal capability stretched to cover the story rather than a documented PR-review workflow. Missing for 10: explicit git/GitHub CLI support, PR/diff viewing UI or workflow, mobile-optimized review tooling, and any user/community confirmation of doing PR reviews via Blink.", "evidenceIds": [ "blink-shell-docs-7", "blink-shell-docs-15", "blink-shell-docs-8" ] }, { "productId": "blink-shell", "storyId": "git-stash", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Blink Shell is a terminal/SSH/Mosh client for iOS; git stash/unstash is a git version-control operation, not a function of a terminal emulator itself. This is a category error — the axis belongs to a git tool or IDE, not a shell/SSH client.", "evidenceIds": [] }, { "productId": "blink-shell", "storyId": "git-submodules", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Blink Shell is an SSH/Mosh terminal client; any git operations would rely entirely on the remote host's own git binary, not a Blink-native capability. Git submodule management is not a feature category this type of product ships, so the axis does not apply.", "evidenceIds": [] }, { "productId": "blink-shell", "storyId": "host-sync-across-devices", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "There is no evidence of cross-device sync for hosts/settings; in fact a community comment explicitly requests this feature ('Could you consider adding config sync via iCloud/Dropbox? It's quite a pain to sync host lists across several iOS devices'), indicating it was not available.", "evidenceIds": [ "blink-shell-comm-6" ] }, { "productId": "blink-shell", "storyId": "inline-editor-lint", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "Blink Shell is documented as an SSH/mosh terminal with a small set of built-in local commands (cat, grep, wc, cd, ls, etc.) and its 'coding experience' feature explicitly delegates editing to external VS Code servers/Codespaces/Gitpod rather than a built-in terminal editor. No evidence describes a bundled terminal-based text editor (e.g., vim/nano) or any built-in syntax/lint checking capability inside the app itself.", "evidenceIds": [ "blink-shell-docs-4", "blink-shell-docs-7", "blink-shell-docs-8" ] }, { "productId": "blink-shell", "storyId": "local-unix-commands", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "Docs explicitly list built-in commands including ls, grep, cat, cd, touch, cp, rm, mv, mkdir, df, du (blink-shell-docs-4) and file transfer via scp/sftp (blink-shell-gh-1), covering much of the 'run local UNIX commands' story. However, tar and curl are never mentioned anywhere in the evidence pack, so support for those specific commands is unconfirmed. missing for 10: explicit documentation or confirmation that tar and curl are supported as local commands, independent hands-on verification of command behavior.", "evidenceIds": [ "blink-shell-docs-4", "blink-shell-gh-1" ] }, { "productId": "blink-shell", "storyId": "manage-cloud-agent-tasks", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Blink Shell is a terminal/SSH/Mosh client for connecting to remote shells; it has no concept of cloud-based coding agent task management or tracking. This story is a category error for a terminal emulator, not a missing feature.", "evidenceIds": [] }, { "productId": "blink-shell", "storyId": "mesh-vpn-access", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "Blink Shell provides SSH/Mosh terminal access to hosts, but there is no evidence of any Kubernetes-specific integration (kubectl exec, kubeconfig management, cluster access) or broader infrastructure-access features beyond generic SSH to named hosts.", "evidenceIds": [] }, { "productId": "blink-shell", "storyId": "multi-session-management", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "Docs confirm multiple shells can be opened (two-finger tap to create, swipe to switch) and each session can persist via Mosh even after sleep, plus per-shell customization via themes/fonts and hosts. However, there's no explicit evidence that each session maintains fully independent appearance/history configuration simultaneously (e.g., per-tab theme or scrollback isolation) beyond global settings. Missing for 10: documented per-session independent history/appearance settings, and independent corroboration of multi-session workflows beyond basic split-view/switching.", "evidenceIds": [ "blink-shell-docs-10", "blink-shell-docs-3", "blink-shell-docs-2", "blink-shell-docs-5", "blink-shell-gh-3", "blink-shell-docs-11" ] }, { "productId": "blink-shell", "storyId": "nl-to-shell-command", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Blink Shell is an SSH/Mosh terminal client for iOS; it has no natural-language-to-shell-command generation feature. This is a wrong axis for a terminal emulator/SSH client—no evidence suggests it offers any AI/NLP command generation capability.", "evidenceIds": [] }, { "productId": "blink-shell", "storyId": "openness-api-parity", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Blink Shell is a terminal/SSH client app, not a service with a programmatic API surface distinct from its UI; the notion of an API replicating UI functionality is a category mismatch for this product type.", "evidenceIds": [] }, { "productId": "blink-shell", "storyId": "openness-full-export", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Blink Shell is a terminal/SSH client app, not a data-storage or SaaS platform that accumulates user data subject to export; there is no 'user data' corpus (documents, records, etc.) to export in the sense this story implies. Data export/lock-in is a category mismatch for a shell/terminal emulator.", "evidenceIds": [] }, { "productId": "blink-shell", "storyId": "openness-open-license", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "GitHub repo (blinksh/blink) is publicly available and community notes describe it as an open-source development process on GitHub, but the license itself is disputed—one commenter questions GPL compatibility with the App Store, and no evidence pack item explicitly names or confirms an OSI-approved open license for the source. missing for 10: explicit license file/name confirmation, resolution of the GPL/App Store tension, first-party statement of licensing terms.", "evidenceIds": [ "blink-shell-gh-2", "blink-shell-comm-10", "blink-shell-comm-11" ] }, { "productId": "blink-shell", "storyId": "openness-self-host", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Blink Shell is a client-side terminal/SSH app that runs locally on the user's device and connects to servers the user already controls; there is no hosted backend or SaaS component for an 'ai-native' user to self-host. The self-hosting axis applies to server/platform products, not to a local iOS client app, so this is a category mismatch rather than a missing capability.", "evidenceIds": [] }, { "productId": "blink-shell", "storyId": "privacy-data-residency", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Blink Shell is a local terminal/SSH client app, not a data-storage or cloud service; data residency/region selection is not a meaningful axis for this product category.", "evidenceIds": [] }, { "productId": "blink-shell", "storyId": "privacy-no-training", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Blink Shell is a terminal/SSH client, not an AI model or AI service that trains on user data; the question of preventing data being used for AI training is a category error for this product type.", "evidenceIds": [] }, { "productId": "blink-shell", "storyId": "privacy-retention-controls", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Blink Shell is a terminal/SSH/Mosh client for iOS; it does not process or store user data on behalf of an AI service, so data retention/deletion controls are a category error for this kind of product.", "evidenceIds": [] }, { "productId": "blink-shell", "storyId": "privacy-telemetry-optout", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "No evidence in the pack mentions telemetry, analytics, usage tracking, or any opt-out/privacy settings for Blink Shell; the evidence is entirely about SSH/Mosh features, UI, and community feedback unrelated to data collection.", "evidenceIds": [] }, { "productId": "blink-shell", "storyId": "python-package-install", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "Blink Shell's evidence describes it as an SSH/Mosh terminal client with a small set of built-in local commands (cat, grep, wc, ls, etc.) and remote connectivity features; there is no mention of a bundled Python runtime or pip package management on-device. No evidence supports installing pure-Python packages locally.", "evidenceIds": [ "blink-shell-docs-4" ] }, { "productId": "blink-shell", "storyId": "rendered-file-live-preview", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Blink Shell is a terminal/SSH/Mosh client, not a file preview or rendering tool; live-reload preview of Markdown/HTML is outside its category.", "evidenceIds": [] }, { "productId": "blink-shell", "storyId": "secure-enclave-ssh-keys", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "Evidence shows Blink Shell supports creating SSH key pairs (docs-12) but there is no mention of hardware-backed secure enclave storage or biometric protection for keys anywhere in the docs, GitHub, or community discussion.", "evidenceIds": [ "blink-shell-docs-12" ] }, { "productId": "blink-shell", "storyId": "session-persistence-mosh", "verdict": "full", "quality": 9, "confidence": "high", "rationale": "Blink Shell is built around Mosh, explicitly marketed for surviving network changes (train, home, office) and device sleep with connections remaining intact, backed by docs and community praise of solid connectivity. Missing for 10: independent hands-on verification specifically testing sleep/network-switch persistence rather than general connectivity praise.", "evidenceIds": [ "blink-shell-docs-2", "blink-shell-docs-3", "blink-shell-docs-14", "blink-shell-comm-5", "blink-shell-comm-8" ] }, { "productId": "blink-shell", "storyId": "ssh-key-auth", "verdict": "full", "quality": 9, "confidence": "high", "rationale": "Docs explicitly confirm support for Ed25519, ECDSA, and RSA keys via libssh/libssh2, with key pair creation and hostname-based ssh usage documented, and community discussion corroborates Ed25519 support as a differentiator from competitors. Missing for 10: independent hands-on verification of ECDSA/RSA specifically (community focus is mostly on Ed25519).", "evidenceIds": [ "blink-shell-docs-1", "blink-shell-docs-12", "blink-shell-docs-15", "blink-shell-comm-1" ] }, { "productId": "blink-shell", "storyId": "ssh-key-generation", "verdict": "full", "quality": 9, "confidence": "high", "rationale": "Official docs explicitly describe the 'Keys' feature for creating SSH key pairs for password-less server access, supporting Ed25519, ECDSA, and RSA, corroborated by community discussion confirming Ed25519 support (a differentiator vs competitors). Missing for 10: independent hands-on verification of the key-generation UX itself beyond docs description.", "evidenceIds": [ "blink-shell-docs-12", "blink-shell-docs-1", "blink-shell-comm-1" ] }, { "productId": "blink-shell", "storyId": "ssh-quick-connect", "verdict": "full", "quality": 7, "confidence": "medium", "rationale": "Docs confirm saved 'Hosts' allow access via just hostname, SSH key pairs enable password-less login, and connections persist through sleep/network changes via Mosh — together supporting one-tap reconnection to saved hosts without re-entering credentials. missing for 10: no explicit demonstration of a literal one-tap UI flow, and no independent hands-on account specifically validating passwordless saved-host connection.", "evidenceIds": [ "blink-shell-docs-11", "blink-shell-docs-12", "blink-shell-docs-3", "blink-shell-docs-15" ] }, { "productId": "blink-shell", "storyId": "subnet-routing", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Blink Shell is a terminal/SSH/Mosh client for iOS, not a VPN or network-mesh product; subnet routing to reach devices as if on the local network is a VPN-style capability entirely outside its category (wrong axis).", "evidenceIds": [] }, { "productId": "github-mobile", "storyId": "agent-pr-analysis", "verdict": "full", "quality": 7, "confidence": "medium", "rationale": "First-party docs directly state Copilot code review can analyze PRs and suggest improvements from the phone, matching the story closely (github-mobile-docs-4), supported by related Copilot agent task management on mobile (github-mobile-docs-3, docs-5, docs-6). Missing for 10: independent/hands-on verification of this specific Copilot code review feature (community evidence predates Copilot integration and only covers general app usability issues, not AI review functionality).", "evidenceIds": [ "github-mobile-docs-4", "github-mobile-docs-3", "github-mobile-docs-5", "github-mobile-docs-6" ] }, { "productId": "github-mobile", "storyId": "agentic-agent-docs", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "A probe confirms docs.github.com serves a valid llms.txt (HTTP 200) that an agent could be pointed at, but this is generic GitHub documentation rather than anything specific to GitHub Mobile, and no GitHub Mobile-specific agent-oriented docs are shown. missing for 10: GitHub Mobile-specific agent-facing documentation, confirmation the llms.txt content covers mobile app usage, independent corroboration of agents actually using it.", "evidenceIds": [ "github-mobile-probe-1" ] }, { "productId": "github-mobile", "storyId": "agentic-ai-insights", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "GitHub Mobile ships Copilot-powered features that generate insights/suggestions from repo data — code review suggestions, natural-language Q&A over public/private repos, and agent task management — per docs-3 through docs-6. However, these are vendor-only claims with no independent/hands-on corroboration of AI-insight quality in the community evidence, which instead focuses on unrelated UX complaints. Missing for 10: independent verification of AI suggestion accuracy/usefulness, detail on what 'insights' are surfaced proactively (vs. on-demand chat), and community confirmation of these AI features working well in practice.", "evidenceIds": [ "github-mobile-docs-3", "github-mobile-docs-4", "github-mobile-docs-5", "github-mobile-docs-6" ] }, { "productId": "github-mobile", "storyId": "agentic-autonomous-automation", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "GitHub Mobile lets users assign issues to Copilot and manage/track Copilot cloud agent tasks that run autonomously in the background, and start new agent tasks from the app (docs-3, docs-5, docs-6). However, this is essentially a mobile front-end to trigger/monitor agent runs rather than a full automation-builder (e.g., no scheduling, workflow-authoring, or webhook-trigger setup evidenced), and there is no independent/hands-on corroboration of this specific feature's reliability. Missing for 10: evidence of configuring/scheduling automations (not just assigning single tasks), and independent hands-on validation of the Agent Tasks feature.", "evidenceIds": [ "github-mobile-docs-3", "github-mobile-docs-5", "github-mobile-docs-6" ] }, { "productId": "github-mobile", "storyId": "agentic-builtin-assistant", "verdict": "full", "quality": 7, "confidence": "medium", "rationale": "GitHub Mobile ships built-in Copilot features letting users delegate work: assigning issues to Copilot for a ready-to-review PR, launching/tracking Copilot cloud 'Agent Tasks', Copilot code review, and natural-language Copilot chat for code Q&A and PR creation, all within the app. Missing for 10: independent/hands-on verification of these AI features (community evidence only covers pre-Copilot app issues) and detail on reliability/limits of the agent delegation flow.", "evidenceIds": [ "github-mobile-docs-3", "github-mobile-docs-4", "github-mobile-docs-5", "github-mobile-docs-6" ] }, { "productId": "github-mobile", "storyId": "agentic-headless", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "GitHub Mobile is a mobile app UI for interacting with GitHub, not a tool meant to run headlessly in CI/automation pipelines — this axis is a category error for a mobile client application.", "evidenceIds": [] }, { "productId": "github-mobile", "storyId": "agentic-mcp-client", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "GitHub Mobile is a mobile client app for GitHub, not an agent/MCP-client platform where users plug in MCP servers; the evidence shows only Copilot cloud agent task management and code review features, no MCP integration capability of any kind, making this a category error for this product type.", "evidenceIds": [] }, { "productId": "github-mobile", "storyId": "agentic-mcp-server", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "GitHub Mobile is a consumer mobile client app for browsing and managing GitHub activity, not a platform or agent product that would expose or connect to an MCP server; no evidence in the pack even mentions MCP, and the axis is a category mismatch for this kind of product.", "evidenceIds": [] }, { "productId": "github-mobile", "storyId": "agentic-nl-commands", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "GitHub Mobile documents natural-language interaction via Copilot chat (asking Copilot to explain code, navigate repos, open PRs) and Copilot code review/agent task assignment, which are genuine NL-driven agentic capabilities within the app. However this covers only a subset of the app's functionality (core browsing, notifications, merging still require standard UI), and there's no independent/hands-on corroboration of the natural-language features specifically — community evidence only discusses non-AI aspects of the app. Missing for 10: independent corroboration of the Copilot NL features actually working, broader coverage of NL commands beyond code Q&A/PR creation, evidence of reliability in real use.", "evidenceIds": [ "github-mobile-docs-6", "github-mobile-docs-5", "github-mobile-docs-3", "github-mobile-docs-4" ] }, { "productId": "github-mobile", "storyId": "agentic-official-cli", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "GitHub Mobile is a mobile app for browsing/reviewing code, not a CLI product; an official CLI is a wrong axis for a mobile app category (GitHub's CLI, if any, is a separate product not evidenced here).", "evidenceIds": [] }, { "productId": "github-mobile", "storyId": "agentic-public-api", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "GitHub Mobile is a client app with no evidence of exposing its own documented public API; the probe for an OpenAPI/Swagger spec at docs.github.com returned 404s, and the docs pack only markets Copilot features, not programmatic API access to the mobile app itself. missing for 10: any documented REST/GraphQL/OpenAPI spec for driving GitHub Mobile, SDKs, or automation endpoints tied to this product.", "evidenceIds": [ "github-mobile-probe-2", "github-mobile-probe-1" ] }, { "productId": "github-mobile", "storyId": "agentic-scoped-keys", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "GitHub Mobile is a mobile client app for browsing/reviewing repos and PRs, not an API credential/token management surface for AI agents; scoped credential issuance is a GitHub platform (PATs/OAuth Apps/GitHub Apps) concern, not a mobile-app axis.", "evidenceIds": [] }, { "productId": "github-mobile", "storyId": "agentic-sdks", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "GitHub Mobile is a mobile client app for consuming GitHub's platform, not a developer platform/SDK product; 'building against official SDKs' is not a fair axis for this consumer-facing mobile app (that axis applies to GitHub's API/platform, not its mobile client).", "evidenceIds": [] }, { "productId": "github-mobile", "storyId": "agentic-webhooks", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "GitHub Mobile is a mobile client app for consuming GitHub, not a webhook/event subscription surface; webhooks belong to the GitHub platform/API, not this mobile app's category.", "evidenceIds": [] }, { "productId": "github-mobile", "storyId": "ai-commit-message-generation", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "GitHub Mobile has no support for staging/committing changes locally (no git working tree operations); it focuses on PR review, issues, Copilot cloud agent tasks, and code browsing, not local commit workflows where a commit message would be generated from staged diffs.", "evidenceIds": [] }, { "productId": "github-mobile", "storyId": "ai-repository-agent-actions", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "GitHub Mobile lets users converse with Copilot to search code, ask questions about repos, assign issues to Copilot for automated PR creation, and manage Copilot cloud agent tasks—covering browse, search, and a form of edit/commit/PR creation via natural language. However, there's no evidence of a full conversational agent loop that also handles pull/push git operations or arbitrary file edits directly through chat; PR creation is Copilot's autonomous action rather than user-directed commit/pull/push. Missing for 10: explicit pull/push-via-conversation capability, hands-on confirmation of the full browse-to-push agent workflow, and independent corroboration beyond vendor docs.", "evidenceIds": [ "github-mobile-docs-3", "github-mobile-docs-5", "github-mobile-docs-6", "github-mobile-docs-7" ] }, { "productId": "github-mobile", "storyId": "amend-undo-commits", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "GitHub Mobile is a review/notification/PR management app, not a git client with local commit history editing; amending or rewriting commits is a git working-copy operation outside its feature set, making this a category mismatch rather than a missing feature.", "evidenceIds": [] }, { "productId": "github-mobile", "storyId": "api-interactive-docs", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "GitHub Mobile is a mobile client app, not an API/developer platform product; an interactive API reference with runnable examples is a category error for this axis, regardless of GitHub's broader API offerings.", "evidenceIds": [] }, { "productId": "github-mobile", "storyId": "api-machine-spec", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "GitHub Mobile is a consumer mobile app for browsing/reviewing code, not an API or developer platform product; publishing a machine-readable OpenAPI spec is not a fair expectation for this app's category, even though GitHub's broader API exists separately. The probes in evidence confirm no such spec is exposed through the mobile app's own docs.", "evidenceIds": [ "github-mobile-probe-2" ] }, { "productId": "github-mobile", "storyId": "api-sandbox", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "GitHub Mobile is a mobile client for reviewing/managing repos and issues, not a testing/execution environment; sandbox-vs-production testing is outside its product category, so this axis is a category error rather than a missing feature.", "evidenceIds": [] }, { "productId": "github-mobile", "storyId": "api-versioning-policy", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "GitHub Mobile is a mobile client app for GitHub, not a developer API/platform product; versioned API deprecation policy is not an axis relevant to this consumer-facing mobile app itself (that story would apply to the GitHub REST/GraphQL API product, not the mobile client).", "evidenceIds": [] }, { "productId": "github-mobile", "storyId": "assign-issue-to-agent", "verdict": "full", "quality": 7, "confidence": "medium", "rationale": "First-party docs explicitly state the exact capability: 'Assign issues to Copilot and get a ready-to-review pull request. Use comments to refine, iterate, approve and merge—all directly within GitHub Mobile,' plus supporting docs on Copilot cloud Agent Tasks management from mobile. Missing for 10: independent/hands-on corroboration specifically of this AI-agent assignment flow (all community evidence predates this feature and concerns unrelated app UX issues).", "evidenceIds": [ "github-mobile-docs-5", "github-mobile-docs-3", "github-mobile-docs-6" ] }, { "productId": "github-mobile", "storyId": "automation-bulk-operations", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "GitHub Mobile evidence focuses on individual item actions (single PR review, single issue assignment, single search) with no mention of bulk/multi-item operations; community feedback even highlights missing features and friction for single-item workflows, with nothing about batch actions across many items.", "evidenceIds": [] }, { "productId": "github-mobile", "storyId": "automation-rules-engine", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "GitHub Mobile is a mobile client app for viewing/reviewing repos and interacting with Copilot; defining automation rules that trigger on events (e.g., Actions workflows) is a platform/repo-configuration capability, not something a mobile client app would define or ship — wrong axis for this product type.", "evidenceIds": [] }, { "productId": "github-mobile", "storyId": "automation-scheduled-jobs", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "GitHub Mobile evidence covers reviewing PRs, Copilot agent tasks, code search, and notifications on the go, but nothing describes scheduling recurring jobs or workflows (e.g., cron-like automation or scheduled actions) from the app.", "evidenceIds": [] }, { "productId": "github-mobile", "storyId": "automation-versioned-workflows", "verdict": "partial", "quality": 4, "confidence": "low", "rationale": "GitHub Mobile lets users track Copilot cloud agent tasks and review/approve/merge PRs generated by automations, which touches 'review' but nothing in the evidence describes versioning automation configs or explicitly rolling back an automation's changes. missing for 10: explicit workflow/version history for automations, rollback/revert mechanism, and independent confirmation of these capabilities beyond first-party docs.", "evidenceIds": [ "github-mobile-docs-3", "github-mobile-docs-5" ] }, { "productId": "github-mobile", "storyId": "biometric-connection-auth", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "No evidence in the pack mentions biometric authentication, Face ID, fingerprint unlock, or any app-level security lock for GitHub Mobile; only general feature descriptions and unrelated community complaints are present.", "evidenceIds": [] }, { "productId": "github-mobile", "storyId": "broadcast-commands", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "GitHub Mobile is a mobile app for code review/collaboration, not a terminal/SSH tool; grouping terminal sessions and broadcasting commands is a category error for this product type.", "evidenceIds": [] }, { "productId": "github-mobile", "storyId": "code-search-navigation", "verdict": "partial", "quality": 3, "confidence": "low", "rationale": "Docs mention 'global code search' allowing locating snippets and navigating repositories, but there is no evidence of fuzzy matching, filters, or regex support in the mobile search experience. Community feedback also highlights broken navigation to files/links, suggesting code navigation is limited. Missing for 10: documentation or evidence of regex/filter syntax support, fuzzy matching, and independent confirmation of code search functionality working well.", "evidenceIds": [ "github-mobile-docs-7", "github-mobile-comm-2" ] }, { "productId": "github-mobile", "storyId": "conversational-repo-agent", "verdict": "full", "quality": 7, "confidence": "medium", "rationale": "First-party docs explicitly describe conversing with Copilot in natural language on GitHub Mobile to get insights into public/private repositories, explain codebases, and open pull requests, directly matching the story. Missing for 10: independent hands-on corroboration of the AI chat/insights feature specifically (community evidence is mostly about general app usability, not the AI conversational feature) and detail on PR-specific insight depth.", "evidenceIds": [ "github-mobile-docs-6", "github-mobile-docs-3", "github-mobile-docs-4", "github-mobile-docs-5" ] }, { "productId": "github-mobile", "storyId": "credential-vault-storage", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "GitHub Mobile is a mobile client app for GitHub, not a credential/secrets management vault product; storing credentials once and referencing them across hosts is a secrets-manager/CLI-config axis that doesn't apply to this product category.", "evidenceIds": [] }, { "productId": "github-mobile", "storyId": "cross-app-file-access", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "This story concerns OS-level file/document interoperability (e.g., file provider extensions, share sheets accessing other apps' sandboxed files) which is not a relevant axis for a GitHub client app that works with remote repositories via API, not local device file sandboxes.", "evidenceIds": [] }, { "productId": "github-mobile", "storyId": "customizable-terminal-appearance", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "GitHub Mobile is a mobile app for reviewing/managing repos, not a terminal emulator; terminal font/color/cursor customization is a category error for this product type.", "evidenceIds": [] }, { "productId": "github-mobile", "storyId": "direct-p2p-connection", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "GitHub Mobile is a cloud-connected app for GitHub.com/Enterprise Cloud services; direct server connectivity bypassing cloud relay/VPN is a category error for this kind of SaaS mobile client, not an applicable networking-access axis.", "evidenceIds": [] }, { "productId": "github-mobile", "storyId": "exit-node-routing", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "GitHub Mobile is a code collaboration app; exit-node/network-traffic routing is a VPN/networking feature entirely outside its category.", "evidenceIds": [] }, { "productId": "github-mobile", "storyId": "file-transfer-scp-sftp", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "GitHub Mobile is a mobile app for reviewing/managing repos and PRs, not a terminal or SSH client; scp/sftp file transfer via configured keys is entirely outside its category.", "evidenceIds": [] }, { "productId": "github-mobile", "storyId": "git-clone-protocols", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "GitHub Mobile is a companion app for reviewing PRs, issues, and notifications on a phone; it does not provide a git client for cloning repositories via HTTPS/SSH/git protocol, which is a wrong axis for this product type.", "evidenceIds": [] }, { "productId": "github-mobile", "storyId": "git-commit-graph", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence GitHub Mobile offers any commit-graph visualization across branches; docs cover PR review, Copilot features, notifications, and search but nothing about a graph/branch visualization tool, and community feedback focuses on diffs, notifications, and navigation issues instead.", "evidenceIds": [] }, { "productId": "github-mobile", "storyId": "git-commit-push", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "GitHub Mobile's evidence covers PR review, merging, Copilot agent tasks, code search, and notifications, but nowhere mentions committing or pushing local file changes/code edits from the device; one community comment even notes a competing third-party app (Working Copy) is used specifically for shipping small changes from a phone, implying GitHub's own app lacks this.", "evidenceIds": [ "github-mobile-docs-1", "github-mobile-docs-5", "github-mobile-comm-18" ] }, { "productId": "github-mobile", "storyId": "git-commit-signing", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "GitHub Mobile is a review/notification/browsing app, not a git client capable of authoring or signing commits; commit signing with GPG/SSH keys is not something a mobile companion app of this type would perform, so the axis does not apply.", "evidenceIds": [] }, { "productId": "github-mobile", "storyId": "git-interactive-rebase", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "GitHub Mobile's evidence covers PR review, Copilot features, notifications, and code search, but there is no mention of interactive rebase, commit editing, squashing, or reordering—capabilities not supported by mobile git clients generally. No documentation or community evidence indicates this exists.", "evidenceIds": [] }, { "productId": "github-mobile", "storyId": "git-merge-conflict-resolution", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence of any merge conflict resolution tool in GitHub Mobile; the app focuses on PR review, notifications, Copilot tasks, and code search, with no mention of conflict resolution across files. Community feedback even highlights diff-view limitations rather than conflict tools.", "evidenceIds": [] }, { "productId": "github-mobile", "storyId": "git-pull-request-creation", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "GitHub Mobile docs confirm PR-related workflows: assigning issues to Copilot yields a 'ready-to-review pull request' and Copilot chat can 'open a new pull request' directly from the app, with review/approve/merge available in-app. However, evidence centers on Copilot-driven PR creation rather than a straightforward manual 'New Pull Request' flow, and community feedback highlights broader gaps in mobile code-review UX (diff wrapping, missing notifications) though nothing directly disputes PR creation itself. Missing for 10: explicit confirmation of manual (non-Copilot) PR creation from arbitrary branches, and independent hands-on validation of the PR-creation flow.", "evidenceIds": [ "github-mobile-docs-5", "github-mobile-docs-6", "github-mobile-docs-4", "github-mobile-comm-4" ] }, { "productId": "github-mobile", "storyId": "git-pull-request-review", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "GitHub Mobile's official docs explicitly support reviewing, commenting, approving and merging PRs from the phone, plus Copilot-assisted code review, which directly matches the story. However, multiple hands-on community reports describe genuine friction in the review experience itself (diff line-wrapping, large font making diffs hard to read, diff view called 'unusable') and missing PR-review notifications, undercutting a purely full delivery. Missing for 10: independent confirmation that diff readability issues have been fixed, and consistent positive reviews of the core review UX rather than mixed reports.", "evidenceIds": [ "github-mobile-docs-1", "github-mobile-docs-4", "github-mobile-docs-5", "github-mobile-comm-4", "github-mobile-comm-15", "github-mobile-comm-9", "github-mobile-comm-1" ] }, { "productId": "github-mobile", "storyId": "git-stash", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "GitHub Mobile is a review/notification/browsing app, not a local git client with a working directory; git stash/unstash requires a local working copy which GitHub Mobile does not provide, making this a category error for this product type.", "evidenceIds": [] }, { "productId": "github-mobile", "storyId": "git-submodules", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "GitHub Mobile is a mobile companion app for browsing repos, reviewing PRs/issues, and using Copilot—not a git client with clone/checkout/filesystem operations. Managing submodules requires local git repository operations that fall outside this product's category, so this axis does not apply.", "evidenceIds": [] }, { "productId": "github-mobile", "storyId": "host-sync-across-devices", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "This story concerns syncing 'saved hosts and connection settings' — a concept relevant to SSH/remote-connection tools, not a GitHub repository/PR mobile client. GitHub Mobile is a code review/collaboration app with no concept of 'hosts' to connect to; this is a category mismatch, not a missing feature.", "evidenceIds": [] }, { "productId": "github-mobile", "storyId": "inline-editor-lint", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "GitHub Mobile is a mobile app for browsing/reviewing repos, issues, and PRs; it has no terminal/SSH access or embedded code editor with lint/syntax checking, making this axis a category error for this product type.", "evidenceIds": [] }, { "productId": "github-mobile", "storyId": "local-unix-commands", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "GitHub Mobile is a mobile client for reviewing/managing repos, PRs, and Copilot tasks; it has no terminal or shell environment, so running local UNIX commands is a category error for this product type.", "evidenceIds": [] }, { "productId": "github-mobile", "storyId": "manage-cloud-agent-tasks", "verdict": "full", "quality": 8, "confidence": "medium", "rationale": "First-party docs explicitly state Agent Tasks are on GitHub Mobile giving a centralized way to manage Copilot cloud agent tasks, start new tasks, and track progress, directly matching the story. Missing for 10: independent/hands-on corroboration of this specific agent-task feature (community evidence predates this feature and covers general app issues only).", "evidenceIds": [ "github-mobile-docs-3", "github-mobile-docs-5" ] }, { "productId": "github-mobile", "storyId": "mesh-vpn-access", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "GitHub Mobile is a mobile client for code review, issues, and Copilot tasks; infrastructure access to resources like Kubernetes clusters is a zero-trust/network-access category concern (e.g., Teleport, Boundary), entirely outside this product's scope.", "evidenceIds": [] }, { "productId": "github-mobile", "storyId": "multi-session-management", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "GitHub Mobile is a mobile companion app for code review/PR management, not a terminal or SSH tool; the story's concept of multiple terminal sessions with distinct context/appearance/history is a category error for this product type.", "evidenceIds": [] }, { "productId": "github-mobile", "storyId": "nl-to-shell-command", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "GitHub Mobile is a mobile client for repo/PR/issue management and Copilot chat; generating shell commands from natural language is a CLI/terminal-assistant capability outside this product's category and interface.", "evidenceIds": [] }, { "productId": "github-mobile", "storyId": "openness-api-parity", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "GitHub Mobile is a client app (mobile UI), not the API layer itself; API parity is a question for the GitHub platform/API product, not a mobile client. This is a category-mismatch axis for a mobile app.", "evidenceIds": [] }, { "productId": "github-mobile", "storyId": "openness-full-export", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "No evidence in the pack addresses data export, open formats, or account portability from GitHub Mobile; the app's documentation focuses on code review, Copilot, and browsing features only.", "evidenceIds": [] }, { "productId": "github-mobile", "storyId": "openness-open-license", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "GitHub Mobile is a closed proprietary mobile client app; no evidence relates to its source code being open-licensed, and this axis is not a fair question for a mobile companion app's category beyond the vendor's own product openness stance. Treated as not applicable.", "evidenceIds": [] }, { "productId": "github-mobile", "storyId": "openness-self-host", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "GitHub Mobile is a client app for accessing GitHub's hosted service; self-hosting the core product is a category error for a mobile app axis, not something a buyer would evaluate here.", "evidenceIds": [] }, { "productId": "github-mobile", "storyId": "privacy-data-residency", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "No evidence in the pack addresses data residency or region selection for GitHub Mobile or GitHub's backend storage; the mobile app docs and community feedback focus entirely on app features/bugs, not data location controls.", "evidenceIds": [] }, { "productId": "github-mobile", "storyId": "privacy-no-training", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "No evidence in the pack addresses AI-training data opt-out or privacy controls for GitHub Mobile; all citations concern app features, bugs, and UX complaints. Missing for 10: any mention of data-training opt-out settings, Copilot data usage policy, or privacy controls specific to GitHub Mobile.", "evidenceIds": [] }, { "productId": "github-mobile", "storyId": "privacy-retention-controls", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence in the pack addresses data retention or deletion controls related to AI/Copilot features within GitHub Mobile; all citations concern app features, UX complaints, or unrelated docs probes.", "evidenceIds": [] }, { "productId": "github-mobile", "storyId": "privacy-telemetry-optout", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "No evidence in the pack addresses telemetry opt-out or usage tracking controls for GitHub Mobile; all docs focus on features (Copilot, code search, reviews) and community items discuss UX bugs, not privacy settings.", "evidenceIds": [] }, { "productId": "github-mobile", "storyId": "python-package-install", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "GitHub Mobile is a companion app for reviewing/managing repos and PRs, not a terminal or execution environment; installing pip packages is outside its category entirely.", "evidenceIds": [] }, { "productId": "github-mobile", "storyId": "rendered-file-live-preview", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence GitHub Mobile offers any Markdown/HTML file preview with live reload; docs focus on PR review, Copilot agent tasks, code search, and notifications, and community comments describe browsing/reviewing code, not rendered file preview with reload.", "evidenceIds": [] }, { "productId": "github-mobile", "storyId": "secure-enclave-ssh-keys", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "GitHub Mobile is a mobile client for reviewing/managing repos and issues; it has no SSH key management or hardware-backed key storage feature—this is a category mismatch, not a missing feature of the app's intended scope.", "evidenceIds": [] }, { "productId": "github-mobile", "storyId": "session-persistence-mosh", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "GitHub Mobile is a code review/management app, not a terminal or SSH client; persistent terminal sessions across network changes/sleep is a wrong-axis question for this product category.", "evidenceIds": [] }, { "productId": "github-mobile", "storyId": "ssh-key-auth", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "GitHub Mobile is a mobile app for browsing repos, reviews, and Copilot tasks; SSH terminal connectivity with cryptographic keys is entirely outside its category (no terminal/SSH feature is claimed or evidenced).", "evidenceIds": [] }, { "productId": "github-mobile", "storyId": "ssh-key-generation", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "GitHub Mobile is a mobile companion app for code review/notifications, not a terminal or SSH client; generating SSH key pairs for server access is outside its product category (wrong axis).", "evidenceIds": [] }, { "productId": "github-mobile", "storyId": "ssh-quick-connect", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "This story concerns SSH terminal host connections, which is entirely outside GitHub Mobile's category as a code review/PR/issue management app — it has no terminal-SSH functionality mentioned anywhere in evidence.", "evidenceIds": [] }, { "productId": "github-mobile", "storyId": "subnet-routing", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Subnet routing/VPN network access is a networking-tool capability entirely unrelated to GitHub Mobile, which is a mobile client for code review, issues, and Copilot tasks; this axis is a category error for this product.", "evidenceIds": [] }, { "productId": "tailscale", "storyId": "agent-pr-analysis", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Tailscale is a network connectivity/VPN product, not an AI agent or code-analysis tool; analyzing PRs and suggesting code improvements is entirely outside its category. It could at most provide network access to reach such an agent, but that's a different axis from the story itself.", "evidenceIds": [] }, { "productId": "tailscale", "storyId": "agentic-agent-docs", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "A direct probe found llms.txt returns 404, and there is no evidence of agent-oriented documentation or an llms.txt file anywhere in the evidence pack.", "evidenceIds": [ "tailscale-probe-1" ] }, { "productId": "tailscale", "storyId": "agentic-ai-insights", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Tailscale is a networking/VPN product for connecting devices and infrastructure; it has no data analytics or AI-insights layer over user data, and this axis is a category error for its product type.", "evidenceIds": [] }, { "productId": "tailscale", "storyId": "agentic-autonomous-automation", "verdict": "partial", "quality": 3, "confidence": "low", "rationale": "Tailscale documents API/webhook and infrastructure-as-code automation for managing a tailnet (tailscale-docs-12), which could be used to script background automations, but there is no evidence of AI-agent-specific, autonomous background automation capabilities or examples of such use. Missing for 10: dedicated agent/automation framework, evidence of autonomous (not just scriptable) background operation, and any AI-native tooling or examples beyond a single generic automation mention.", "evidenceIds": [ "tailscale-docs-12" ] }, { "productId": "tailscale", "storyId": "agentic-builtin-assistant", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Tailscale is a networking/VPN product; it does not offer or claim any built-in AI assistant feature. Delegating tasks to an AI assistant is outside its product category, making this axis a category error rather than an unmet capability.", "evidenceIds": [] }, { "productId": "tailscale", "storyId": "agentic-headless", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "Docs show Tailscale can run inside Docker containers, be automated via auth keys/IaC/webhooks, and has a documented CLI for scripting—strongly suggesting headless/CI use—but there's no explicit CI pipeline example (e.g., GitHub Actions) in the evidence, and community feedback notes API keys expire every 60 days, complicating long-running automation. missing for 10: explicit CI/CD integration examples, confirmation of long-lived non-expiring credentials for unattended automation, and independent hands-on CI usage reports.", "evidenceIds": [ "tailscale-docs-11", "tailscale-docs-12", "tailscale-probe-3", "tailscale-comm-15" ] }, { "productId": "tailscale", "storyId": "agentic-mcp-client", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Tailscale is a networking/VPN product, not an AI agent or agentic tool; plugging MCP servers into it to gain tool access is a category error for this product type.", "evidenceIds": [] }, { "productId": "tailscale", "storyId": "agentic-mcp-server", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Tailscale is a networking/VPN infrastructure product, not an AI agent or agent-serving platform; no evidence of an MCP server offering exists, and this axis is a category error for a network connectivity tool.", "evidenceIds": [] }, { "productId": "tailscale", "storyId": "agentic-nl-commands", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence Tailscale offers any natural-language command interface, chatbot, or AI assistant control layer; it exposes a traditional CLI and admin console. Probes even show absence of llms.txt/OpenAPI discovery aids. Missing for 10: any NL command parsing, AI assistant integration, or documented conversational interface.", "evidenceIds": [ "tailscale-probe-1", "tailscale-probe-2", "tailscale-probe-3" ] }, { "productId": "tailscale", "storyId": "agentic-official-cli", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "Tailscale documents an official CLI reference (tailscale-probe-3), confirming the capability exists, but the evidence pack lacks detail on CLI features, scripting/automation support for AI-agent workflows, or independent corroboration of its use in agentic contexts. Missing for 10: detailed CLI command documentation, AI-agent-specific automation examples, and independent hands-on validation of CLI robustness.", "evidenceIds": [ "tailscale-probe-3" ] }, { "productId": "tailscale", "storyId": "agentic-public-api", "verdict": "partial", "quality": 3, "confidence": "low", "rationale": "Evidence only vaguely references automating tailnets via 'infrastructure-as-code providers, webhooks, and other integrations' and a documented CLI, but probes explicitly failed to find an OpenAPI/swagger spec or llms.txt, giving no concrete confirmation of a documented public REST API surface in this pack. Missing for 10: explicit API reference docs, endpoint list, authentication scheme details, and independent corroboration of API usage by AI/automation tools.", "evidenceIds": [ "tailscale-docs-12", "tailscale-probe-2", "tailscale-probe-3" ] }, { "productId": "tailscale", "storyId": "agentic-scoped-keys", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "The evidence pack shows general automation/API mentions (docs-12) and API keys expiring after 60 days (comm-15), but nothing about issuing scoped or least-privilege credentials specifically for an AI agent's use — no ACL tag scoping, OAuth client scopes, or agent-specific access controls are documented.", "evidenceIds": [ "tailscale-docs-12", "tailscale-comm-15" ] }, { "productId": "tailscale", "storyId": "agentic-sdks", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "Evidence shows only infra-as-code/webhook integrations and a CLI reference, with no mention of official SDKs; probes explicitly show the OpenAPI spec and llms.txt endpoints returning 404, indicating no discoverable machine-readable API/SDK surface for AI-native builders.", "evidenceIds": [ "tailscale-docs-12", "tailscale-probe-1", "tailscale-probe-2", "tailscale-probe-3" ] }, { "productId": "tailscale", "storyId": "agentic-webhooks", "verdict": "partial", "quality": 5, "confidence": "low", "rationale": "Tailscale docs explicitly mention automating the tailnet via 'infrastructure-as-code providers, webhooks, and other integrations,' indicating webhook support exists, but there's no detail on event types, subscription setup, or payload schema, and no independent/community corroboration of using this feature. Missing for 10: documentation of specific webhook event catalog, setup/config details, and independent confirmation of real-world webhook usage.", "evidenceIds": [ "tailscale-docs-12" ] }, { "productId": "tailscale", "storyId": "ai-commit-message-generation", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Tailscale is a networking/VPN product, not a coding tool or git assistant; AI-generated commit message suggestions are entirely outside its product category and wrong axis for this type of product.", "evidenceIds": [] }, { "productId": "tailscale", "storyId": "ai-repository-agent-actions", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Tailscale is a network connectivity/VPN product, not a coding agent or repository tool; browsing/editing/committing/pushing code is entirely outside its product category — this is a wrong-axis question, not a gap in its networking feature set.", "evidenceIds": [] }, { "productId": "tailscale", "storyId": "amend-undo-commits", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Tailscale is a networking/VPN product with no git functionality; amending commits or managing git history is entirely outside its product category.", "evidenceIds": [] }, { "productId": "tailscale", "storyId": "api-interactive-docs", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence of an interactive API reference or runnable examples; probes for OpenAPI/swagger specs returned 404s, and there's no mention of an interactive API explorer in the docs pack.", "evidenceIds": [ "tailscale-probe-2" ] }, { "productId": "tailscale", "storyId": "api-machine-spec", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "Tailscale does have a documented REST API, but the evidence pack shows explicit probe failures for OpenAPI/Swagger spec endpoints at all candidate URLs, with no machine-readable spec found. missing for 10: a downloadable OpenAPI/Swagger JSON or YAML spec, any documentation page linking to such a spec.", "evidenceIds": [ "tailscale-probe-2", "tailscale-probe-1" ] }, { "productId": "tailscale", "storyId": "api-sandbox", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Tailscale is a network connectivity/VPN product, not a testing, data-management, or sandbox-environment tool; the notion of 'sandbox vs production data' for AI testing is a wrong axis for this product category.", "evidenceIds": [] }, { "productId": "tailscale", "storyId": "api-versioning-policy", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "No evidence of API versioning documentation or a deprecation policy; probes for OpenAPI/spec files returned 404s and no docs mention API version lifecycle. missing for 10: documented API versioning scheme, deprecation policy, changelog for breaking changes.", "evidenceIds": [ "tailscale-probe-2" ] }, { "productId": "tailscale", "storyId": "assign-issue-to-agent", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Tailscale is a networking/VPN product; assigning issues to AI coding agents and receiving pull requests is entirely outside its category — this is a wrong-axis question, not a capability gap.", "evidenceIds": [] }, { "productId": "tailscale", "storyId": "automation-bulk-operations", "verdict": "partial", "quality": 3, "confidence": "low", "rationale": "Tailscale exposes a CLI and supports infrastructure-as-code/webhook automation of a tailnet, which implies a user could script bulk changes across many devices, but there is no concrete documentation or example of a native bulk-operations feature (e.g., batch tagging, mass key rotation, multi-device ACL updates) or API endpoint for bulk actions. missing for 10: explicit bulk-operation API/CLI examples, evidence of batch device/user management, independent confirmation of scripted bulk workflows.", "evidenceIds": [ "tailscale-docs-12", "tailscale-probe-3" ] }, { "productId": "tailscale", "storyId": "automation-rules-engine", "verdict": "partial", "quality": 3, "confidence": "low", "rationale": "Tailscale documents webhooks and infrastructure-as-code integrations for automating tailnet events, which could be used to trigger external actions on network changes, but there is no evidence of a built-in rules engine for defining conditional automation logic tied to arbitrary events. Missing for 10: documented rule/condition syntax, examples of event-triggered automations, and independent confirmation of this capability being used for automation workflows.", "evidenceIds": [ "tailscale-docs-12" ] }, { "productId": "tailscale", "storyId": "automation-scheduled-jobs", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Tailscale is a networking/VPN product; scheduling recurring jobs or workflows is not a networking capability and falls entirely outside its product category. This is a wrong-axis question, not a missing feature.", "evidenceIds": [] }, { "productId": "tailscale", "storyId": "automation-versioned-workflows", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Tailscale is a networking/VPN product, not an automation/workflow-building tool with versionable automations; versioning, reviewing, and rolling back 'automations' is not a fair axis for its category.", "evidenceIds": [] }, { "productId": "tailscale", "storyId": "biometric-connection-auth", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "No evidence in the pack mentions Face ID, fingerprint, or any biometric authentication mechanism for Tailscale connections; only SSO/identity-provider login is discussed. missing for 10: any documentation or claim of biometric/Face ID/fingerprint authentication support.", "evidenceIds": [] }, { "productId": "tailscale", "storyId": "broadcast-commands", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Tailscale is a networking/VPN product providing connectivity between devices; it has no terminal multiplexing or broadcast-command-to-multiple-sessions feature, and grouping terminal sessions is a wrong axis for a mesh-networking tool, not a networking capability gap.", "evidenceIds": [] }, { "productId": "tailscale", "storyId": "code-search-navigation", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Tailscale is a networking/VPN product; code search, fuzzy matching, and regex-based navigation of code content are outside its category entirely — this is a wrong-axis question, not a missing feature.", "evidenceIds": [] }, { "productId": "tailscale", "storyId": "conversational-repo-agent", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Tailscale is a networking/VPN product; conversing with an AI agent about repository/PR insights is entirely outside its category (wrong axis), not something Tailscale's evidence pack even attempts to address.", "evidenceIds": [] }, { "productId": "tailscale", "storyId": "credential-vault-storage", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Tailscale is a networking/VPN mesh product, not a secrets/credentials vault; the evidence pack shows it provides secure network access (SSH, Kubernetes, subnet routing) but no capability for storing or referencing credentials/secrets. This story is a category error for this product type.", "evidenceIds": [] }, { "productId": "tailscale", "storyId": "cross-app-file-access", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "This story concerns sandboxed app file/repo access (an OS-level app-sandbox interoperability concern), which is unrelated to Tailscale's category as a mesh VPN/networking tool for device and service connectivity — wrong axis for this product type.", "evidenceIds": [] }, { "productId": "tailscale", "storyId": "customizable-terminal-appearance", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Tailscale is a VPN/networking product, not a terminal or CLI application with UI customization features; terminal appearance settings are entirely outside its product category.", "evidenceIds": [] }, { "productId": "tailscale", "storyId": "direct-p2p-connection", "verdict": "disputed", "quality": 6, "confidence": "medium", "rationale": "Tailscale's mesh overlay and WireGuard-based architecture is documented to establish direct peer-to-peer connections for SSH, Kubernetes, NAS, and subnet access (tailscale-docs-1,5,6,9; tailscale-comm-1,7,8), and users report direct SSH/file access 'like I'm home' (tailscale-docs-7,8). However, hands-on community reports concretely contradict the 'no relay' claim: NAT traversal 'doesn't always work, sometimes I get connected to a DERP server, so that limits network speeds' (tailscale-comm-10), meaning cloud relay fallback is a real, documented occurrence rather than a hypothetical. Missing for 10: first-party acknowledgment/quantification of DERP relay fallback frequency, and independent benchmarking of direct-vs-relayed connection rates.", "evidenceIds": [ "tailscale-docs-1", "tailscale-docs-5", "tailscale-docs-6", "tailscale-docs-7", "tailscale-docs-8", "tailscale-comm-1", "tailscale-comm-10" ] }, { "productId": "tailscale", "storyId": "exit-node-routing", "verdict": "full", "quality": 8, "confidence": "high", "rationale": "First-party docs explicitly document exit nodes for routing all internet traffic through a specific device, and community evidence corroborates real-world use of exit nodes (e.g., using a home exit node to bypass geo-blocking). Missing for 10: independent hands-on walkthrough of exit-node setup/performance and more detail on configuration nuances.", "evidenceIds": [ "tailscale-docs-10", "tailscale-comm-8" ] }, { "productId": "tailscale", "storyId": "file-transfer-scp-sftp", "verdict": "partial", "quality": 5, "confidence": "low", "rationale": "Tailscale provides standard IP connectivity between devices so any TCP-based tool including scp/sftp over SSH should work using normal SSH keys, and evidence confirms SSH access to boxes (tailscale-docs-6, tailscale-docs-7, tailscale-comm-1). However, there is no explicit mention of scp/sftp usage, and community reports specifically flag file-transfer performance overhead as a real drawback (tailscale-comm-7), which is directly relevant to this story's file-transfer use case. Missing for 10: explicit scp/sftp documentation or examples, confirmation that key-based auth flows unchanged, and resolution of the noted file-transfer performance complaints.", "evidenceIds": [ "tailscale-docs-6", "tailscale-docs-7", "tailscale-comm-1", "tailscale-comm-7" ] }, { "productId": "tailscale", "storyId": "git-clone-protocols", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Tailscale is a networking/VPN tool, not a Git hosting or code-clone tool; cloning repos via HTTPS/SSH/Git protocol is outside its product category, though it could enable network access to a self-hosted Git server as a side effect.", "evidenceIds": [] }, { "productId": "tailscale", "storyId": "git-commit-graph", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Tailscale is a networking/VPN product; visualizing git commit graphs is entirely outside its category and unrelated to any of its documented features.", "evidenceIds": [] }, { "productId": "tailscale", "storyId": "git-commit-push", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Tailscale is a networking/VPN product, not a git or source-control tool; committing and pushing code is entirely outside its category (wrong axis).", "evidenceIds": [] }, { "productId": "tailscale", "storyId": "git-commit-signing", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Tailscale is a networking/VPN product, not a git or code-signing tool; signing commits with GPG/SSH keys is entirely outside its product category.", "evidenceIds": [] }, { "productId": "tailscale", "storyId": "git-interactive-rebase", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Tailscale is a networking/VPN product, not a version control tool; interactive git history rewriting is entirely outside its category.", "evidenceIds": [] }, { "productId": "tailscale", "storyId": "git-merge-conflict-resolution", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Tailscale is a networking/VPN product; merge conflict resolution is a git/code-editing capability entirely outside its category.", "evidenceIds": [] }, { "productId": "tailscale", "storyId": "git-pull-request-creation", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Tailscale is a networking/VPN tool; creating pull requests on Git platforms is a source-control feature entirely outside its category — this is a wrong-axis question, not a missing capability.", "evidenceIds": [] }, { "productId": "tailscale", "storyId": "git-pull-request-review", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Tailscale is a network connectivity/VPN tool; reviewing pull requests is a git-hosting/code-review workflow entirely outside its product category. It could enable mobile access to a self-hosted git server, but that's a stretch not evidenced, and the axis itself is a wrong-category fit for a networking product.", "evidenceIds": [] }, { "productId": "tailscale", "storyId": "git-stash", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Tailscale is a networking/VPN product with no git or version control functionality; git stash/unstash is entirely outside its product category.", "evidenceIds": [] }, { "productId": "tailscale", "storyId": "git-submodules", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Tailscale is a networking/VPN tool, not a Git or version-control product; managing Git submodules is entirely outside its category and not a fair axis for it.", "evidenceIds": [] }, { "productId": "tailscale", "storyId": "host-sync-across-devices", "verdict": "partial", "quality": 4, "confidence": "low", "rationale": "Tailscale's mesh network model means every device on a tailnet automatically sees the same peer/device list (hosts) via the coordination server, and docs describe it as cross-platform and infrastructure agnostic, which implies your network of devices is consistent everywhere. However, there is no explicit evidence of syncing individual 'connection settings' (e.g., exit-node choice, per-device preferences, saved shortcuts) across devices beyond the shared tailnet device list. Missing for 10: documentation of settings/preference sync (not just device visibility), independent confirmation that user-level configs carry across devices, and any UI showing 'saved hosts' as a discrete synced feature.", "evidenceIds": [ "tailscale-docs-4", "tailscale-docs-5", "tailscale-docs-9" ] }, { "productId": "tailscale", "storyId": "inline-editor-lint", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Tailscale is a networking/VPN product providing connectivity (SSH, subnet routing, mesh network); it is not an editor, IDE, or code-quality tool and does not provide in-app terminal editing or lint/syntax checking. This is a wrong-axis story for the product category.", "evidenceIds": [] }, { "productId": "tailscale", "storyId": "local-unix-commands", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Tailscale is a networking/VPN mesh product, not a terminal/agent app with a built-in shell; running local UNIX commands like ls/grep/tar/curl inside 'the app' is a category error for this product type — it enables SSH connectivity to remote machines but does not itself execute local shell commands.", "evidenceIds": [] }, { "productId": "tailscale", "storyId": "manage-cloud-agent-tasks", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Tailscale is a network connectivity/VPN mesh product, not a coding-agent task management or tracking tool; nothing in the evidence relates to managing or tracking cloud-based coding agent tasks, only network access from devices including phones.", "evidenceIds": [] }, { "productId": "tailscale", "storyId": "mesh-vpn-access", "verdict": "full", "quality": 8, "confidence": "medium", "rationale": "First-party docs explicitly claim infrastructure access 'wherever your resources live, including Kubernetes clusters,' with auditable SSH/K8s/database access, subnet routers, and infra-as-code integrations, and community testimonials corroborate managing home k8s clusters and SSH access remotely. Missing for 10: independent hands-on validation specifically of Kubernetes access (only a generic homelab testimonial), and no detailed K8s-operator documentation excerpt beyond marketing claims.", "evidenceIds": [ "tailscale-docs-1", "tailscale-docs-6", "tailscale-docs-8", "tailscale-docs-9", "tailscale-docs-12", "tailscale-comm-1" ] }, { "productId": "tailscale", "storyId": "multi-session-management", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Tailscale is a networking/VPN mesh product, not a terminal emulator or SSH client with session/appearance/history management — multi-session terminal UX is a wrong-axis question for this category of product.", "evidenceIds": [] }, { "productId": "tailscale", "storyId": "nl-to-shell-command", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Tailscale is a networking/VPN product, not a natural-language-to-command generation tool; this axis is a category error for its product type.", "evidenceIds": [] }, { "productId": "tailscale", "storyId": "openness-api-parity", "verdict": "partial", "quality": 3, "confidence": "low", "rationale": "Docs mention automating a tailnet via infrastructure-as-code, webhooks, and other integrations, and a CLI reference exists, implying some API/CLI parity with the admin console, but there is no explicit claim or evidence that every UI action (e.g., user management, subnet routing, ACL editing) is fully exposed via API, and probes found no discoverable OpenAPI spec. Missing for 10: explicit API/UI feature-parity documentation, a discoverable OpenAPI/API reference, and independent confirmation that admin console actions map 1:1 to API calls.", "evidenceIds": [ "tailscale-docs-12", "tailscale-docs-13", "tailscale-probe-2", "tailscale-probe-3" ] }, { "productId": "tailscale", "storyId": "openness-full-export", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Tailscale is a network connectivity/VPN product, not a data-store or content-authoring platform; the notion of 'exporting all my data in open formats and leaving' does not apply to its category — this is a wrong axis rather than a missing feature.", "evidenceIds": [] }, { "productId": "tailscale", "storyId": "openness-open-license", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "No evidence in the pack shows Tailscale publishing its source under an open license; on the contrary, a community comment explicitly describes Tailscale's control/coordination server as 'closed source' (tailscale-comm-19), and no docs or repos are cited to counter this.", "evidenceIds": [ "tailscale-comm-19" ] }, { "productId": "tailscale", "storyId": "openness-self-host", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No vendor documentation claims a self-hostable control server; multiple independent community comments explicitly note Tailscale's coordination/control server is closed-source and cannot be self-hosted, with users citing this as a trust/lock-in concern.", "evidenceIds": [ "tailscale-comm-4", "tailscale-comm-19", "tailscale-comm-20" ] }, { "productId": "tailscale", "storyId": "privacy-data-residency", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "Tailscale is a mesh VPN/networking product; the evidence pack contains nothing about choosing a data storage region or data residency controls for user data/AI content. This is a plausible axis for privacy-conscious SaaS-style products, but there is no documentation of regional data storage or residency options, so it is 'none' rather than 'na'.", "evidenceIds": [] }, { "productId": "tailscale", "storyId": "privacy-no-training", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Tailscale is a networking/VPN mesh product, not an AI model provider or data processor that trains AI models; the axis of preventing data use for AI training is a category error for this product type.", "evidenceIds": [] }, { "productId": "tailscale", "storyId": "privacy-retention-controls", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence addresses data retention policies, deletion controls, or AI-native data handling settings; evidence pack focuses on networking features, VPN performance, and identity provider concerns unrelated to data retention/deletion.", "evidenceIds": [] }, { "productId": "tailscale", "storyId": "privacy-telemetry-optout", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "The evidence pack contains no documentation or community mention of a telemetry/usage-tracking opt-out setting for Tailscale; only unrelated product marketing, feature docs, and general community trust/security discussions are present. This is a fair question for a network/VPN product, but no capability is evidenced.", "evidenceIds": [] }, { "productId": "tailscale", "storyId": "python-package-install", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Tailscale is a networking/VPN product; installing pip packages is a local development environment concern unrelated to network connectivity, which is entirely outside its category.", "evidenceIds": [] }, { "productId": "tailscale", "storyId": "rendered-file-live-preview", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Tailscale is a networking/VPN tool; live-reload preview of Markdown/HTML files is a code-editor/IDE feature, entirely outside its product category.", "evidenceIds": [] }, { "productId": "tailscale", "storyId": "secure-enclave-ssh-keys", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Tailscale is a mesh networking/VPN product; hardware-backed secure enclave storage for SSH keys protected by biometrics is a credential-management/OS-security feature outside its product category, not something a networking tool ships.", "evidenceIds": [] }, { "productId": "tailscale", "storyId": "session-persistence-mosh", "verdict": "partial", "quality": 3, "confidence": "low", "rationale": "Evidence shows Tailscale is commonly used to SSH into always-reachable devices (docs-7, comm-1) via a stable mesh network, which implies some resilience, but there is no explicit evidence that an active terminal session survives network changes or device sleep (e.g., no mosh-like session persistence claim). Community reports also note connectivity breakage from ISPs/guest wifi blocking Tailscale ports and NAT traversal failures (comm-11, comm-10), casting doubt on seamless roaming. missing for 10: explicit documentation or hands-on test of session persistence across network/device changes, confirmation of roaming behavior during sleep/wake cycles.", "evidenceIds": [ "tailscale-docs-7", "tailscale-comm-1", "tailscale-comm-11", "tailscale-comm-10" ] }, { "productId": "tailscale", "storyId": "ssh-key-auth", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "Evidence confirms Tailscale is commonly used to SSH into remote machines (docs-6, docs-7, comm-1), since it provides an encrypted network layer that carries ordinary SSH traffic, but there is no evidence addressing support for specific SSH key types (Ed25519, ECDSA, RSA) — this is typically handled by the standard OS SSH client, not Tailscale itself. Missing for 10: explicit documentation of key-type support, Tailscale SSH feature's key handling specifics, and independent confirmation of standard-key SSH working over Tailscale.", "evidenceIds": [ "tailscale-docs-6", "tailscale-docs-7", "tailscale-comm-1" ] }, { "productId": "tailscale", "storyId": "ssh-key-generation", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "Tailscale enables password-less SSH access to servers (its Tailscale SSH feature and mesh network let users SSH into boxes without manual key exchange), evidenced by docs-6/docs-7 and community testimonials of SSHing into machines effortlessly (tailscale-comm-1). However, this works by replacing traditional SSH key-pair generation with Tailscale's own node identity and ACLs rather than an actual 'generate an SSH key pair' workflow, so the story as literally stated (generating SSH key pairs) is not directly evidenced. Missing for 10: explicit key-pair generation tooling/docs, first-party walkthrough of the Tailscale SSH feature, and independent verification of key-based passwordless access specifically.", "evidenceIds": [ "tailscale-docs-6", "tailscale-docs-7", "tailscale-comm-1" ] }, { "productId": "tailscale", "storyId": "ssh-quick-connect", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "Tailscale's mesh network keeps authenticated devices persistently reachable, and testimonials describe SSH'ing into boxes 'like I'm home' and managing home servers 'from my phone,' implying no per-session credential re-entry once connected. However, no evidence specifically documents a 'saved host' UI with one-tap connect (e.g., a bookmarked host list in the app), and some community reports describe friction (mobile client issues, NAT traversal problems) that complicate a seamless one-tap experience. Missing for 10: explicit one-tap saved-host UI documentation, first-party screenshots/demo of the connect flow, and independent confirmation of zero re-authentication across sessions.", "evidenceIds": [ "tailscale-docs-7", "tailscale-docs-8", "tailscale-comm-1", "tailscale-comm-6", "tailscale-comm-10" ] }, { "productId": "tailscale", "storyId": "subnet-routing", "verdict": "full", "quality": 9, "confidence": "high", "rationale": "Tailscale's docs explicitly describe subnet routers giving devices outside the local network access to services within specific subnets, plus broader infrastructure access (Kubernetes, SSH, cloud/on-prem) and community hands-on confirmation of SSH'ing into remote boxes and managing home NAS/k8s clusters as if local. Missing for 10: independent third-party benchmark or detailed hands-on walkthrough specifically of subnet router setup (rather than general VPN/exit-node use).", "evidenceIds": [ "tailscale-docs-9", "tailscale-docs-6", "tailscale-docs-5", "tailscale-docs-7", "tailscale-docs-8", "tailscale-comm-1" ] }, { "productId": "termius", "storyId": "agent-pr-analysis", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Termius is a mobile-capable SSH/terminal client; PR analysis and code-suggestion agents are a code-review/CI-integration capability outside its category, which focuses on terminal sessions, host management, and shell command AI assistance. Nothing in the evidence shows PR/code review integration, so this is a wrong-axis question rather than a missing feature.", "evidenceIds": [] }, { "productId": "termius", "storyId": "agentic-agent-docs", "verdict": "full", "quality": 8, "confidence": "high", "rationale": "A probe confirms docs.termius.com/llms.txt returns HTTP 200 with structured documentation links, meaning an agent can be pointed directly at an llms.txt file. Missing for 10: no first-party announcement or documentation explicitly describing/promoting the llms.txt file as an agent-facing feature, and no independent corroboration of its completeness or maintenance.", "evidenceIds": [ "termius-probe-1" ] }, { "productId": "termius", "storyId": "agentic-ai-insights", "verdict": "partial", "quality": 4, "confidence": "low", "rationale": "Termius docs mention AI-generated shell commands from plain-language descriptions (docs-6), which is a form of AI suggestion, but there's no evidence of AI-generated insights derived from the user's own data (e.g., analyzing session logs, host activity, or infrastructure patterns) — autocomplete (docs-11, docs-24) is rule/history-based, not AI-driven. missing for 10: AI analysis/insights over session logs or infrastructure data, dashboards or summaries generated from user data, independent/hands-on corroboration of the AI command feature.", "evidenceIds": [ "termius-docs-6", "termius-docs-24", "termius-docs-25" ] }, { "productId": "termius", "storyId": "agentic-autonomous-automation", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "Termius offers snippets, broadcast commands, and workspace templates that are user-triggered, but there is no evidence of scheduling, triggers, or autonomous background execution without a user actively running them.", "evidenceIds": [] }, { "productId": "termius", "storyId": "agentic-builtin-assistant", "verdict": "partial", "quality": 4, "confidence": "low", "rationale": "Termius docs mention AI-assisted command generation from natural language (termius-docs-6), which is a narrow AI helper feature rather than a full agentic assistant capable of being delegated multi-step tasks. Missing for 10: evidence of autonomous task execution, multi-step delegation, or a persistent AI assistant beyond single-command translation, and no independent/hands-on corroboration of this AI feature's real-world use.", "evidenceIds": [ "termius-docs-6" ] }, { "productId": "termius", "storyId": "agentic-headless", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Termius is a GUI-based SSH/terminal client designed for interactive, human-driven sessions across desktop and mobile; running headlessly or in CI automation pipelines is outside its product category (no CLI, headless mode, or automation API is evidenced or implied by its design).", "evidenceIds": [] }, { "productId": "termius", "storyId": "agentic-mcp-client", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Termius is an SSH/terminal client focused on connectivity, key management, and collaboration; there is no evidence of any MCP server integration or plugin mechanism for AI tools, and this axis is not a natural fit for a terminal/SSH client product category.", "evidenceIds": [] }, { "productId": "termius", "storyId": "agentic-mcp-server", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Termius is an SSH/terminal client (an agent-adjacent tool for humans), not an ecosystem/platform expected to expose an official MCP server for other AI agents to connect to; no evidence suggests it plays that server role. This is a category mismatch rather than a missing feature.", "evidenceIds": [] }, { "productId": "termius", "storyId": "agentic-nl-commands", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "Termius docs explicitly describe an AI feature that converts plain-language descriptions into shell commands (termius-docs-6), directly supporting natural-language command operation. However, this appears limited to command generation within the terminal rather than broader natural-language control of the app (e.g., navigating hosts, managing vaults, or automating workflows via NL), and there's no independent/community corroboration of this AI feature's real-world reliability. Missing for 10: broader NL control beyond command generation, hands-on/community validation of the AI feature, and details on accuracy/limitations.", "evidenceIds": [ "termius-docs-6" ] }, { "productId": "termius", "storyId": "agentic-official-cli", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "The evidence pack covers Termius's GUI features (snippets, workspaces, port forwarding, AI command generation) but contains no mention of an official standalone CLI tool for scripting/automation outside the app; the probe for OpenAPI/API surface also returned 404s, suggesting no documented CLI/API surface.", "evidenceIds": [ "termius-probe-2" ] }, { "productId": "termius", "storyId": "agentic-public-api", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence of a documented public API for driving Termius programmatically; OpenAPI probes all returned 404, and docs focus on UI/CLI features like snippets, AI command generation, and sync rather than an API for external agent control.", "evidenceIds": [ "termius-probe-2", "termius-probe-1" ] }, { "productId": "termius", "storyId": "agentic-scoped-keys", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Termius is an SSH/terminal client for human users, not an agent platform or identity provider; issuing scoped API credentials for an AI agent is outside its product category and not something a buyer comparing terminal clients would expect.", "evidenceIds": [] }, { "productId": "termius", "storyId": "agentic-sdks", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence of any official SDK for developers to build against; Termius is an SSH client with AI-generated command features, not a platform offering SDKs, and the openapi probe returned 404s with no SDK docs found.", "evidenceIds": [ "termius-probe-2", "termius-docs-6" ] }, { "productId": "termius", "storyId": "agentic-webhooks", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Termius is an SSH client/terminal app, not an event-driven platform; webhook subscriptions are outside its product category (wrong axis) rather than a missing feature.", "evidenceIds": [] }, { "productId": "termius", "storyId": "ai-commit-message-generation", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Termius is an SSH/terminal client, not a version control or git tool; commit message generation is unrelated to its product category (its AI feature is for generating shell commands, not git commits).", "evidenceIds": [] }, { "productId": "termius", "storyId": "ai-repository-agent-actions", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Termius is an SSH/terminal client, not an AI coding agent or repo-management tool; the story asks for an AI agent to browse/search/edit/commit/pull/push in a repository via conversation, which is a category error for this product type. Its AI feature is limited to generating shell commands from plain language, not agentic repo operations.", "evidenceIds": [ "termius-docs-6" ] }, { "productId": "termius", "storyId": "amend-undo-commits", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Termius is an SSH client/terminal tool, not a git client or version control tool; amending or undoing commits is entirely outside its product category (wrong axis).", "evidenceIds": [] }, { "productId": "termius", "storyId": "api-interactive-docs", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "Termius is an SSH client, not an API product; no evidence of an interactive API reference or runnable examples exists, and the OpenAPI probe explicitly returned 404s at all candidate paths. There is no documented API playground or reference in the evidence pack.", "evidenceIds": [ "termius-probe-2" ] }, { "productId": "termius", "storyId": "api-machine-spec", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "A probe explicitly checked for OpenAPI/Swagger spec files at common paths and all returned 404, and no other evidence mentions a machine-readable API spec being available for download.", "evidenceIds": [ "termius-probe-2" ] }, { "productId": "termius", "storyId": "api-sandbox", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Termius is an SSH/terminal client for connecting to and managing real servers, not a testing or sandboxing tool; there is no concept of a 'sandbox vs production' testing environment in its feature set. This axis is a category error for a terminal/SSH client.", "evidenceIds": [] }, { "productId": "termius", "storyId": "api-versioning-policy", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "Termius is an SSH client focused on terminal/session management; there is no evidence of a public versioned API or documented deprecation policy. The openapi probe returned 404 for all candidate paths, confirming absence of API documentation.", "evidenceIds": [ "termius-probe-2" ] }, { "productId": "termius", "storyId": "assign-issue-to-agent", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Termius is an SSH/terminal client for managing server connections, not an AI coding agent or issue-tracking/PR workflow tool; assigning issues to agents and receiving PRs is outside its product category.", "evidenceIds": [] }, { "productId": "termius", "storyId": "automation-bulk-operations", "verdict": "full", "quality": 8, "confidence": "medium", "rationale": "Termius provides multiple documented bulk-operation mechanisms: broadcasting commands to all sessions simultaneously and saving as reusable workspace templates, executing snippets on multiple hosts at once, and CSV bulk-import of hosts/groups/credentials. These directly satisfy 'bulk operations across many items.' Missing for 10: independent/hands-on corroboration specifically validating broadcast-to-many-hosts at scale (community evidence only touches snippet scripting, not the broadcast/bulk-import features) and evidence of bulk operations on other item types like credentials or vault entries.", "evidenceIds": [ "termius-docs-4", "termius-docs-5", "termius-docs-17", "termius-docs-18", "termius-docs-19", "termius-comm-1" ] }, { "productId": "termius", "storyId": "automation-rules-engine", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "Termius evidence covers saved connections, jump-host auto-routing, snippets/broadcast commands, and AI command generation, but none of this describes user-defined rules that trigger actions automatically on events (e.g., on-connect/on-disconnect triggers, webhooks, conditional automations). Jump-host auto-connect is a static config, not an event-rule engine, and no evidence pack item describes any such automation system.", "evidenceIds": [ "termius-docs-2", "termius-docs-4", "termius-docs-5", "termius-docs-6" ] }, { "productId": "termius", "storyId": "automation-scheduled-jobs", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "Termius offers snippets, broadcast commands, and templates, but no evidence of scheduling recurring jobs or workflows (e.g., cron-like triggers or timed automation) exists in the pack.", "evidenceIds": [] }, { "productId": "termius", "storyId": "automation-versioned-workflows", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "Termius offers snippets, templates, and logs, but there is no evidence of version control, review workflows, or rollback capability for automations/snippets—no changelog, history, or revert feature is documented.", "evidenceIds": [] }, { "productId": "termius", "storyId": "biometric-connection-auth", "verdict": "full", "quality": 8, "confidence": "medium", "rationale": "Termius docs explicitly claim biometric protection via Windows Hello, Touch ID/Face ID, and Android biometrics tied to device-bound keys, directly matching the story. Missing for 10: independent/hands-on corroboration of biometric unlock in practice and details on implementation robustness across platforms.", "evidenceIds": [ "termius-docs-14", "termius-docs-13" ] }, { "productId": "termius", "storyId": "broadcast-commands", "verdict": "full", "quality": 8, "confidence": "high", "rationale": "Termius Workspaces feature explicitly groups multiple terminal sessions and broadcasts the same input to all of them, with templates capturing layout, tabs, and running commands (termius-docs-18, termius-docs-19, termius-docs-4). Missing for 10: independent hands-on corroboration of broadcast reliability across many hosts and any documented limits/edge cases from community sources.", "evidenceIds": [ "termius-docs-18", "termius-docs-19", "termius-docs-4" ] }, { "productId": "termius", "storyId": "code-search-navigation", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Termius is an SSH/terminal client, not a code editor or repository tool; searching/navigating code content with fuzzy matching, filters, and regex is a wrong-axis capability for this product category. It only offers log searching, not code content search/navigation.", "evidenceIds": [] }, { "productId": "termius", "storyId": "conversational-repo-agent", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Termius is an SSH/terminal client for managing servers; it has no repository or pull-request awareness, and this story's subject (AI conversational insight into repos/PRs) is a wrong-axis category error for this product type. Its only AI feature is natural-language-to-shell-command generation, unrelated to repos/PRs.", "evidenceIds": [ "termius-docs-6" ] }, { "productId": "termius", "storyId": "credential-vault-storage", "verdict": "full", "quality": 8, "confidence": "medium", "rationale": "Termius provides a Keychain vault where credentials (SSH keys, passwords) are stored once and referenced by multiple Hosts and Groups without duplication, backed by Personal and Team vaults synced across devices with encryption. This directly matches the story's core need of centralized credential storage referenced across hosts. Missing for 10: independent/hands-on verification of the vault-reference mechanism specifically (community evidence covers general SSH client experience but not this exact vault-reuse workflow), and no detail on encryption specifics beyond marketing claims.", "evidenceIds": [ "termius-docs-3", "termius-docs-8", "termius-docs-9", "termius-docs-28", "termius-docs-12" ] }, { "productId": "termius", "storyId": "cross-app-file-access", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Termius is an SSH/terminal client focused on remote server management, not a file-system/document interop tool with iOS/Android app-sandbox file access (like Files app document providers). Accessing other apps' sandboxed files/repos is outside its product category.", "evidenceIds": [] }, { "productId": "termius", "storyId": "customizable-terminal-appearance", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "No vendor documentation describes font, color, or cursor customization for Termius, and a community report explicitly states the user could not add custom fonts, indicating this capability is not evidenced or is missing.", "evidenceIds": [ "termius-comm-8" ] }, { "productId": "termius", "storyId": "direct-p2p-connection", "verdict": "full", "quality": 8, "confidence": "medium", "rationale": "Termius explicitly documents local-first, direct SSH connections without cloud dependency: \"Termius doesn't depend on the cloud to manage your access... Connect directly to your servers without the internet, a proxy, or VPN,\" backed by locally encrypted infrastructure storage. Community evidence corroborates real direct SSH usage in the field (debugging via SSH from mobile), though no independent technical audit verifies the no-relay claim. Missing for 10: independent/hands-on verification of the no-relay architecture claim, and details on how sync (which does use Termius cloud) is kept separate from the direct connection path.", "evidenceIds": [ "termius-docs-15", "termius-docs-8", "termius-comm-2", "termius-comm-12" ] }, { "productId": "termius", "storyId": "exit-node-routing", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Termius is an SSH/terminal client with port forwarding and tunneling (local/remote/dynamic), not a VPN or mesh-networking tool that can route all device traffic through an exit node. This capability is outside the product's category (SSH/SFTP session management), so the axis does not apply.", "evidenceIds": [ "termius-docs-20", "termius-docs-15" ] }, { "productId": "termius", "storyId": "file-transfer-scp-sftp", "verdict": "full", "quality": 8, "confidence": "high", "rationale": "Termius documents SFTP file transfer with a dual-pane interface and one-click switching between terminal and SFTP sessions on the same host, using the same configured Hosts/Keychain credentials, plus a keychain for SSH key management with passphrase protection referenced across connections. This directly covers scp/sftp-style file transfer using configured keys. Missing for 10: explicit mention of the `scp` command/protocol specifically (only SFTP is named) and independent hands-on corroboration of file-transfer reliability.", "evidenceIds": [ "termius-docs-21", "termius-docs-22", "termius-docs-12", "termius-docs-3" ] }, { "productId": "termius", "storyId": "git-clone-protocols", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Termius is an SSH/terminal client focused on server connections, file transfer, and session management, not a Git client or version control tool; cloning Git repositories over HTTPS/SSH/Git protocol is outside its product category.", "evidenceIds": [] }, { "productId": "termius", "storyId": "git-commit-graph", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Termius is an SSH/terminal client, not a source-control or git tool; visualizing a commit graph across branches is entirely outside its product category.", "evidenceIds": [] }, { "productId": "termius", "storyId": "git-commit-push", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Termius is an SSH/terminal client for connecting to remote hosts, snippets, and file transfer—it has no git integration or version control features for committing/pushing code. This story is a category error for this product type.", "evidenceIds": [] }, { "productId": "termius", "storyId": "git-commit-signing", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Termius is an SSH/terminal client focused on connection management, not a git/version-control tool; commit signing with GPG/SSH keys is a git workflow feature outside its product category. Evidence covers SSH key generation/management for authentication, not git commit signing.", "evidenceIds": [] }, { "productId": "termius", "storyId": "git-interactive-rebase", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Termius is an SSH/terminal client, not a git tool; interactive rebase/history rewriting is entirely outside its product category.", "evidenceIds": [] }, { "productId": "termius", "storyId": "git-merge-conflict-resolution", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Termius is an SSH/terminal client, not a source-control or code-diff tool; merge conflict resolution is entirely outside its product category.", "evidenceIds": [] }, { "productId": "termius", "storyId": "git-pull-request-creation", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Termius is an SSH/terminal client focused on connecting to hosts, managing keys, and terminal collaboration; it is not a Git hosting or Git workflow tool and has no evidence of Git/PR integration, so creating pull requests is outside its product category.", "evidenceIds": [] }, { "productId": "termius", "storyId": "git-pull-request-review", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Termius is an SSH/terminal client, not a git/code review tool; it has no mention of pull requests, git hosting integration, or code review workflows. Reviewing PRs is outside its product category (wrong axis), even though it supports mobile terminal SSH sessions.", "evidenceIds": [] }, { "productId": "termius", "storyId": "git-stash", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Termius is an SSH/terminal client, not a version control tool; git stash/unstash is a wrong axis for this product category.", "evidenceIds": [] }, { "productId": "termius", "storyId": "git-submodules", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Termius is an SSH/terminal client focused on host management, file transfer, and session tools; Git submodule management is a source-control operation entirely outside its product category, not something a terminal client would ship as a feature.", "evidenceIds": [] }, { "productId": "termius", "storyId": "host-sync-across-devices", "verdict": "full", "quality": 8, "confidence": "high", "rationale": "Termius documents a Personal vault synced across all devices, automatic sync of vaults/hosts/configurations on login, and cross-device access to hosts, keys, groups, snippets, and port-forwarding rules; community evidence corroborates cross-device usage (e.g., debugging from iPhone). Missing for 10: independent verification of sync reliability/conflict handling and no detailed technical explanation of sync mechanism/security internals.", "evidenceIds": [ "termius-docs-8", "termius-docs-29", "termius-docs-28", "termius-docs-3", "termius-comm-2", "termius-comm-13" ] }, { "productId": "termius", "storyId": "inline-editor-lint", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Termius is an SSH client/terminal app for connecting to remote hosts, not a text editor or IDE with built-in linting/syntax-checking capability; editing and running lint checkers is outside its product category (users would rely on remote shell tools like vim/nano and remote linters via SSH, not a Termius-native feature).", "evidenceIds": [] }, { "productId": "termius", "storyId": "local-unix-commands", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "All evidence describes Termius as an SSH/SFTP client for connecting to and managing remote hosts (snippets run on hosts, port forwarding, session logs, SFTP), with no mention of a local shell/terminal mode for running commands like ls, grep, cat, tar, curl directly against the local machine. Missing for 10: any documentation or community confirmation of a local terminal tab/local command execution feature.", "evidenceIds": [ "termius-docs-5", "termius-docs-23", "termius-docs-21", "termius-docs-22" ] }, { "productId": "termius", "storyId": "manage-cloud-agent-tasks", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Termius is an SSH/terminal client for managing servers, not a platform for orchestrating or tracking cloud-based AI coding agent tasks; nothing in the evidence relates to coding agent task management.", "evidenceIds": [] }, { "productId": "termius", "storyId": "mesh-vpn-access", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "Termius's evidence pack covers SSH/host management, port forwarding, vaults, snippets, and file transfer, but there is no mention anywhere of Kubernetes clusters, kubectl integration, or container-orchestration access—this is a specific capability that is entirely unevidenced.", "evidenceIds": [] }, { "productId": "termius", "storyId": "multi-session-management", "verdict": "full", "quality": 8, "confidence": "medium", "rationale": "Termius Workspaces explicitly group multiple terminal sessions with per-session tab names, layout, working directories, and saved templates, while each Host retains its own connection context, keychain-linked credentials, and per-host session logs/history. Community evidence corroborates multi-session use in the field (e.g., managing multiple servers via saved snippets and SSH sessions), though performance complaints on Windows suggest some friction at scale. Missing for 10: independent hands-on verification of per-session appearance customization (themes/fonts) and no direct community testimony about running many concurrent tabs smoothly.", "evidenceIds": [ "termius-docs-18", "termius-docs-19", "termius-docs-25", "termius-docs-31", "termius-comm-1", "termius-comm-3" ] }, { "productId": "termius", "storyId": "nl-to-shell-command", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "Termius docs explicitly state it can convert a plain-language description into a shell command via AI generation, directly matching the story. However, this is a single first-party doc claim with no independent/hands-on corroboration, no detail on scope/accuracy, and no community evidence discussing this AI feature. missing for 10: independent or hands-on verification of the AI command-generation feature, detail on its reliability/limitations, and broader documentation beyond one line.", "evidenceIds": [ "termius-docs-6" ] }, { "productId": "termius", "storyId": "openness-api-parity", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence of a public API exposing Termius's core UI capabilities (hosts, snippets, vaults, workspaces) programmatically; probes for an OpenAPI spec all returned 404, and no documentation describes an API at all.", "evidenceIds": [ "termius-probe-2" ] }, { "productId": "termius", "storyId": "openness-full-export", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "Evidence shows Termius supports importing hosts/keys from SSH config and CSV files, but nowhere does the pack mention any export function for hosts, keychains, snippets, or vaults in open formats, and community comments raise concern about SSH keys being stored on Termius' servers with no mention of an exit path.", "evidenceIds": [ "termius-docs-16", "termius-docs-17", "termius-comm-16", "termius-comm-4" ] }, { "productId": "termius", "storyId": "openness-open-license", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "Termius is closed-source; there's no evidence of an open license or public source repository, and community feedback (termius-comm-4) explicitly notes concerns about it being closed-source with no visibility into crypto implementation.", "evidenceIds": [ "termius-comm-4" ] }, { "productId": "termius", "storyId": "openness-self-host", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "Termius is presented as a cloud-synced SSH client with Personal/Team vaults and sync services (termius-docs-8, termius-docs-9, termius-docs-29); there is no mention of any self-hosted server/backend option or on-prem deployment for the core product. termius-docs-15 only notes local caching of credentials for offline connect, not a self-hosted core service. Missing for 10: any documented self-hosted/on-prem deployment option, self-hosting instructions, or enterprise self-managed sync server.", "evidenceIds": [ "termius-docs-8", "termius-docs-9", "termius-docs-15", "termius-docs-29" ] }, { "productId": "termius", "storyId": "privacy-data-residency", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence Termius offers any data residency or region-selection controls for where vault/host data is stored; docs only describe local encryption and sync to Termius' cloud without regional choice options.", "evidenceIds": [] }, { "productId": "termius", "storyId": "privacy-no-training", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "No evidence pack item mentions AI training data opt-out, data usage policy for model training, or any privacy control specific to AI training; only unrelated AI-command-generation feature (termius-docs-6) is mentioned, which does not address data usage/training consent.", "evidenceIds": [] }, { "productId": "termius", "storyId": "privacy-retention-controls", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "Termius documents where data lives (Personal/Team vaults, local encrypted storage, synced session logs) but provides no evidence of user-facing controls for setting retention periods, purging logs, or deleting synced/vault data on demand.", "evidenceIds": [ "termius-docs-7", "termius-docs-8", "termius-docs-9", "termius-docs-15", "termius-docs-25" ] }, { "productId": "termius", "storyId": "privacy-telemetry-optout", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence pack item mentions telemetry, usage tracking, analytics opt-out, or any privacy/data-collection settings controllable by the user; documentation focuses on features (sync, keychain, SSH keys) not telemetry controls.", "evidenceIds": [] }, { "productId": "termius", "storyId": "python-package-install", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Termius is an SSH/terminal client, not a Python runtime or package manager; installing pip packages would occur on the remote host's OS itself, not as a Termius feature. This axis is a category error for this product type.", "evidenceIds": [] }, { "productId": "termius", "storyId": "rendered-file-live-preview", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Termius is an SSH/terminal client focused on remote connections, file transfer, and terminal collaboration; it has no evidence of rendering Markdown/HTML preview with live reload, which is a file/document-editing feature outside its category as a terminal tool.", "evidenceIds": [] }, { "productId": "termius", "storyId": "secure-enclave-ssh-keys", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "Termius docs explicitly claim 'device-bound keys and biometric protection with Windows Hello, Touch ID/Face ID, or Android biometrics' plus FIDO2 security key support, matching the hardware-backed/biometric claim reasonably well. However, there's no explicit mention of a 'secure enclave' term or independent verification of how keys are hardware-isolated, and community comments express skepticism about SSH keys being stored on Termius' servers and about closed-source crypto practices, which tempers confidence without concretely disproving the biometric/device-bound claim. Missing for 10: independent/hands-on verification of the secure-enclave implementation, explicit documentation of enclave/TPM/Keystore usage, and resolution of community concerns about key storage location.", "evidenceIds": [ "termius-docs-14", "termius-docs-13", "termius-docs-12", "termius-comm-16", "termius-comm-4" ] }, { "productId": "termius", "storyId": "session-persistence-mosh", "verdict": "partial", "quality": 5, "confidence": "low", "rationale": "A single community comment confirms Termius supports Mosh, which enables sessions to survive network changes, and another notes remote debugging while mobile, suggesting some resilience to connectivity drops. However there is no first-party documentation describing session persistence across network changes or device sleep, and no evidence addressing behavior specifically during device sleep. missing for 10: first-party docs on Mosh/session-persistence feature, explicit device-sleep resilience evidence, independent verification beyond one HN comment.", "evidenceIds": [ "termius-comm-2", "termius-comm-12" ] }, { "productId": "termius", "storyId": "ssh-key-auth", "verdict": "full", "quality": 9, "confidence": "high", "rationale": "Termius docs explicitly confirm it can generate Ed25519, ECDSA, RSA (and ML-DSA) keys with passphrase protection, and supports importing existing ~/.ssh keys and configs for connecting to remote servers via SSH. Community evidence corroborates real-world SSH usage as a core client function. Missing for 10: independent hands-on verification specifically testing each key type's SSH connection success.", "evidenceIds": [ "termius-docs-27", "termius-docs-12", "termius-docs-16", "termius-comm-1", "termius-comm-2" ] }, { "productId": "termius", "storyId": "ssh-key-generation", "verdict": "full", "quality": 8, "confidence": "high", "rationale": "Termius docs explicitly confirm SSH key pair generation (Ed25519, ECDSA, RSA, ML-DSA) with passphrase protection, encrypted storage, and cross-device sync/keychain reuse across hosts for password-less auth. Missing for 10: independent hands-on verification of the key-generation workflow itself (community evidence covers other features but not this specific one).", "evidenceIds": [ "termius-docs-12", "termius-docs-27", "termius-docs-3", "termius-docs-8" ] }, { "productId": "termius", "storyId": "ssh-quick-connect", "verdict": "full", "quality": 8, "confidence": "high", "rationale": "Docs confirm saved hosts with credentials stored in Keychain/vault so users connect instantly without re-entering IPs/ports/passwords, with sync across devices enabling one-tap access from any client. Community evidence corroborates real-world quick reconnection (e.g., fixing servers from a phone). Missing for 10: independent hands-on verification specifically of the one-tap flow (vs. broader feature set) and no mention of biometric/one-tap unlock friction trade-offs.", "evidenceIds": [ "termius-docs-1", "termius-docs-3", "termius-docs-8", "termius-docs-29", "termius-comm-2", "termius-comm-12" ] }, { "productId": "termius", "storyId": "subnet-routing", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Subnet routing (reaching an entire remote subnet via a single gateway node, à la Tailscale subnet routers) is a mesh-VPN networking feature, not something an SSH/terminal client like Termius provides. Termius offers per-host jump hosts, port forwarding, and tunneling, but these require configuring access per host/service, not exposing a whole subnet transparently — this capability class is outside Termius's product category.", "evidenceIds": [] }, { "productId": "working-copy", "storyId": "agent-pr-analysis", "verdict": "partial", "quality": 4, "confidence": "low", "rationale": "Working Copy ships a 'Repository Agent' AI assistant that can browse, search, read/modify files, commit, pull and push from the phone, which is a general agentic capability, but the docs never mention it analyzing pull requests specifically or suggesting code improvements (only AI-generated commit messages are separately documented). missing for 10: explicit PR review/analysis feature, code-improvement suggestions, independent hands-on evidence of the Repository Agent doing this task.", "evidenceIds": [ "working-copy-docs-29", "working-copy-docs-5" ] }, { "productId": "working-copy", "storyId": "agentic-agent-docs", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "Probes explicitly show no llms.txt, no markdown-accessible docs, and no OpenAPI spec exist for Working Copy; no evidence of any agent-oriented documentation format being provided.", "evidenceIds": [ "working-copy-probe-1", "working-copy-probe-2", "working-copy-probe-3" ] }, { "productId": "working-copy", "storyId": "agentic-ai-insights", "verdict": "partial", "quality": 6, "confidence": "low", "rationale": "Working Copy documents two AI features: AI-suggested commit messages based on staged diffs (docs-5) and a conversational 'Repository Agent' that can browse, search, read/modify files, commit, pull and push (docs-29) — both surface AI-generated insight/suggestions from the user's repository data. However, evidence is entirely first-party docs with no independent/hands-on validation of quality or reliability, and no detail on depth of 'insights' beyond commit messages and agentic file actions. Missing for 10: independent/hands-on corroboration of the Repository Agent's real-world usefulness, and richer detail on what kinds of data insights (beyond commit suggestions) are generated.", "evidenceIds": [ "working-copy-docs-5", "working-copy-docs-29" ] }, { "productId": "working-copy", "storyId": "agentic-autonomous-automation", "verdict": "partial", "quality": 4, "confidence": "low", "rationale": "Working Copy integrates with Apple's Shortcuts app for automation (docs-28) and has a conversational Repository Agent that can browse, edit, commit, pull and push (docs-29), but neither is documented as running autonomously in the background without user-triggered interaction — Shortcuts automations in this context appear action-chaining rather than scheduled/autonomous, and the Repository Agent is described as conversational (user-driven), not a background daemon. missing for 10: explicit documentation of scheduled/triggered background automations, evidence of autonomous unattended execution, and independent confirmation of background automation working.", "evidenceIds": [ "working-copy-docs-28", "working-copy-docs-29" ] }, { "productId": "working-copy", "storyId": "agentic-builtin-assistant", "verdict": "full", "quality": 7, "confidence": "medium", "rationale": "Working Copy documents a built-in 'Repository Agent' AI assistant that users interact with conversationally to browse files, search content, read/modify files, commit, pull and push — directly matching the delegation story, alongside a separate AI commit-message suggestion feature. missing for 10: no independent/hands-on user reports confirming the Repository Agent's real-world reliability, and no detail on scope limits or setup requirements.", "evidenceIds": [ "working-copy-docs-29", "working-copy-docs-5" ] }, { "productId": "working-copy", "storyId": "agentic-headless", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Working Copy is a GUI-based iOS git client tied to the iPhone/iPad interface; it offers on-device automation via Shortcuts and URL schemes but has no server/CLI mode that could run headlessly in a CI pipeline. Running headlessly/in CI is a category error for this type of mobile app, not a missing feature.", "evidenceIds": [ "working-copy-docs-28" ] }, { "productId": "working-copy", "storyId": "agentic-mcp-client", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "Working Copy's docs describe a built-in 'Repository Agent' AI assistant but there is no evidence it supports plugging in external MCP servers or consuming third-party tools via MCP; automation is only via Shortcuts app actions, not MCP.", "evidenceIds": [ "working-copy-docs-29", "working-copy-docs-28" ] }, { "productId": "working-copy", "storyId": "agentic-mcp-server", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "Working Copy is a git client with a built-in 'Repository Agent' AI assistant (docs-29), but there is no evidence of an official MCP server that lets external agents connect to Working Copy; probes for llms.txt/openapi endpoints also return 404s.", "evidenceIds": [ "working-copy-docs-29", "working-copy-probe-1", "working-copy-probe-2", "working-copy-probe-3" ] }, { "productId": "working-copy", "storyId": "agentic-nl-commands", "verdict": "full", "quality": 7, "confidence": "medium", "rationale": "The docs describe a 'Repository Agent' AI assistant that users interact with via conversation to browse files, search content, read/modify files, commit, pull, and push — directly matching natural-language operation. However, this is first-party documentation only, with no independent/hands-on corroboration of how well the natural-language interface actually performs. Missing for 10: independent user reports validating the Repository Agent's reliability, and detail on the scope/limits of supported natural-language commands.", "evidenceIds": [ "working-copy-docs-29" ] }, { "productId": "working-copy", "storyId": "agentic-official-cli", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Working Copy is an iOS-only Git client with no terminal/CLI environment; its automation surface is limited to URL schemes, Shortcuts integration, and an in-app AI 'Repository Agent'. A traditional CLI is not a coherent capability for a sandboxed iOS app, making this axis a category mismatch rather than a missing feature.", "evidenceIds": [ "working-copy-docs-28", "working-copy-docs-29" ] }, { "productId": "working-copy", "storyId": "agentic-public-api", "verdict": "partial", "quality": 3, "confidence": "medium", "rationale": "Working Copy documents automation via the Shortcuts app (docs-28) and a WebDAV server for file transfer (docs-27), which allow some programmatic/agentic control, but there is no documented REST/OpenAPI or general-purpose public API — probes confirm no openapi.json, no llms.txt, and no machine-readable docs endpoint. missing for 10: a documented REST/OpenAPI-style API, API reference/docs, and independent confirmation that AI agents can drive it beyond Shortcuts.", "evidenceIds": [ "working-copy-docs-28", "working-copy-docs-27", "working-copy-probe-1", "working-copy-probe-2", "working-copy-probe-3" ] }, { "productId": "working-copy", "storyId": "agentic-scoped-keys", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence of any API credential/token scoping mechanism for agents; Working Copy uses SSH keys/Identities for git auth and has a Repository Agent AI assistant, but nothing about issuing scoped or least-privilege API credentials for external agents.", "evidenceIds": [ "working-copy-docs-20", "working-copy-docs-29", "working-copy-probe-3" ] }, { "productId": "working-copy", "storyId": "agentic-sdks", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Working Copy is a Git client app for iOS, not a platform offering an SDK for developers to build against; the story asks about official SDKs which is a category error for this product type.", "evidenceIds": [] }, { "productId": "working-copy", "storyId": "agentic-webhooks", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Working Copy is a mobile Git client app, not a service with an event-driven API; webhooks (subscribing to repo/CI events) is not a fair capability for this type of product. Evidence shows Shortcuts automation and Files app integration but nothing about webhook subscriptions, which is out of scope for a client app.", "evidenceIds": [ "working-copy-docs-28" ] }, { "productId": "working-copy", "storyId": "ai-commit-message-generation", "verdict": "full", "quality": 8, "confidence": "medium", "rationale": "Working Copy's docs explicitly state it can suggest commit messages using AI based on staged diffs, sent to OpenAI, directly matching the story. Missing for 10: independent/hands-on corroboration of this specific AI commit-message feature and details on accuracy/configuration options.", "evidenceIds": [ "working-copy-docs-5" ] }, { "productId": "working-copy", "storyId": "ai-repository-agent-actions", "verdict": "full", "quality": 7, "confidence": "medium", "rationale": "Working Copy documents a first-party \"Repository Agent\" that is explicitly described as an AI assistant interacted with via conversation, capable of browsing files, searching content, reading/modifying files, committing, pulling and pushing — directly matching the story. However, there is no independent/community corroboration of this specific agent feature working hands-on, and details on setup, model/provider, and reliability are thin. Missing for 10: independent or hands-on validation of the Repository Agent, more detail on configuration/limitations, and confirmation of conversational browsing/search fidelity beyond the doc line.", "evidenceIds": [ "working-copy-docs-29", "working-copy-docs-4", "working-copy-docs-5" ] }, { "productId": "working-copy", "storyId": "amend-undo-commits", "verdict": "full", "quality": 8, "confidence": "high", "rationale": "Docs explicitly describe amending the latest commit via the commit dialog's Amend toggle and undoing unpushed commits via swipe-left, with changes preserved in the working directory, plus additional editing tools (Edit Message, Squash, Delete Commit) for splitting/fixing history. Missing for 10: independent hands-on verification of these specific commit-editing workflows beyond first-party docs.", "evidenceIds": [ "working-copy-docs-15", "working-copy-docs-16", "working-copy-docs-17" ] }, { "productId": "working-copy", "storyId": "api-interactive-docs", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "Working Copy is a mobile git client with no evidence of any API reference, interactive docs, or runnable examples; probes for llms.txt, markdown docs, and OpenAPI specs all returned 404.", "evidenceIds": [ "working-copy-probe-1", "working-copy-probe-2", "working-copy-probe-3" ] }, { "productId": "working-copy", "storyId": "api-machine-spec", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "Probes explicitly show no OpenAPI/swagger spec exists at any candidate path and no llms.txt or machine-readable docs are available; Working Copy exposes Shortcuts automation and an x-callback-url scheme but no documented downloadable API spec.", "evidenceIds": [ "working-copy-probe-1", "working-copy-probe-2", "working-copy-probe-3" ] }, { "productId": "working-copy", "storyId": "api-sandbox", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Working Copy is a git client for iOS; sandbox-vs-production data isolation for AI testing is not a relevant capability for this kind of product — it's a wrong-axis question.", "evidenceIds": [] }, { "productId": "working-copy", "storyId": "api-versioning-policy", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence of any public API, versioning scheme, or deprecation policy; probes for OpenAPI/llms.txt all return 404s, and Working Copy's docs only cover in-app Git features, not an API for programmatic/agentic access.", "evidenceIds": [ "working-copy-probe-1", "working-copy-probe-2", "working-copy-probe-3" ] }, { "productId": "working-copy", "storyId": "assign-issue-to-agent", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "Working Copy's 'Repository Agent' is a conversational AI assistant for browsing/editing/committing within the app, but there is no evidence of assigning an external issue to an autonomous agent that then produces a ready-to-review pull request. missing for 10: issue-to-PR automation workflow, autonomous agent triggering from issue assignment, PR creation/readiness evidence.", "evidenceIds": [ "working-copy-docs-29" ] }, { "productId": "working-copy", "storyId": "automation-bulk-operations", "verdict": "partial", "quality": 4, "confidence": "low", "rationale": "The docs show some bulk-like features — the Resolve tool for handling merge conflicts across many files at once, Shortcuts app automation for scripting flows across files, and a Repository Agent AI assistant that can browse/search/modify/commit across a repo — but there is no evidence of true bulk operations across many items (e.g., batch commits across multiple repos, mass file edits, bulk push/pull) as an AI-native automation feature. Missing for 10: explicit multi-repo or multi-file batch APIs, scripted bulk edit/commit workflows, and independent verification that Shortcuts or the Repository Agent can perform such bulk tasks reliably.", "evidenceIds": [ "working-copy-docs-7", "working-copy-docs-28", "working-copy-docs-29" ] }, { "productId": "working-copy", "storyId": "automation-rules-engine", "verdict": "partial", "quality": 4, "confidence": "low", "rationale": "Working Copy supports Shortcuts app automation where files/data flow between actions, which allows building event-triggered workflows via iOS Shortcuts automations (e.g., time/location/app triggers), but there's no first-party rule engine or documented event-trigger system within Working Copy itself. missing for 10: native event/rule triggers inside the app, documented automation-on-git-events (e.g. auto-commit/push on file change), examples of Shortcuts automations actually wired to Working Copy triggers.", "evidenceIds": [ "working-copy-docs-28" ] }, { "productId": "working-copy", "storyId": "automation-scheduled-jobs", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "No evidence of scheduling or recurring job/workflow capability; Shortcuts automation and Repository Agent support ad-hoc triggers, not scheduled recurring jobs. Missing for 10: any scheduling mechanism, cron-like triggers, or recurring workflow automation documentation.", "evidenceIds": [] }, { "productId": "working-copy", "storyId": "automation-versioned-workflows", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "Working Copy provides strong git version-control primitives (commit, undo, amend, delete/squash commits, checkout old versions, commit graph) that could version and roll back automation scripts stored in a repo, and its Repository Agent AI assistant can commit/pull/push conversationally, plus Shortcuts automation integration. However, the story frames automation-workflow versioning specifically, and there's no evidence of automation-run history, diffing of automation configs, or rollback tied to Shortcuts/agent-run outputs rather than generic file commits. missing for 10: evidence of versioning/reviewing/rolling back actual automation runs or agent actions (not just generic git files), independent hands-on confirmation of Repository Agent's commit/rollback behavior.", "evidenceIds": [ "working-copy-docs-14", "working-copy-docs-15", "working-copy-docs-16", "working-copy-docs-17", "working-copy-docs-18", "working-copy-docs-28", "working-copy-docs-29" ] }, { "productId": "working-copy", "storyId": "biometric-connection-auth", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "Working Copy documents that SSH keys can be stored in the Secure Enclave protected by Face ID or Touch ID, directly enabling biometric protection of remote (SSH) connections. However, this is limited to SSH key access specifically, with no evidence of biometric gating for HTTPS credentials or app-wide lock, and no independent/hands-on corroboration beyond the vendor docs. Missing for 10: evidence of biometric protection for HTTPS remotes, independent confirmation of the Face ID/Touch ID flow in practice, and details on fallback/security scope.", "evidenceIds": [ "working-copy-docs-8", "working-copy-docs-1", "working-copy-docs-20" ] }, { "productId": "working-copy", "storyId": "broadcast-commands", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Working Copy is a Git client for iOS, not a terminal/SSH multiplexer; grouping terminal sessions and broadcasting commands is outside its product category entirely.", "evidenceIds": [] }, { "productId": "working-copy", "storyId": "code-search-navigation", "verdict": "partial", "quality": 4, "confidence": "medium", "rationale": "Working Copy's docs confirm regular-expression search within file scope (wrapping pattern in slashes), and syntax-highlighted file browsing supports basic navigation, but there is no evidence of fuzzy matching or advanced filter options for code search. missing for 10: fuzzy matching support, filter options (by file type/path/date), evidence of broader project-wide search UI beyond regex.", "evidenceIds": [ "working-copy-docs-10", "working-copy-docs-3" ] }, { "productId": "working-copy", "storyId": "conversational-repo-agent", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "Working Copy's docs describe a 'Repository Agent' AI assistant you converse with to browse files, search content, read/modify files, commit, pull and push — directly matching the ai-native conversational insight story for repositories. However, there is no explicit mention of pull-request insights/management via this agent, and no independent/hands-on corroboration of the feature's real-world behavior. missing for 10: explicit pull-request conversational insight capability, independent/hands-on verification of the Repository Agent's conversational quality.", "evidenceIds": [ "working-copy-docs-29" ] }, { "productId": "working-copy", "storyId": "credential-vault-storage", "verdict": "partial", "quality": 5, "confidence": "low", "rationale": "Working Copy supports secure credential storage via Identities (SSH keys stored in the Secure Enclave, protected by Face ID/Touch ID, and can be imported/generated) and supports connecting to many host types (GitHub Enterprise, GitLab, Gitea, BitBucket, etc.), implying credentials could be reused. However, there is no explicit documentation confirming one Identity/credential can be attached to and reused across multiple different repositories or hosts simultaneously, nor any independent verification of this workflow. Missing for 10: explicit multi-host credential reuse documentation, independent/hands-on confirmation of cross-host credential sharing.", "evidenceIds": [ "working-copy-docs-8", "working-copy-docs-20", "working-copy-docs-9" ] }, { "productId": "working-copy", "storyId": "cross-app-file-access", "verdict": "full", "quality": 8, "confidence": "medium", "rationale": "Working Copy explicitly integrates with the iOS Files app and other apps' sandboxes: repositories appear in the Files app/document picker for 3rd party apps, external directories/document packages from other apps can be linked, files can be dragged in from email/other apps, and a built-in WebDAV server plus Shortcuts automation enable cross-app file flow. This directly matches accessing/working with files and repos across app sandboxes on-device. Missing for 10: independent hands-on verification of cross-app sandbox access beyond vendor docs.", "evidenceIds": [ "working-copy-docs-24", "working-copy-docs-25", "working-copy-docs-26", "working-copy-docs-27", "working-copy-docs-28" ] }, { "productId": "working-copy", "storyId": "customizable-terminal-appearance", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Working Copy is a mobile Git client with a file/diff viewer, not a terminal emulator; there is no terminal interface to customize font, colors, or cursor appearance. This axis is a category error for this product type.", "evidenceIds": [] }, { "productId": "working-copy", "storyId": "direct-p2p-connection", "verdict": "full", "quality": 8, "confidence": "medium", "rationale": "Working Copy documents direct git/ssh/https protocol support, including private self-hosted GitHub Enterprise, GitLab, and Gitea instances, with SSH keys stored in Secure Enclave — all indicating direct, non-relay connections to user-controlled servers. Community evidence shows users pairing it with self-hosted VPS git servers, corroborating real-world direct-connection use. missing for 10: independent technical verification that no intermediary/relay is used during sync, and explicit confirmation of raw SSH/git protocol (not tunneled) from a third party.", "evidenceIds": [ "working-copy-docs-1", "working-copy-docs-8", "working-copy-docs-9", "working-copy-docs-20", "working-copy-comm-6" ] }, { "productId": "working-copy", "storyId": "exit-node-routing", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Working Copy is a Git client for iOS; exit-node/network-routing capability is unrelated to its product category (a Git repository management app), not a Git or VPN networking feature.", "evidenceIds": [] }, { "productId": "working-copy", "storyId": "file-transfer-scp-sftp", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Working Copy is a Git client for iOS that supports git-over-ssh and SSH keys for authentication, but there is no evidence it offers general scp/sftp file transfer to arbitrary remote hosts — this is a Git-specific tool, not a general SSH file-transfer utility, making the scp/sftp axis a category mismatch.", "evidenceIds": [] }, { "productId": "working-copy", "storyId": "git-clone-protocols", "verdict": "full", "quality": 9, "confidence": "high", "rationale": "Working Copy's manual explicitly states support for https, ssh, git, and http protocols, plus SSH key management via Secure Enclave and identity attachment for authentication, and community evidence confirms real-world clone/pull/push usage over GitHub. Missing for 10: independent hands-on verification of the raw git:// protocol specifically and no dedicated troubleshooting/edge-case documentation.", "evidenceIds": [ "working-copy-docs-1", "working-copy-docs-8", "working-copy-docs-20", "working-copy-comm-1" ] }, { "productId": "working-copy", "storyId": "git-commit-graph", "verdict": "full", "quality": 8, "confidence": "medium", "rationale": "Working Copy has a dedicated Commit Graph feature accessible from the Repository screen explicitly for exploring repository changes across branches, plus supporting features like swipe-to-checkout old commits and branch-aware history operations. Missing for 10: independent hands-on review or screenshots corroborating the graph's usability/completeness across many branches.", "evidenceIds": [ "working-copy-docs-18", "working-copy-docs-14" ] }, { "productId": "working-copy", "storyId": "git-commit-push", "verdict": "full", "quality": 8, "confidence": "high", "rationale": "Working Copy's docs clearly describe the core commit-and-push workflow (staging/committing via the Changes/Status tab, pushing over https/ssh/git protocols, amend/squash, and a real user account of pulling, editing, and pushing on the go). Missing for 10: independent hands-on verification of push reliability/conflict scenarios beyond a single anecdote, and no first-party benchmark or detailed push-error handling documentation.", "evidenceIds": [ "working-copy-docs-1", "working-copy-docs-4", "working-copy-docs-9", "working-copy-comm-1" ] }, { "productId": "working-copy", "storyId": "git-commit-signing", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "Evidence shows Working Copy uses SSH keys (including Secure Enclave-backed keys) for authenticating to remotes, but nothing in the docs describes GPG or SSH commit signing/verification as a feature. Missing for 10: any mention of signed commits, GPG key support, or SSH-signature verification workflow.", "evidenceIds": [ "working-copy-docs-8", "working-copy-docs-20" ] }, { "productId": "working-copy", "storyId": "git-interactive-rebase", "verdict": "full", "quality": 8, "confidence": "high", "rationale": "Working Copy explicitly documents interactive history rewriting: delete commit, edit commit message, squash a commit with its child (docs-17), amend the latest commit (docs-16), and undo unpushed commits (docs-15). This directly covers deleting, editing, squashing commits as described in the story. Missing for 10: no explicit reordering/rebase-onto-arbitrary-commit UI mentioned and no independent hands-on corroboration of this specific feature beyond docs.", "evidenceIds": [ "working-copy-docs-17", "working-copy-docs-16", "working-copy-docs-15", "working-copy-docs-6" ] }, { "productId": "working-copy", "storyId": "git-merge-conflict-resolution", "verdict": "full", "quality": 8, "confidence": "medium", "rationale": "Working Copy's docs explicitly describe a dedicated 'Resolve tool' for handling merge conflicts across many files at once, directly matching the story. Missing for 10: independent/hands-on corroboration of the multi-file resolve workflow beyond vendor docs.", "evidenceIds": [ "working-copy-docs-7" ] }, { "productId": "working-copy", "storyId": "git-pull-request-creation", "verdict": "full", "quality": 8, "confidence": "medium", "rationale": "Working Copy's docs explicitly state it supports creating pull requests for BitBucket, GitHub and GitLab, directly from the mobile app, and also supports self-hosted GitHub Enterprise/GitLab/Gitea instances. This directly matches the story of creating PRs on hosted Git platforms from a device. Missing for 10: independent hands-on confirmation of the PR-creation flow itself (community evidence covers general git usage but not PR creation specifically).", "evidenceIds": [ "working-copy-docs-19", "working-copy-docs-9" ] }, { "productId": "working-copy", "storyId": "git-pull-request-review", "verdict": "partial", "quality": 4, "confidence": "low", "rationale": "Working Copy documents diff viewing, commit graphs, and syntax-highlighted file review, and notes it can create pull/merge requests for GitHub, GitLab, and BitBucket, which implies some PR-related workflow on mobile. However there is no explicit documentation of viewing PR discussion threads, inline review comments, or approving/merging PRs from the app. Missing for 10: dedicated PR review UI (comments, approve/request-changes, merge button), and independent hands-on evidence of reviewing PRs on the go.", "evidenceIds": [ "working-copy-docs-18", "working-copy-docs-19", "working-copy-docs-3", "working-copy-comm-1" ] }, { "productId": "working-copy", "storyId": "git-stash", "verdict": "full", "quality": 8, "confidence": "high", "rationale": "Official docs explicitly confirm stash/unstash via the repository context menu, directly matching the story's core requirement. Missing for 10: independent hands-on corroboration of the stash workflow beyond vendor docs.", "evidenceIds": [ "working-copy-docs-22" ] }, { "productId": "working-copy", "storyId": "git-submodules", "verdict": "partial", "quality": 5, "confidence": "low", "rationale": "Working Copy's docs explicitly mention Git submodule support, confirming the feature exists, but there is no detail on cloning with submodules, updating them, or managing (add/remove/sync) submodules, nor any community corroboration of real-world submodule workflows. missing for 10: documented submodule clone/update/init workflow, UI for managing submodule paths, independent user confirmation of submodule handling.", "evidenceIds": [ "working-copy-docs-23" ] }, { "productId": "working-copy", "storyId": "host-sync-across-devices", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "Working Copy is a single-device iOS git client; the evidence pack contains no mention of any cross-device sync feature (e.g. iCloud sync of hosts/identities/keys) for saved hosts or connection settings across devices, only per-repository git operations, SSH key storage in Secure Enclave, and file access mechanisms.", "evidenceIds": [] }, { "productId": "working-copy", "storyId": "inline-editor-lint", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "Working Copy is a Git client for iOS with syntax-highlighted file viewing and editing, but there is no evidence of a terminal-based editor or any integrated syntax/lint checker execution inside the app — no shell, no linting tools, no build/check runner mentioned anywhere in the docs.", "evidenceIds": [] }, { "productId": "working-copy", "storyId": "local-unix-commands", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "Working Copy is a git client for iOS with file browsing, syntax highlighting, and Shortcuts automation, but there is no evidence of a terminal or shell environment allowing execution of UNIX commands like ls, grep, cat, tar, or curl.", "evidenceIds": [] }, { "productId": "working-copy", "storyId": "manage-cloud-agent-tasks", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "Working Copy is a mobile git client with its own in-app AI 'Repository Agent' for local file/commit operations (working-copy-docs-29), but there is no evidence it can view, manage, or track tasks from cloud-based coding agents (e.g., a task queue, agent run status, or PR tracking from services like Codex/Copilot workspace). The story's specific axis of monitoring cloud agent task state is unaddressed.", "evidenceIds": [ "working-copy-docs-29" ] }, { "productId": "working-copy", "storyId": "mesh-vpn-access", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Working Copy is a Git client for iOS focused on repository management; it has no relevance to infrastructure access or Kubernetes clusters — this is a category mismatch, not a missing feature.", "evidenceIds": [] }, { "productId": "working-copy", "storyId": "multi-session-management", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Working Copy is a git client for iOS with no terminal/SSH-session feature; the story's axis of multiple terminal sessions with distinct context/appearance/history is a category error for this product type, which manages git repos rather than shell sessions.", "evidenceIds": [] }, { "productId": "working-copy", "storyId": "nl-to-shell-command", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Working Copy is a mobile Git GUI client with no shell/command-line interface; the natural-language-to-shell-command axis is a category error for this product. Its Repository Agent performs actions directly via conversation rather than generating shell commands.", "evidenceIds": [] }, { "productId": "working-copy", "storyId": "openness-api-parity", "verdict": "partial", "quality": 3, "confidence": "medium", "rationale": "Working Copy exposes automation via the Shortcuts app and a conversational 'Repository Agent' that can browse, search, read/modify files, commit, pull and push, giving some non-UI access to core git actions, but there is no documented REST/OpenAPI surface (probe shows no openapi.json, llms.txt, or machine-readable docs) proving full UI-parity for an AI-native/API consumer. missing for 10: a formal API/SDK spec covering all UI actions, evidence that Shortcuts actions cover every UI feature (branches, tags, submodules, resolve tool, etc.), and independent confirmation of Repository Agent's coverage.", "evidenceIds": [ "working-copy-docs-28", "working-copy-docs-29", "working-copy-probe-1", "working-copy-probe-2", "working-copy-probe-3" ] }, { "productId": "working-copy", "storyId": "openness-full-export", "verdict": "full", "quality": 7, "confidence": "medium", "rationale": "Working Copy stores all repository data as standard Git repositories (open format) and provides multiple export paths: Files app/document-picker access, drag-and-drop, a built-in WebDAV server, and Shortcuts automation, meaning a user can pull all data out in a non-proprietary format at any time (docs-24, docs-25, docs-27, docs-28). This directly satisfies 'export in open formats and leave' since Git itself is portable across any host. Missing for 10: no explicit single bulk-export/account-deletion feature described, and no independent hands-on account of a full data migration out of the app.", "evidenceIds": [ "working-copy-docs-24", "working-copy-docs-25", "working-copy-docs-26", "working-copy-docs-27", "working-copy-docs-28" ] }, { "productId": "working-copy", "storyId": "openness-open-license", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "Working Copy is a closed-source commercial iOS app; no evidence indicates its source code is available under any open license, and no repository or license file is mentioned anywhere in the evidence pack.", "evidenceIds": [] }, { "productId": "working-copy", "storyId": "openness-self-host", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Working Copy is a proprietary iOS git client app distributed via App Store, not a server/platform that could be self-hosted; self-hosting the 'core product' is a category error for this type of client application.", "evidenceIds": [] }, { "productId": "working-copy", "storyId": "privacy-data-residency", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Working Copy is a local iOS Git client where users choose their own Git remote/server (GitHub, GitLab, self-hosted, etc.); it does not offer a managed data-residency/region selection feature of its own, making this a category error for a client app rather than a hosted service.", "evidenceIds": [] }, { "productId": "working-copy", "storyId": "privacy-no-training", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "Working Copy's docs mention AI features that send staged diffs to OpenAI (working-copy-docs-5) and an AI Repository Agent (working-copy-docs-29), but there is no mention of any opt-out, data-retention policy, or control preventing that data from being used to train AI models. Since the product actively integrates third-party AI processing, this axis applies, but no evidence shows a training-data opt-out or privacy guarantee exists.", "evidenceIds": [ "working-copy-docs-5", "working-copy-docs-29" ] }, { "productId": "working-copy", "storyId": "privacy-retention-controls", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "Working Copy's docs mention AI features (commit-message suggestions, Repository Agent) that send data to OpenAI, but there is no evidence of any user-facing control over how long that data is retained by the AI provider, nor any deletion/export mechanism for AI-related data. The axis applies because the product ships AI features that transmit user data externally, but no retention/deletion controls are documented. Missing for 10: any documented retention policy, opt-out/delete mechanism for data sent to OpenAI, or user-facing controls over AI data lifecycle.", "evidenceIds": [ "working-copy-docs-5", "working-copy-docs-29" ] }, { "productId": "working-copy", "storyId": "privacy-telemetry-optout", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "No evidence in the pack addresses telemetry, usage tracking, analytics, or an opt-out setting for Working Copy; only AI commit-message and Repository Agent features mention sending data to OpenAI, with no privacy toggle documented. Missing for 10: any privacy policy or settings documentation on telemetry/analytics collection, and any opt-out mechanism.", "evidenceIds": [] }, { "productId": "working-copy", "storyId": "python-package-install", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Working Copy is a Git client for iOS with no terminal, shell, or Python runtime — installing pip packages is entirely outside its product category (a git/file-management app, not a code execution or package management environment).", "evidenceIds": [] }, { "productId": "working-copy", "storyId": "rendered-file-live-preview", "verdict": "full", "quality": 8, "confidence": "medium", "rationale": "Docs confirm preview of html/document files with syntax highlighting, plus explicit live-reload behavior that auto-reloads on file/asset changes while preserving scroll and zoom. Missing for 10: no independent/hands-on corroboration of live reload in practice and no explicit mention of Markdown-specific preview beyond 'html and document files'.", "evidenceIds": [ "working-copy-docs-3", "working-copy-docs-13" ] }, { "productId": "working-copy", "storyId": "secure-enclave-ssh-keys", "verdict": "full", "quality": 8, "confidence": "high", "rationale": "Working Copy's documentation explicitly states SSH keys can reside on the Secure Enclave protected by Face ID or Touch ID, directly matching the story's hardware-backed, biometric-protected key storage requirement. Missing for 10: independent/hands-on corroboration of this specific feature beyond first-party docs.", "evidenceIds": [ "working-copy-docs-8", "working-copy-docs-20" ] }, { "productId": "working-copy", "storyId": "session-persistence-mosh", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Working Copy is a Git client for iOS; it has no interactive terminal/SSH session feature to keep alive across network changes or sleep — this is a category error for this product type.", "evidenceIds": [] }, { "productId": "working-copy", "storyId": "ssh-key-auth", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "Docs confirm SSH remote support and private-key based Identities (importable or generated, storable in Secure Enclave), but no evidence specifies which key algorithms (Ed25519, ECDSA, RSA) are supported. Missing for 10: explicit documentation of supported key types/algorithms, independent confirmation of SSH auth working with each key type.", "evidenceIds": [ "working-copy-docs-1", "working-copy-docs-20", "working-copy-docs-8" ] }, { "productId": "working-copy", "storyId": "ssh-key-generation", "verdict": "full", "quality": 7, "confidence": "medium", "rationale": "Working Copy's docs state you attach a private key to an Identity which can be 'imported or generated inside the app,' and that SSH keys can be stored in the Secure Enclave protected by Face ID/Touch ID, directly enabling password-less SSH access to git servers. Missing for 10: independent/hands-on confirmation of the keygen flow and details on supported key types/algorithms.", "evidenceIds": [ "working-copy-docs-20", "working-copy-docs-8", "working-copy-docs-1" ] }, { "productId": "working-copy", "storyId": "ssh-quick-connect", "verdict": "partial", "quality": 5, "confidence": "low", "rationale": "Working Copy stores SSH identities/keys (optionally in Secure Enclave protected by Face ID/Touch ID) attached to a repository, which implies reconnecting to a saved remote doesn't require re-entering credentials, but this is git-remote SSH, not an interactive terminal session, and there's no explicit documentation of a one-tap 'connect to saved host' action or session reuse UI. Missing for 10: explicit one-tap host connection flow, interactive terminal/shell access evidence, and independent confirmation of credential-free reconnect behavior.", "evidenceIds": [ "working-copy-docs-8", "working-copy-docs-20", "working-copy-docs-1" ] }, { "productId": "working-copy", "storyId": "subnet-routing", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Working Copy is a Git client for iOS; subnet routing/VPN-style network access to reach remote devices is entirely outside its product category (a wrong axis, not a missing feature).", "evidenceIds": [] } ]