Skip to content

History

Revisions

  • §5 (Sarıoğlu): rewrite AI Transparency to reflect the actual four-step Claude workflow; drop empty prompts-log link

    @mehmetborasarioglu mehmetborasarioglu committed May 16, 2026
    9883130
  • Final Milestone Deliverables: §2 + §4.1 (Sarıoğlu row + Aslan note) + §4.2 + §4.3 + §4.5 + §5 (Sarıoğlu) + final UML diagrams + test reports - §2 Project Documentation: link to Requirements wiki page + new UML Diagrams (Final) wiki pages - §4.1 Team Contribution: populated Mehmet Bora Sarıoğlu row with backend / DevOps / coordination work + cross-layer PR review - §4.2 Status of Requirements: full 122-row audit pasted from the source-of-truth doc (112 Completed / 5 In Progress / 4 Not Started / 3 Out of Scope) - §4.3 API Endpoints: 4 verified scenarios already overridden; live Swagger UI link - §4.5 Utilised Standards: Compliance Summary annotated with issuing bodies + usage; Deep Dive entries now cite concrete file paths and integration tests - §4.6 Testing & QA: test report tree attached at reports/final-milestone/ with headline pass/fail per layer - §5 Individual Contributions: Mehmet Bora Sarıoğlu full 8-item section - §6 Live Deployment: bare IP swapped for https://mymentornet.org New wiki pages: - Use-Case-Diagram-(Final): 5-actor, ~165-use-case diagram (PlantUML render) - Class-Diagram-(Final): 6 bounded-context blocks - Sequence-Diagrams-(Final): 8 end-to-end workflows Assets: - images/final-milestone/: 28 rendered PNG diagrams (13 Mermaid + 15 PlantUML) - sources/final-milestone-diagrams/: 15 .puml sources + 3 Mermaid .md sources - reports/final-milestone/: 25 MB of HTML + JUnit-XML test reports across backend / web (unit + Playwright E2E) / mobile

    @mehmetborasarioglu mehmetborasarioglu committed May 16, 2026
    71852f7
  • Updated Final Milestone Deliverables (markdown)

    @LifelongWay LifelongWay committed May 16, 2026
    721f707
  • Updated Final Milestone Deliverables (markdown)

    @LifelongWay LifelongWay committed May 16, 2026
    32d54c7
  • Updated Final Milestone Deliverables (markdown)

    @mehmetborasarioglu mehmetborasarioglu committed May 16, 2026
    38baaeb
  • Updated Final Milestone Deliverables (markdown)

    @mehmetborasarioglu mehmetborasarioglu committed May 16, 2026
    d6e9776
  • Updated Prompts Dogan (markdown)

    @BERATCANS BERATCANS committed May 16, 2026
    994beae
  • Updated Prompts Dogan (markdown)

    @BERATCANS BERATCANS committed May 16, 2026
    79b5279
  • Updated Final Milestone Deliverables (markdown)

    @BERATCANS BERATCANS committed May 16, 2026
    2868840
  • Updated Final Milestone Deliverables (markdown)

    @BERATCANS BERATCANS committed May 16, 2026
    820d101
  • Updated Final Milestone Deliverables (markdown)

    @burakogut5 burakogut5 committed May 16, 2026
    9d58bd1
  • Updated Prompts Ogut (markdown)

    @burakogut5 burakogut5 committed May 16, 2026
    d4c7f5e
  • Updated Final Milestone Deliverables (markdown)

    @burakogut5 burakogut5 committed May 16, 2026
    f1a20aa
  • Updated Final Milestone Deliverables (markdown)

    @muhammetsami muhammetsami committed May 16, 2026
    5d5a15e
  • Updated Final Milestone Deliverables (markdown)

    @muhammetsami muhammetsami committed May 16, 2026
    50ae243
  • Updated Prompts Çakmak (markdown)

    @muhammetsami muhammetsami committed May 16, 2026
    78f42d5
  • Updated Prompts Muhammet Sami Çakmak (WEB) (markdown)

    @muhammetsami muhammetsami committed May 16, 2026
    0adb947
  • Updated Prompts Muhammet Sami Çakmak (WEB) (markdown)

    @muhammetsami muhammetsami committed May 16, 2026
    65bf8e0
  • Updated Prompts Cakmak (markdown)

    @muhammetsami muhammetsami committed May 16, 2026
    c31d70a
  • Updated _Sidebar (markdown)

    @ibrahimkayan ibrahimkayan committed May 16, 2026
    a76e17b
  • Updated Final Milestone Deliverables (markdown)

    @ibrahimkayan ibrahimkayan committed May 16, 2026
    877fcf7
  • Updated _Sidebar (markdown)

    @ibrahimkayan ibrahimkayan committed May 15, 2026
    e07a08b
  • Created AI Prompt Log - İbrahim Kayan (markdown)

    @ibrahimkayan ibrahimkayan committed May 15, 2026
    4c7f854
  • Updated Final Milestone Deliverables (markdown)

    @burakogut5 burakogut5 committed May 12, 2026
    aee0cdb
  • Updated Final Milestone Deliverables (markdown)

    @burakogut5 burakogut5 committed May 12, 2026
    7aad03d
  • docs: realign acceptance tests with Requirements.md and shipped backend * Intro paragraph + table refreshed to drop the "seven concrete tests" framing (file actually carries AT-01..AT-16 plus newly added AT-17/AT-18) and tag each row by step count. * AT-02 rewritten so it walks the mentor lifecycle against the feed surface that actually ships (1.1.7.x + 1.2.2.4) — the previous draft referenced a "blog" entity that never existed; mentor feed posts are the realised version of the 1.2.2.4 requirement. * AT-04 newly inserted in place of the empty Community Lifecycle slot. Walks social-feed reporting + hashtag search + share/repost across 1.1.6.x and 1.1.7.x. The 47-requirement "Community Lifecycle" outline that previously claimed this slot targeted a Community/Forum feature family that is not part of Requirements.md. * AT-05 rewritten so it walks the polymorphic-report state machine (1.1.6.x + 1.1.1.3.x) plus 2.2.4 cancellation auto-ban and 2.2.5 spam-bot detection — the realised abuse-mitigation surface — rather than the unimplemented Community Moderator + auto keyword filter flow from the previous draft. * AT-17 added: server-side profile-visibility enforcement (1.1.2.5, 1.2.2.3). Re-verifies the mentor-views-mentee mask plus private profile blocking via the post-#570 visibility gate. * AT-18 added: admin user-list and report-queue reads (1.1.1.3.1/2/3). Covers the post-#569 admin user list and the post-#568 admin reports queue. AT-07 (NFR posture) left untouched in this commit — its rewrite needs backend additions (community endpoints, vote manipulation detection, ban evasion detection) that are not in the current Requirements doc and not part of the shipped backend. A follow-up will rewrite AT-07 once the NFR surface scope is settled. AT-19..22 (follow graph, cancel/end-early, mentor rating, advanced search filters) are also deferred to a follow-up.

    @mehmetborasarioglu mehmetborasarioglu committed May 12, 2026
    b995be3
  • docs(at): replace obsolete AT-04 with AT-08 through AT-16 AT-04 (Community Lifecycle Management) is deleted — the underlying requirements 1.1.7.1.*, 1.1.8.*, 1.1.9.*, 1.1.10.* no longer exist in the spec (1.1.7 is now Social Feed, not communities). The test.fixme()-d spec files at04{a,b,c,d}-*.spec.js will be cleaned up in a follow-up; this commit covers only the wiki side. In its place, nine new acceptance tests cover the features that landed since the original AT-01-07 batch and the ones the PR #573 prereqs unblocked: AT-08 Feed post lifecycle (create, edit, delete, like, comment, bookmark) AT-09 Following feed near-real-time updates (STOMP push + 5s SLA) AT-10 Personalized For-You feed and explore recommendations with factor chips and a diverse-pick label AT-11 Mentor matching with the 1.1.2.5 surname/photo hide AT-12 Mentor capacity (1.1.1.2.11) and request gating (1.1.2.7) AT-13 Scheduler-driven auto-decline (1.1.4.7) and auto-completion (1.1.4.10) via the TestSupport triggers AT-14 Milestone and task lifecycle with timeline auto-refresh AT-15 Past mentorships, admin direct messaging, banned-state banner AT-16 Mobile parity (Maestro) — feature reachability across the React Native app All nine are authored by Mehmet Bora Sarıoğlu. AT-13 / AT-14 / AT-15 depend on the prereq infrastructure landing in PR #573 (TestSupport scheduler triggers, MyMentorshipsPage, AdminConsolePage, BannedStateBanner, MentorshipProgressTimeline refreshKey). AT-16 depends on the mobile testID sweep that also landed in #573 plus a Maestro CI pipeline that is its own follow-up.

    @mehmetborasarioglu mehmetborasarioglu committed May 12, 2026
    03ab9e4
  • Updated _Sidebar (markdown)

    @mehmetborasarioglu mehmetborasarioglu committed May 12, 2026
    7e3440f
  • docs(strategy): codify deterministic AT implementation patterns After debugging cross-browser flakes in AT-02 and AT-07, the team converged on a set of conventions that consistently produce zero-flake runs locally. Document them in the strategy page so new specs follow them by default: - Pre-authenticate via API + inject storageState (skip /login UI) - Atomic Promise.all([waitForResponse, action]) for UI-triggered mutations - Isolate shared per-IP buckets per test (unique probe emails, reset) - Avoid waitForLoadState(networkidle) - Disable controls until hydrated (Playwright maintainer recipe) - Stable data-testid selectors only, centralised in e2e/testids.js - Stability budget: 10 consecutive local runs, zero retries

    @mehmetborasarioglu mehmetborasarioglu committed May 12, 2026
    9df6fd5
  • Correct Final Milestone deadlines in Weekly Meeting 9 Code release deadline is 12.05.2026 (not 15.05.2026); other deliverables are 16.05.2026. Updates the agenda, discussion, and Actions Taken table to reflect the correct dates and shifts the 'X days earlier' relationship from 1 day to 4 days.

    @mehmetborasarioglu mehmetborasarioglu committed May 10, 2026
    3792b57