PR #48 - getformo/cli

Why

incur boolean flags do not consume the following token. --flag false sets the flag to true and leaves false as a stray positional argument, so every documented example did the opposite of what the reader asked for.

Verified against incur's parser:

Written	Parsed
`--include-in-pipeline false`	`true` ← the documented form
`--include-in-pipeline`	`true`
`--include-in-pipeline=false`	`false`
`--no-include-in-pipeline`	`false`

What changed

Fixed the broken example. SKILLS.md told readers to exclude a contract from the pipeline with formo contracts update <chain> <address> --include-in-pipeline false, which included it instead. Added a note on both affected flags (--include-in-pipeline, --is-public).
Corrected the --include-in-pipeline description. It read "true by default in the API". The API default is decode-only (false), and after getformo/formono#2251 an omitted field preserves the stored value rather than resetting it.
Clarified --is-public on create (defaults to private) and update (omitting preserves the stored value).
Extended the incur patch so rendered --help examples emit --flag / --flag=false instead of --flag false, which stopped the CLI's own help from teaching the wrong syntax. This follows the existing patch precedent in this repo for incur's flag rendering.

Companion to getformo/formono#2251, which makes an omitted include_in_pipeline on PUT /v0/contracts/{chain}/{address} preserve the stored value instead of silently disabling pipeline ingestion.