curviate-jobs

原文涵盖的主题

• Curviate: job postings and applicants
• Before any command
• The commands
• job create: the required set
• Traps
• A safe posting flow
• Full command surface
• Exit codes to branch on here

Every posting starts as a draft. Drafts are free and reversible; publishing is neither. The two things that surprise agents here are that a free publish is still subscription-gated and that an update's read-back lags the write. Command surface established against CLI 0.33.0. Credentials resolve flag > environment > stored profile (CURVIATEAPIKEY, CURVIATEBASEURL, CURVIATEACCOUNT). --profile picks the stored credential set; --account picks which connected LinkedIn account owns the posting. --preview before every write, and especially before a publish. On a read command it is refused with exit 2. --json on anything you parse; --fields a,b,c to project; --verbose when a slim response looks suspiciously empty. Put global flags at the end of the command. Branch on the exit code, never on prose. See the table at the end. These are not retrieval-mode commands: --mode/--max-age are refused here with unknown flag, exit 2. job publish --mode is a different flag with the same name: it selects a publishing publishing mode and can spend real money. See curviate-profile for retrieval mode. | Command | What it does | Confidence | |---|---|---| | curviate job get | One public posting's full detail

这里只展示节选，请以完整原文和当前要求为准。