Hub
mobile-ground-truth
Four mobile commands that answer from the tree and the toolchain rather than from memory: API availability, crash triage, upgrade impact, privacy declarations.
Install
Staged first, the resolved commit pinned in .arcturn-install.json, then linked into the roots Arcturn scans. Nothing is linked before the pin.
To see the table below derived from the package itself rather than from this entry, run arcturn inspect sitharaj88/arcturn/kits/mobile-ground-truth — it stages exactly as an install would, links nothing, and prints what it would add.
Source
- Maintainer
- Sitharaj Seenivasan
- Contents
- 4 skills
Usage
What you would type
Every command this package adds, in the form you would run it. A slash command is invoked by its own name; a pipeline goes through /workflow.
/api-checkAnswer whether an API exists in the SDK you build against and whether it runs on the oldest OS you ship to, from files on this machine, never from memory./crash-triageTriage a mobile crash only when the trace is symbolicated and its symbols proven to match the shipped build; otherwise name what is missing and stop./privacy-declarationsDraft the privacy-manifest and data-safety inputs a store asks for from what the code evidences, marking everything unevidenced as undeclarable./upgrade-impactReport only the breaking changes in an upgrade that actually occur in this repository, with the compiler's own deprecation output as the evidence.
Disclosure
What this would add to your machine
Read in the same vocabulary the installer uses: derived lanes, declared tools, stage counts, budgets, and whether any of it is executable code.
Skills
4
- /api-check
- /crash-triage
- /privacy-declarations
- /upgrade-impact
No executable code disclosed
This entry declares no extensions/. Verify it against the package itself with arcturn inspect — and note that the installer would confirm-gate executable code either way, whatever a listing says.