tim/SlipItIn
1
0
Fork 0
Code Pull Requests 1 Actions 1 Packages Releases Wiki Activity

docs: update OpenWiki

Browse Source
This commit is contained in:
tim
2026-08-08 18:09:52 +00:00
committed by github-actions[bot]
parent 37616a9316
commit c67c549f48
4 changed files with 10 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
openwiki/.last-update.json
View File

@@ -1,7 +1,7 @@
{ {
"updatedAt": "2026-08-08T10:49:34.141Z", "updatedAt": "2026-08-08T18:09:49.042Z",
"command": "update", "command": "update",
"gitHead": "bbc6ad60802ba4e19218d1529c927c67389d973d", "gitHead": "37616a93166c2ac0a46eedab276164f811043f4e",
"model": "gemini-3.6-flash", "model": "gemini-3.6-flash",
"status": "complete", "status": "complete",
"language": "en" "language": "en"

2
openwiki/architecture/overview.md
View File

@@ -108,7 +108,7 @@ sequenceDiagram
Client->>Hub: JoinLobby(lobbyCode) Client->>Hub: JoinLobby(lobbyCode)
Hub->>Hub: GetAuthenticatedUserId() Hub->>Hub: GetAuthenticatedUserId()
Hub->>Service: JoinGameAsync(lobbyCode, userId, connectionId) Hub->>Service: JoinGameAsync(lobbyCode, userId, connectionId)
Hub-->>Client: Broadcast "PlayerJoined" (GameStateDto) Hub-->>Client: Broadcast PlayerJoined (GameStateDto)
``` ```
*Sequence diagram showing user authentication via REST and subsequent authenticated SignalR WebSocket connection.* *Sequence diagram showing user authentication via REST and subsequent authenticated SignalR WebSocket connection.*

3
openwiki/source-map.md
View File

@@ -96,3 +96,6 @@ SlipItIn.slnx
### `Documentation & Specifications` (`Agents/`) ### `Documentation & Specifications` (`Agents/`)
- **`Agents/Architecture.md`**: Specification document defining backend security and client MVVM/stability patterns. - **`Agents/Architecture.md`**: Specification document defining backend security and client MVVM/stability patterns.
- **`Agents/ProjectPlan.md`**: Project plan breakdown covering development phases. - **`Agents/ProjectPlan.md`**: Project plan breakdown covering development phases.
### `Automation & CI/CD` (`.github/workflows/`)
- **`.github/workflows/openwiki-update.yml`**: Scheduled GitHub Actions workflow executing `openwiki code --update` via Gemini Flash (`gemini-3.6-flash`) to keep repository documentation in sync with source changes.

8
openwiki/workflows/slip-and-challenge.md
View File

@@ -95,15 +95,15 @@ sequenceDiagram
GameBoardVM->>Hub: SubmitSlip(gameId, playerAId, cardId) GameBoardVM->>Hub: SubmitSlip(gameId, playerAId, cardId)
Hub->>Service: SubmitSlipAsync() Hub->>Service: SubmitSlipAsync()
Service->>DB: Set PlayerCard.IsUsed = true Service->>DB: Set PlayerCard.IsUsed = true
Hub-->>Challenger: Broadcast "SlipSubmitted" Hub-->>Challenger: Broadcast SlipSubmitted
Note over Challenger: Suspects invalid phrase Note over Challenger: Suspects invalid phrase
Challenger->>GameBoardVM: ChallengeCardAsync(card) Challenger->>GameBoardVM: ChallengeCardAsync(card)
GameBoardVM->>Hub: ChallengeSlip(gameId, playerBId, cardId) GameBoardVM->>Hub: ChallengeSlip(gameId, playerBId, cardId)
Hub->>Service: CreateChallengeAsync() Hub->>Service: CreateChallengeAsync()
Service->>DB: Insert SlipChallenge (Status = Pending) Service->>DB: Insert SlipChallenge (Status = Pending)
Hub-->>Challenger: Broadcast "SlipChallenged" Hub-->>Challenger: Broadcast SlipChallenged
Hub-->>Slipper: Unicast "ChallengeReceived" Hub-->>Slipper: Unicast ChallengeReceived
Note over Slipper: Notification Overlay Displays Note over Slipper: Notification Overlay Displays
Slipper->>GameBoardVM: ResolveChallengeAsync(challengeId, approved) Slipper->>GameBoardVM: ResolveChallengeAsync(challengeId, approved)
@@ -116,7 +116,7 @@ sequenceDiagram
else approved == true (Justified Catch) else approved == true (Justified Catch)
Service->>DB: Set Challenge.Status = Approved Service->>DB: Set Challenge.Status = Approved
end end
Hub-->>Challenger: Broadcast "ChallengeResolved" Hub-->>Challenger: Broadcast ChallengeResolved
``` ```
*Sequence diagram showing phrase submission, challenge initiation, target notification, and penalty resolution.* *Sequence diagram showing phrase submission, challenge initiation, target notification, and penalty resolution.*