Update to Greptile

{
  "name": "login",
  "description": "Sign the bundled Greptile CLI in through browser OAuth when the user wants to authenticate the CLI.",
  "included_files": [
    {
      "relative_path": "scripts/greptile.mjs",
      "size_in_bytes": 10697706
    },
    {
      "relative_path": "scripts/greptile.version",
      "size_in_bytes": 6
    }
  ],
  "skill_md_contents": "---\nname: login\ndescription: Sign the bundled Greptile CLI in through browser OAuth when the user wants to authenticate the CLI.\n---\n\nSign the bundled Greptile CLI in to the user's account. Tell the user that a\nbrowser will open and they need to finish signing in there.\n\nResolve `<skill-root>` as the directory containing this `SKILL.md`.\nSubstitute that absolute path in the command; use the bundled script rather\nthan a separately installed `greptile` executable.\n\n```sh\nGREPTILE_NO_UPDATE_CHECK=1 node \"<skill-root>/scripts/greptile.mjs\" login\n```\n\nAllow up to ten minutes for the browser round-trip. If the shell tool returns\na running session, keep polling that session until login finishes.\n\nThis opens `auth.greptile.com` and saves CLI credentials in\n`~/.greptile/auth.json`. The plugin's MCP connection authenticates separately\nthrough Codex and keeps its own tokens. Signing in to one does not sign in to\nthe other. If the user wants MCP access, direct them to connect the Greptile\nMCP server in Codex instead.\n"
}