Fix misleading docstring for get_remaining_cost() regarding terminal cost

[Copilot]

Description

The get_remaining_cost() docstring claimed to include OMPL's terminalCost in its calculation, but the implementation only accumulates motion costs. This is correct behavior since our objectives don't override terminalCost (defaults to 0), but the docstring was misleading.

Updated ompl_path.py docstring to:

• Clarify that only motion costs are accumulated, not terminal/initial costs
• Document the zero-cost assumption explicitly
• Note that future non-zero terminal/initial costs require implementation updates

Key distinction: OMPL's terminalCost is an additional cost applied to the final state, not the cost of the last waypoint itself.

Verification

• Docstring now matches implementation behavior
• Code review passed
• Security scan passed

Resources

• Original PR: Raghumanimehta/778 get cost #798
• Review comment: Raghumanimehta/778 get cost #798 (comment)

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[Copilot]

Just as a heads up, I was blocked by some firewall rules while working on your feedback. Expand below for details.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• ompl.kavrakilab.org
  • Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node /home/REDACTED/work/_temp/ghcca-node/node/bin/node --enable-source-maps /home/REDACTED/work/_temp/copilot-developer-action-main/dist/index.js (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)