mapps code:logs reference table has incorrect flag descriptions and casing

[idand-boost]

Summary

The logs.md reference file in the monday-code-ops skill contains several inaccuracies compared to the actual CLI behavior of mapps code:logs. The official mapps CLI
docs are correct — the errors are only in this repo's reference table and examples.

Issues found

1. -s and -t are effectively required (not optional)

Omitting either -s or -t triggers an interactive prompt, breaking non-interactive usage that is relevant for coding agents. Both must always be specified explicitly.

2. History casing is wrong — must be history (lowercase)

The table listed History as the accepted value for -s, but the CLI only accepts history (lowercase).

3. -f, -e, -r are required for -s history, not -s live

The table said these flags were "only with -s live", but the opposite is true:

• -s history requires -f and -e to return any logs
• -s history prompts for -r interactively — pass "" to skip
• -s live does not require any of these flags

4. -r does not work — fails silently with -s live, does not filter with -s history

The -r flag is described as a regex search filter but does not work in either mode:

• With -s live: passing -r causes the command to fail silently — no logs are returned at all
• With -s history: the command runs but returns all logs regardless of the value passed to -r

Fix

Updated logs.md with correct flag descriptions, casing, and examples that always include all required flags to avoid interactive prompts.

[stasyu2009-ux]

https://docs.github.com/en/site-policy/github-terms/github-terms-of-service