Add critical protocol definitions: Field Widget, Plugin Lifecycle, Driver Interface, and Trigger Context - #34

Add $notContains to StringOperatorSchema, FieldOperatorsSchema, Filter<T>,
FILTER_OPERATORS, VALID_AST_OPERATORS, and AST_OPERATOR_MAP with both
'notcontains' and 'not_contains' AST aliases.

Fixes #34

Co-authored-by: hotlong <50353452+hotlong@users.noreply.github.com>

Adds entries 26-40 covering the gaps that make the helpdesk template
'pretty but not daily-usable' from an end-user perspective:

P0 additions:
- #26 No inline message composer on detail pages
- #27 No external-user portal mechanism
- #28 Attachment/file-list field UI not E2E

P1 additions:
- #29 No 'changed since last visit' indicator
- #30 Bulk operations UI unverified (escalates #17)
- #31 Rich-text editor scoped to comments only
- #32 No first-class canned response / macro
- #33 No collaboration presence indicators
- #34 No keyboard-shortcut API
- #35 No conditional SLA timer (pause on waiting_customer)
- #36 Formula fields can't reference foreign object fields

P2 additions:
- #37 No chart drill-down
- #38 No period-over-period analytics primitive
- #39 No inbound-channel abstraction (email-to-ticket etc.)
- #40 i18n translation namespace validation weak

Includes 'user-pain → platform-gap' mapping table tracing each end-user
complaint to a specific issue number.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

…re it at +36 against the 358 ceiling (objectstack-ai#15265)

* docs(pm-skill): write the third platform-readings increment and measure it against the ceiling

Four members, each written in the file's voice and wrapped by the gate's own
`wrapLine` rather than by hand, so the counts are landing costs and not estimates:
the channel/input-scoped attribution-footer row, the MCP-side rate-refusal reading,
the CDN cause behind the payload channel's absence rule, and the Routine transport
family with its orphan-recovery path.

The ceiling row is deliberately NOT touched: raising it is a maintainer-floor act
and this change exists to give that ruling a measured number to size. The ratchet
is expected RED.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019RfFHiRCSs3JXLK4cwcfox

* docs(pm-skill): fold a fourth footer observation, measured by this flight, into the same row

Opening this PR over a raw REST create measured a combination none of the three
prior observations covered: the create end appended a SECOND session-URL footer
(a leading horizontal rule, exactly +90 bytes, the sent body a strict prefix of
the stored one) rather than the bare form the edit end appends. The row now says
the append shape varies by channel AND by action, and still refuses to state a law.

Re-measured after the change: the member costs 12 lines instead of 9, so the
increment is +39 rather than +36.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019RfFHiRCSs3JXLK4cwcfox

* tooling(pm): raise the platform-readings ceiling to 397 on the ruling, as an ordinary ruled raise

The maintainer sized the third increment at the measured +39 (decision batch objectstack-ai#34,
item 1 = A). The ceiling row moves 358 to 397 and carries the ruling verbatim
beside it, with the four members and their line counts, the same way the row above
carries the previous one.

The move declaration takes a SECOND `ruledRaises` record rather than a carried-
forward `was`: an ordinary ruled raise is the maintainer's, so it is subtracted
before the move is priced. `was` stays at this file's literal pre-move 314, and the
verdict reads +10 (314 to 397, less 73 lines of ordinary ruled raise) against the
same net source decrease of 11.

Item 2 of the ruling is C: the two quota sentences left in tension stay exactly as
written, pending a discriminating read. Neither is edited.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019RfFHiRCSs3JXLK4cwcfox

---------

Co-authored-by: Claude <noreply@anthropic.com>