Skip to content

Document wait endpoint exception and mandatory duration logging - #17

Draft
TaprootFreak wants to merge 2 commits into
developfrom
docs/wait-endpoint-exception
Draft

Document wait endpoint exception and mandatory duration logging#17
TaprootFreak wants to merge 2 commits into
developfrom
docs/wait-endpoint-exception

Conversation

@TaprootFreak

@TaprootFreak TaprootFreak commented Sep 6, 2026

Copy link
Copy Markdown
Contributor

EN:
Exempt wait endpoints, including long polling, from the 100ms response deadline and require logging the actual waiting duration of every individual request. All other quality requirements remain applicable.

DE:
Wait-Endpunkte einschliesslich Long-Polling von der 100-ms-Antwortfrist ausnehmen und die tatsächliche Wartezeit jedes einzelnen Aufrufs protokollieren. Alle übrigen Qualitätsanforderungen gelten weiterhin.

Details

Clarifies CONTRIBUTING.md, README.md and REVIEW.md. Wait duration alone must not cause a 100ms cutoff or review/CI failure; forwarding known routes remains forbidden. Documentation only, at the user's explicit direction: no runtime, endpoint, catalog, test or deployment changes. The runtime exception and wait logging are not claimed to be implemented.

Commit verification blocker: both the Git data API and contents API produced unsigned commits. Direct Git push was rejected with HTTP 403. CONTRIBUTING.md requires GitHub-verified commits and forbids rewriting published commits to re-sign them. This PR remains a draft pending a compliant signed publication path or an explicit reviewer exception. The documentation diff and required test CI pass.

Review scope clarification: REVIEW.md item 11 also requires a written grant for existing unidentified E2E rows. Those existing gaps remain in the unchanged catalog (/, /version, swagger aliases, /v1/statistic, /v1/coin, /v1/setting, /v1/bank, /v1/app). The user's explicit documentation-only instruction governs this task; no implementation or unrelated E2E work is included. This does not claim those gaps are resolved or grant permission to change their endpoints.

Validation: documentation diff and whitespace checks, required test CI on the final head, mergeability and review threads.

@TaprootFreak TaprootFreak changed the title Document the response deadline exception for wait endpoints Document wait endpoint exception and mandatory duration logging Sep 6, 2026

@TaprootFreak TaprootFreak left a comment

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Final self-review: documentation explicitly exempts wait duration from the 100ms deadline and requires actual-duration logging for every wait request; other requirements remain applicable. Documentation diff and whitespace check pass. Required test CI succeeded on this exact head, the PR is mergeable, and no review threads are open. No runtime, catalog or workflow changes. Blocker: both commits are unsigned, contrary to CONTRIBUTING.md; GitHub connector writes did not produce verified commits and direct Git push was denied with HTTP 403. No published history was rewritten. Existing unidentified E2E rows are reported in the PR body under the user's explicit documentation-only scope. Keeping this PR draft; this is not an independent approval or a claim that every review gate passed.

@TaprootFreakAI

Copy link
Copy Markdown
Contributor

Superseded by #19: identical final documentation tree, GitHub-verified signed commit, successful required CI and final self-review. No published history was rewritten.

@TaprootFreakAI

Copy link
Copy Markdown
Contributor

Superseded by #19: identical final documentation tree, GitHub-verified signed commit, green required CI and final self-review. Please use #19 for review and merge. Closing this old PR through the CLI was denied because its author is a different account.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants