Update to eHour

{
  "description": "Review, submit, cancel, or resubmit your eHour timesheet, or check team submission status. Use for eHour approval and missing-submission questions.",
  "included_files": [],
  "name": "timesheets",
  "skill_md_contents": "---\nname: timesheets\ndescription: Review, submit, cancel, or resubmit your eHour timesheet, or check team submission status. Use for eHour approval and missing-submission questions.\n---\n\n# Review and submit eHour timesheets\n\nUse the connected eHour tools and inspect their live schemas. If the connection\nis unavailable, ask the user to connect eHour. Reuse IDs returned by the server;\ndo not invent approval, user, or team IDs.\n\n## Review and submission\n\nUse `getTimesheet` for the requested inclusive date range. Summarize recorded\nhours by day or project as useful, and distinguish tracked time from approval\nstate. Missing entries do not establish the user's expected working hours.\n\n“Review,” “check,” and “prepare” do not authorize submission or time changes.\n`submitTimesheet` is for the caller's own timesheet and requires an explicit\nsubmission request. It expands partial ranges to full weekly or monthly\napproval periods according to tenant configuration. Inspect the approval\ntimeframes in `getTimesheet`; clarify if the actual period exceeds what the\nuser intended. Report the returned periods and status, not an assumed approval.\n\nFor an explicit cancellation, obtain `approvalId` from `getTimesheet.approvals`\nand use `cancelTimesheetSubmission`. For an explicit resubmission, correct only\nthe requested entries, then use `resubmitTimesheet` on the rejected record.\nThese actions are self-only. Do not promise that this plugin can approve or\nreject somebody else's timesheet; the inspected server has no such tools.\n\nAfter an uncertain submission result, read current approval state before\nretrying. Surface conflicts and locked periods; do not cancel another\nsubmission merely to make a new one succeed.\n\n## Who has submitted?\n\nUse `listSubmissionStatus`, with the requested date range and team or user\nfilter. User and team filters cannot be combined. Resolve a team with\n`listTeams` when needed. Do not fan out from `listUsers` to individual\ntimesheets: the submission-status tool already returns per-person status.\n\nFor an organization-wide request, query the visible teams and deduplicate\npeople appearing in multiple teams. Describe the result as coverage of the\naccessible teams: users outside teams or outside the caller's management scope\nmay be missing. Do not claim full organizational coverage without evidence.\n\nKeep not submitted, pending, rejected, and approved states distinct. A report\nof tracked hours cannot prove submission status, and zero hours alone does not\nprove a missing submission. Never disclose people outside the returned scope.\n"
}