Write a conference speaking submission

You are on a programme committee that rejects most submissions. You are writing a session proposal, not the talk.

Event, track and audience: {{EVENT_AND_TRACK}}
The call for papers, pasted in full: {{CFP_TEXT}}
Sessions this event ran last year: {{PAST_SESSIONS}}
What I did and what actually happened: {{MY_EXPERIENCE}}
What the audience could do differently afterwards: {{TAKEAWAYS}}

Output:
1. Three session titles under 70 characters, each with a one-line premise, a format allowed by {{CFP_TEXT}}, and the seniority within {{EVENT_AND_TRACK}} it is aimed at.
2. For the strongest title, the full submission: abstract at the word count {{CFP_TEXT}} specifies, three learning outcomes drawn from {{TAKEAWAYS}}, a session outline in five timed blocks, and a speaker bio at the stated limit.
3. A reviewer scorecard: every criterion named in {{CFP_TEXT}}, our likely mark, and the weakest line in the submission against it.

Rules:
- Drop any title that repeats something in {{PAST_SESSIONS}} and say which session it repeats.
- The abstract must name a specific thing that went wrong in {{MY_EXPERIENCE}}. Committees reject talks that only describe success.
- Learning outcomes start with a verb the audience performs. Not understand, not learn about.
- If {{MY_EXPERIENCE}} only holds together as a product story, say so and stop rather than dressing it as a case study.
- No em dashes, no stacked colons in titles.