§5 Sarıoğlu: typo, PR-list framing, accurate AT-spec ratios
- Fix 'Unfortunaltely I don't have a ai logs myself' -> 'Unfortunately,
I do not have AI prompt logs preserved' (item 6).
- Item 4: clarify that the 28-PR inline list is the Final-Milestone-
window subset, not the full 70; the lifetime 70 spans #70 (2026-03-12)
to #604 (2026-05-13), with the link to the complete gh-pr-list query
surfaced one line earlier.
- Item 2: 'Two-thirds of the Final-Milestone Playwright surface' was
off — 8 of 13 specs (62%), not two-thirds. Replace with the exact
ratio.
- Item 8: '8 of 14 Final-Milestone Playwright specs' -> '8 of the 13'
to match item 2 and the actual frontend/e2e/specs/ count (AT-01..07
+ AT-17..22).
af12b25
§5 Sarıoğlu: correct authored-and-merged PR count 27 -> 70
The 27 was the size of the partial inline list I called out in item 4,
not the authored-and-merged total. Verified via 'gh pr list --author
mehmetborasarioglu --state merged --limit 200' which returns 70 rows
ranging from #70 (2026-03-12) to #604 (2026-05-13). Updated both the
headline scope in item 2 and the by-the-numbers footer in item 8.
21df472
§5 Sarıoğlu: surface PR / commit evidence and impact framing
Make the individual-contributions section earn its weight by:
- prefixing item 2 with a headline scope (27 authored PRs, ~35 formal
reviews, full ownership areas) and inlining the matching PR refs
into every bullet (social feed, three advanced rankers, reporting +
admin, mentorship + visibility, prod infra, AT specs)
- expanding item 5 from 2 incidents to 4 (Flyway collision,
JaCoCo/ByteBuddy, prod Swagger + nginx, AT-02/07 framer-motion
reduced-motion fix), each with the resolving PR / commit
- tightening item 7 with the actual Surefire and Playwright numbers,
the two JaCoCo class-level gates I added on top of the build, and
the post-merge curl-smoke pass
- using item 8 (previously empty) for a five-line What-I-Shipped
summary and a by-the-numbers footer
ae78d7c
§5 Sarıoğlu: fold PR-thread engagement into the formal-review list
Per team merge policy, every comment-review on the Files-Changed
surface gated a teammate's merge (a 'changes needed' comment was a
hard block), so the previous split between 'Formally reviewed' (5
Beratcan branches with explicit Approve / Request-Changes) and
'Engaged in PR-thread discussion' (~30 other merged PRs) understated
the actual review surface. Consolidate the two lists into a single
'Formally reviewed' section grouped by layer (Backend / Web / Mobile /
E2E) and update the matching item-2 bullet so the totals line up.
e66f994
§2: bump Sequence Diagrams pointer from 8 to 12 workflows
Reflect SD-9..SD-12 (meeting lifecycle, end-mentorship + rating, task
cycle, follow + Neo4j + push) that were added to the Sequence-Diagrams
(Final) wiki page in commit ba51800.
036cd99
§4.6: surface HTML test reports per rubric (XML + HTML for all 3 layers)
The Final Milestone report rubric requires every layer's test results
in both JUnit XML (machine-readable) and HTML (human-readable) form.
The XML side was already linked; the HTML side existed in the wiki
repo but was unlinked — add an HTML column to the headline table and
a 'Direct HTML report downloads' subsection covering Surefire (Backend),
Vitest (Web unit), Playwright (Web E2E), and Jest (Mobile). Each entry
provides a htmlpreview.github.io rendered link plus the raw file URL,
and the Playwright multi-file report gets an explicit clone-and-open
recipe since htmlpreview can't follow relative subfolder fetches.
Also cites the latest CI E2E run (46 passed, 0 failed) alongside the
local Playwright numbers.
b344967
Updated Final Milestone Deliverables (markdown)
99320a8
Updated Final Milestone Deliverables (markdown)
c3b87fe
§4.6: embed direct raw-URL links to JUnit XMLs
GitHub's wiki sidebar only lists .md pages, so the JUnit XML reports
were invisible to readers even though the files are committed to the
wiki repo. Surface them via raw.githubusercontent.com/wiki/... links
for every single-file XML plus 8 representative backend samples, and
add a clone command for the full 240-file backend set.
28edb98
Sequence-Diagrams (Final): add SD-9..SD-12 (meeting, end+rate, task cycle, follow+Neo4j)
ba51800
Updated Final Milestone Deliverables (markdown)
45ea1a5
Updated Final Demo Reflections (markdown)
2666db8
Updated Final Milestone Deliverables (markdown)
4d57e02
Updated Final Milestone Deliverables (markdown)
122700d
Updated Final Milestone Deliverables (markdown)
a30de85
Updated Final Milestone Deliverables (markdown)
b8b04ac
Class/Sequence diagrams (Final): drop intro/notation/source-link prose
Keep the pages focused on the embedded PNG renders. Each block now
goes title -> heading -> one-sentence description -> diagram, with no
intervening notation explainer or source-link footer.
2d79ba2
Updated Final Milestone Deliverables (markdown)
6d5076b
§4.4: embed 19 web screenshots organised by feature area (Discovery / Social Feed / Mentee Profile / Active Mentorship / Messaging / Reporting / Admin Console); §4.1 Sarıoğlu row: tighten to a concise summary, move issue numbers out of prose into the PRs/Issues column
adf5e2e
Final-Demo-Notes + Final-Demo-Reflections: write both pages per §4.7 — Notes mirrors the reconstructed timeline / Q&A / not-presented list / action items; Reflections covers what went well, what did not, three lessons (planning the demo / role-play + rehearsal / constant communication and feedback), and forward action items
7a9f2f2
Updated Final Milestone Deliverables (markdown)
d1a4f95
§5 (Sarıoğlu) — replace three 'I wrote sub-section X' entries with three substantively different non-code items: #424 wiki-report coordination, #310 Lab 9 + AT catalogue authorship, #490 W3C standards adoption
5428e8f
Updated Final Milestone Deliverables (markdown)
beefb0c
§4.3 Scenario 3 step 2 (For-You feed): un-truncate response; show 5 representative ranked posts + full pageable envelope
11df8fb
§5 (Sarıoğlu) — PR section now splits into Authored & merged / Formally reviewed (5 PRs, all Beratcan) / Engaged in PR-thread discussion (selection across backend/web/mobile/E2E)
f32da84
§5 (Sarıoğlu): drop Additional Information bullet; §4.1: clarify formal-review (5 PRs, all Beratcan's) vs comment-thread engagement (~35 across team)
aefafff
§4.2: drop duplicate advanced-ranker rows; fold their content into the base 1.1.2.1 and 1.1.7.3 rows so each SRS ID has one canonical entry
4b35027
§4.2: mark advanced For-You ranker (Thompson-sampling bandit) and advanced mentor ranker (MMR + LLM explanations) as Completed; both ship on main with JaCoCo coverage gate
aa20a8a
§5 (Sarıoğlu): note overall backend branch coverage >95% and enumerate the two JaCoCo class-level gates that fail the build
8a914c4
Use-Case-Diagram-(Final): split into 5 per-actor diagrams (Guest, Mentee, Mentor, Admin, System / Scheduler) for readability; combined diagram kept as cross-reference
66655e8