Move release notes to the deploy projects; drop the wiki page Release notes are per-artifact and per-version - each deploy-mf-* project ships the notes for the version it delivers - so a single wiki page cannot coherently track them and would rot. Remove the Release-Notes placeholder and its sidebar entry; add a pointer in Deployment: Basics ("Staying current") noting that each deployment project ships its own release notes; inline the release-tag convention in JMS App Dev where it used to link the removed page. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01L52U3EycDjN8uLAYL79HJ9
Add Worked Example: SimpleSubscriber (verbatim cut-and-paste methods from the SDK source); sidebar + Develop-JMS link
Develop-JMS: add Application design section (off-callback-thread processing, cache pattern, publish-off-session-thread, GUI thread marshalling) from guide 5.5/5.6
Review edits: Develop-JMS entitlements intro (no S&E, no conflation) + STREAM_UPDATE; Entitlements page use-case framing (self=own identity, proxy=on behalf of end-user) + drop S&E link; Conventions: CORRECTION/RESET marked unused + moved down, expanded multi-stream from guide 5.4
Draft Dynamic Data Conventions (message types, stream state, header properties, multi-stream) and Entitlements Context (comma-delimited context, self/proxy + code-based use-cases, status-only); sidebar + Develop-JMS entitlements link
Develop-JMS revisions: jakarta namespace; latest-clone + tag note; mf-session connect + alias note; MarketData view/multi-key callout; expanded selectors; conventions section + new Dynamic Data Conventions page; entitlements note; Elastic MDS (v6) / context wording. Quick Start clone -> latest
Draft Develop-JMS (verified context model: v5 feed.symbol vs MarketData schema-qualified; selectors; message types; v5 compat). Tighten Glossary Context entry
Scaffold Elastic MDS wiki: Home, sidebar, footer, page stubs for the full doc set