Update to trackly

Changed files

Choose a file to see its text changes. Binary or large files show metadata only.

.codex-plugin/plugin.json →

skills/trackly-apply/SKILL.md →

skills/trackly-apply/references/lifecycle-contract.md →

skills/trackly/SKILL.md →

.codex-plugin/plugin.json

− removed · + added

--- before
+++ after
@@ -24,12 +24,12 @@
   },
   "name": "trackly-openai",
   "skills": "./skills/",
-  "version": "1.0.7",
+  "version": "1.0.8",
   "mcpServers": "./.mcp.json",
   "extensions": {
     "com.openai": {
       "publication": {
-        "release_notes": "Guide users through missing Apply profile and default resume requirements, preserve saved answers, confirm the current profile revision, and refetch readiness after each save. Add current browser handoff compatibility and profile lookup checks. Existing dedicated OpenAI tools, OAuth access, account isolation and manual submission boundaries remain unchanged."
+        "release_notes": "1.0.8: keep Apply bound to the exact jobs a user selects, preserve their order and support safe replay of the same selection. Stop with an upgrade explanation if the service cannot honor exact selection; never broaden it to other saved jobs. Dedicated OpenAI tools, OAuth permissions, account isolation and manual submission remain unchanged."
       },
       "review": {
         "test_cases": {
@@ -54,8 +54,8 @@
             },
             {
               "description": "apply-to-review",
-              "prompt": "Use trackly Apply for my next approved saved job, show the saved resume first, and stop before Submit.",
-              "expected_behavior": "Use a currently available approved saved posting and the confirmed reviewer profile. Inspect and bind the visible employer browser. Ask permission to enter the reviewer details, explain possible autosave, and wait for an explicit user answer before entering data. Fetch only the profileKeys required by that form through trackly_get_apply_snapshot with flat executionId, memberIds, browserSurface and profileKeys arguments. Preview the exact original saved resume and request explicit approval of that file. Attach only if the host supports secure original-file retrieval and upload; otherwise explain the manual-upload fallback. The automatic branch calls trackly_approve_apply_resume and trackly_record_apply_observations separately; the manual branch records approval and requires visible filename confirmation without claiming automatic transfer. Verify committed fields and attachment evidence. Obtain final truth confirmation and certify readiness only after required evidence passes, then refetch durable state. If the host blocks a lifecycle call, report that the browser action succeeded separately from the unrecorded Trackly status; do not claim certification or retry through another account. Preserve the editable employer form for the user. Never submit, invent missing answers, or infer attachment from preview or approval. If the job is closed or inaccessible, report it and ask for another approved job.",
+              "prompt": "Use trackly Apply for the exact saved job I select, show the saved resume first, and stop before Submit.",
+              "expected_behavior": "Ask the reviewer to select one actual returned saved job ID. Call trackly_start_or_resume_apply with jobIds containing only that approved ID and target=1, then verify every returned member belongs to that exact job; do not replace an unavailable selection or retry with a count-only queue. Use the confirmed reviewer profile. Inspect and bind the visible employer browser. Ask permission to enter the reviewer details, explain possible autosave, and wait for an explicit user answer before entering data. Fetch only the profileKeys required by that form through trackly_get_apply_snapshot with flat executionId, memberIds, browserSurface and profileKeys arguments. Preview the exact original saved resume and request explicit approval of that file. Attach only if the host supports secure original-file retrieval and upload; otherwise explain the manual-upload fallback. The automatic branch calls trackly_approve_apply_resume and trackly_record_apply_observations separately; the manual branch records approval and requires visible filename confirmation without claiming automatic transfer. Verify committed fields and attachment evidence. Obtain final truth confirmation and certify readiness only after required evidence passes, then refetch durable state. If the host blocks a lifecycle call, report that the browser action succeeded separately from the unrecorded Trackly status; do not claim certification or retry through another account. Preserve the editable employer form for the user. Never submit, invent missing answers, or infer attachment from preview or approval. If the job is closed or inaccessible, report it and ask for another approved job.",
               "tools_triggered": "trackly_get_apply_readiness, trackly_start_or_resume_apply, trackly_get_apply_progress, trackly_get_apply_snapshot, trackly_get_job, trackly_bind_apply_surface, trackly_approve_apply_resume, trackly_record_apply_observations, trackly_prepare_resume_artifact, trackly_certify_review_ready"
             },
             {