fix(describe-ui): Add point option support

[cameroncooke]

Add the documented describe-ui --point <x,y> option and route point lookups through the simulator accessibility API.

The issue here was a contract mismatch: the docs already described --point, but the CLI help and runtime implementation only exposed full-tree describe-ui. This change makes the command surface, runtime behavior, and shipped skill docs agree, and adds stronger automated coverage around the point-specific payload shape returned from the simulator.

I kept the fix narrow. The command still uses the existing accessibility fetch path, but now calls the point-specific simulator API when --point is provided. I also updated the E2E test to assert the stable shape of the returned accessibility object rather than only checking that BackButton appeared somewhere in the output.

Fixes #38

---

Note

Medium Risk
Changes describe-ui runtime behavior and output shape when --point is used by routing through a different simulator accessibility API, which could affect downstream tooling/tests relying on previous output.

Overview
Implements the documented describe-ui --point <x,y> flag, including argument validation, and routes point lookups through FBSimulator.accessibilityElement(at:nestedFormat:) while preserving full-tree behavior when omitted.

Updates shipped skill docs and the CHANGELOG, and expands test coverage to assert the flag appears in help output, rejects invalid formats, and validates the single-element JSON payload returned for a targeted point (including updated JSON parsing helpers to handle object-vs-array results and additional fields like AXUniqueId).

^{Written by Cursor Bugbot for commit 17a3997. This will update automatically on new commits. Configure here.}

[coderabbitai]

Walkthrough

This pull request implements the --point option for the describe-ui command, enabling coordinate-based accessibility element inspection. Changes include exposing the point parameter in the DescribeUI command structure with validation logic for x,y coordinate parsing; updating AccessibilityFetcher to conditionally fetch a single element at a specified point or all elements; documenting the feature in SKILL.md guides; expanding UIElement test utilities with additional properties and parsing functions to handle both single elements and arrays; and adding test coverage for help output validation, invalid point format handling, and point-based element retrieval. The CHANGELOG records this implementation for issue #38.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and specifically describes the main change: adding point option support to the describe-ui command.
Linked Issues check	✅ Passed	All code changes directly address issue #38's objective of adding the --point option to describe-ui, including help output, runtime behavior, and documentation updates.
Out of Scope Changes check	✅ Passed	All changes are within scope of issue #38: exposing the --point option, routing point lookups through the simulator API, updating documentation, and adding comprehensive test coverage for the feature.
Description check	✅ Passed	The pull request description clearly relates to the changeset, documenting the addition of the describe-ui --point option and its implementation.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

📝 Coding Plan

• Generate coding plan for human review comments

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

Skills/CLI/axe/SKILL.md (1)

75-75: ⚠️ Potential issue | 🟡 Minor

Inconsistency: "Every command" contradicts earlier guidance.

Line 8 states that commands like list-simulators and init do not require --udid, but line 75 says "Every command includes --udid". The sibling file Sources/AXe/Resources/skills/axe/SKILL.md correctly says "Every simulator-interaction command includes --udid" on its corresponding line.

Suggested fix

 Before finalising guidance, verify:
-- Every command includes `--udid`.
+- Every simulator-interaction command includes `--udid`.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@Skills/CLI/axe/SKILL.md` at line 75, The sentence "Every command includes
`--udid`" is inconsistent with earlier guidance and the sibling doc; update the
phrase in SKILL.md (the occurrence of "Every command includes `--udid`") to read
"Every simulator-interaction command includes `--udid`" so it matches the
earlier note that commands like `list-simulators` and `init` do not require
--udid.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Outside diff comments:
In `@Skills/CLI/axe/SKILL.md`:
- Line 75: The sentence "Every command includes `--udid`" is inconsistent with
earlier guidance and the sibling doc; update the phrase in SKILL.md (the
occurrence of "Every command includes `--udid`") to read "Every
simulator-interaction command includes `--udid`" so it matches the earlier note
that commands like `list-simulators` and `init` do not require --udid.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 013a23fb-1bb6-48c9-a14b-f5ac90cbb9c6

📥 Commits

Reviewing files that changed from the base of the PR and between 051e73e and 17a3997.

📒 Files selected for processing (7)

• CHANGELOG.md
• Skills/CLI/axe/SKILL.md
• Sources/AXe/Commands/DescribeUI.swift
• Sources/AXe/Resources/skills/axe/SKILL.md
• Sources/AXe/Utilities/AccessibilityFetcher.swift
• Tests/DescribeUITests.swift
• Tests/TestUtilities.swift