EPILIBS-211: Task create contract — payload.target, failSafeTermination type, privilege docs

[mpqmpqm]

What

Contract catch-ups in taskAdapter (EPILIBS-211):

1. payload.target ('APPLICATION' | 'PROXY', EPICENTER-6729) typed on create and both HTTP payload views (read view echoes lowercase). Previously it only worked by sneaking through the payload spread; TypeScript callers had to pre-declare objects to dodge excess-property checking.
2. failSafeTermination: number → string (ISO-8601) — the wire format the server consumes and echoes, and what the docstring already claimed. Callers today carry toISOString() as unknown as number casts.
3. Privilege docs: every method said "requires support level authentication"; the Task API resource is @Facilitator-gated end to end. The old wording pushes integrators toward unnecessary shared-secret proxy plumbing. Also documented that payload.url is relative and how the runner builds the fire URL ({host}{targetPath}/{account}/{project}{url}).

Verification

• npm run test:run: 1001 passed, including new specs asserting target passes through to the request body (and is absent when omitted); optionals spec now sends an ISO-8601 failSafeTermination.
• npm run type-check clean.
• Live: built dist/cjs, created a task on epicenter-sandbox-1 with target: 'PROXY' and an ISO failSafeTermination using a facilitator session — server echoed target: 'proxy' and the ISO timestamp; probe task destroyed afterward.

Notes

failSafeTermination: number → string is a type-level break for TS callers who passed epoch millis; the ISO string is the only wire format we have verified working against the live API.

🤖 Generated with Claude Code

[gemini-code-assist]

Code Review

This pull request introduces an optional target field to HTTP task payloads, allowing tasks to target either the application or a proxy server. It also updates the documentation to reflect that task operations require facilitator privileges, changes the failSafeTermination option type from a number to an ISO string, and adds corresponding unit tests. The review feedback recommends allowing both uppercase and lowercase values for the input target types to prevent TypeScript compilation errors when developers attempt to reuse or round-trip retrieved payloads.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[gemini-code-assist]

Since the read view (HttpTaskPayloadReadOutView) returns lowercase values ('application' | 'proxy'), typing the input strictly as uppercase ('APPLICATION' | 'PROXY') will cause TypeScript compilation errors when developers attempt to round-trip or reuse a retrieved payload. To improve developer experience and allow flexibility, consider allowing both uppercase and lowercase values in the input types.

Suggested change

	target?: 'APPLICATION' | 'PROXY';
	target?: 'APPLICATION' | 'PROXY' | 'application' | 'proxy';

[gemini-code-assist]

Since the read view (HttpTaskPayloadReadOutView) returns lowercase values ('application' | 'proxy'), typing the input strictly as uppercase ('APPLICATION' | 'PROXY') will cause TypeScript compilation errors when developers attempt to round-trip or reuse a retrieved payload. To improve developer experience and allow flexibility, consider allowing both uppercase and lowercase values in the input types.

Suggested change

	target?: 'APPLICATION' | 'PROXY';
	target?: 'APPLICATION' | 'PROXY' | 'application' | 'proxy';