Skip to content

Model-free App reviewer identity experiment — close unmerged - #221

Closed
HemSoft wants to merge 1 commit into
mainfrom
experiment/issue-173-app-picker-20261021
Closed

HemSoft wants to merge 1 commit into
mainfrom
experiment/issue-173-app-picker-20261021

Conversation

@HemSoft

@HemSoft HemSoft commented Oct 21, 2026 •

Copy link
Copy Markdown
Collaborator

Purpose

Throwaway model-free experiment for #173, authorized by Franz on October 20, 2026 at 20:28 Eastern and relayed by the Chief. Verify the new private organization App hemsoft-sfl-reviewer in GitHub's native Reviewers picker and inspect persisted request/event identity, requester attribution, polling, canned COMMENT completion, removal/re-request, downtime discovery and stale completion behavior.

App ID 5406096; Bot hemsoft-sfl-reviewer[bot] ID 345646943; selected installation 173628126 covers only repository ID 1169772257. Permissions are contents read, metadata read and pull_requests write; no subscribed events or webhook. Preflight independently verified those values with App/installation authentication. No credential values are included here.

This repository is public: experiment requests, events and canned reviews will be public. No model inference, provider credentials, paid usage, deployment or retired automation is authorized or used. Do not run an AI review on this experiment.

Validation

The source change is an inert marker fixture at 81bf8669e29f7333582b62caa3e8e06cec1b2c0e. No runtime behavior changed.

Initial picker visibility failed in the checked session. The Chief, signed in as HemSoft in automated Chromium on mini, opened Reviewers and searched hemsoft-sfl-reviewer, HemSoft SFL and sfl; no matching App was shown. Nothing was selected. Manual human-browser repetition remains untested. The Chief reported an earlier App-install form rejection from this browser; that caveat prevents claiming a universal GitHub enrollment rule or a proven cause.

Both API-only bot-request routes, GraphQL requestReviewsByLogin with the exact bot login and requestReviews with its server-returned Bot node ID, returned without GraphQL errors but persisted no review request or request event. These calls do not establish native picker eligibility.

The canned COMMENT was successfully submitted as Bot ID345646943 using the new App's installation token, at the exact fixture head. This proves comment authorship only: there was no pending request to fulfill. No model inference occurred. The post-comment UI check also failed to create a request: the App appears as an existing commenter, and the picker lists it already ticked, but selecting/saving/reloading creates no pending request. No request or re-request control was present in the checked session.

Screenshots below were supplied by the Chief and visually inspected. They show this throwaway PR at the unchanged fixture head, before the canned App comment. The Chief's approximate01:03 Eastern time is retained as reported; precise server API times and screenshot file metadata are recorded separately rather than treating that estimate as event-order evidence. No recording is available because this handoff supplied still screenshots only.

Initial exact-slug search: Nothing to show

Initial display-name search: no results

Initial broad sfl search: no results

Final initial-picker state: no selection

Post-comment UI check

The Chief checked again as HemSoft in the same automated Chromium session, reporting approximately01:10–01:12 Eastern. The App is now visible as an existing reviewer because it left the canned COMMENT. The Chief selected the already-ticked picker entry and closed the menu; after reload the sidebar was unchanged. The pending-reviewer API still returns empty users/teams, and the full timeline contains no review-request/removal events. The only review is the App COMMENT5595158403. Native request creation and re-request are failed observations for this App/session; manual-browser behavior and the GitHub eligibility cause remain unproven.

After COMMENT: existing App reviewer, no request control

After COMMENT: exact-slug picker entry

Already-ticked App entry selected

After selection and reload: unchanged reviewer sidebar

Disposal

Close this PR unmerged when the experiment ends. It is never a merge candidate and does not close #173. Commit the dated sanitized gate report separately through the mission's normal review and merge gates. Actions remains disabled.

Final disposal: CLOSED unmerged at 01:13:30 EDT October21; branch preserved privately then deleted. Dated report: #222. App identity/installation/COMMENT authorship passed, native request and re-request failed in the checked sessions, dependent native lifecycle gates remain unexercised. Franz chose comment plus automatic polling triggers separately at 01:19 EDT; no inference or replacement trigger was activated.

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 21, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-21T04:55:24.324629Z 81bf866 PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@hemsoft-sfl-reviewer hemsoft-sfl-reviewer Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Model-free App identity experiment for #173.

This is a canned COMMENT from hemsoft-sfl-reviewer, not a model-generated code review or approval. No model has analyzed this PR. Reviewed fixture head: 81bf8669e29f7333582b62caa3e8e06cec1b2c0e. Neither the initial picker searches nor the two API bot-request mutations created a pending request; this comment does not establish native request fulfillment.

Experiment ID: sfl-model-free-pr221-comment-20261021.

@HemSoft

HemSoft commented Oct 21, 2026

Copy link
Copy Markdown
Collaborator Author

Model-free experiment complete. The supplied screenshots are attached in Validation. App identity, selected installation and canned COMMENT authorship passed; initial and post-comment native review-request creation failed in the checked session, and both Bot API routes persisted no request/event. Downstream native-request lifecycle gates remain blocked. Closing unmerged as authorized; a separate dated gate-report PR follows. No model inference or replacement trigger was enabled.

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.

Prove public-target subscription support and native App eligibility

1 participant