Skip to content

feat: own presentation: social preview, code of conduct and issue forms (#134) - #135

Merged
CompleteDotTech merged 12 commits into
mainfrom
feat/134-own-presentation
Nov 1, 2026
Merged

CompleteDotTech merged 12 commits into
mainfrom
feat/134-own-presentation

Conversation

@CompleteDotTech

@CompleteDotTech CompleteDotTech commented Nov 1, 2026 •

Copy link
Copy Markdown
Contributor

Resolves #134

Change and affected skills

Adds the repository's own presentation items that a normal pull request can carry:

  • assets/social-preview.png (1280x640): a byte-identical copy of the reviewed configured own render produced through the real showcase.py (sha256 5d318b92b04518de4a86af0429ef864a97390f6e4cc245a9d7cf78b18a433152; it is the same artifact whose bytes a native Windows replay reproduced exactly). Nothing was regenerated or edited, and the private metadata file is not committed.
  • CODE_OF_CONDUCT.md: the official Contributor Covenant 2.1 text with the contact documented in the published org policy (references/orgs-and-projects.md); no inbox was invented.
  • .github/ISSUE_TEMPLATE/bug_report.yml, feature_request.yml and config.yml: issue forms that follow the published policy and use the repository's label scheme (type:bug, type:feature, status:needs-triage).
  • tests/test_own_presentation.py (plus a CHANGELOG line): checks the asset size, that the forms parse as YAML and reference documented labels, that the code of conduct names the documented contact and contains the canonical pledge text (including the words "caste, color" that an earlier draft omitted).

Resolves #134 only; the Settings social-preview upload is a separate step done through the authenticated UI after this merges; delete_branch_on_merge and wiki/projects are not touched.

Prior work

Searched open and closed issues and PRs for social preview, issue template, community health, doctor R10 and R11 and for an existing PR on this branch: only #119 (doctor owner-decision classification) is related and is not duplicated; merged #130 and #132 are reused. The labels the forms reference were created beforehand (22 planned label operations applied, all exit 0, and an independent readback of labels --plan reports no remaining operations).

Evidence (head f53bc96e740884d20a3093df59dcb1dea41c7ef7, base main 2243010d67725c17a163223d84f91a119f7262dd)

  • Exact-head VM (designated VM, run by the outer coordinator): all four required commands (package tests, package validator, full pytest, quality validator) passed: 1315 passed, 11 skipped, 37 subtests (vm-f53bc96e...-result.json); whole-tree ruff passes.
  • Code-of-conduct fidelity: the root VM comparison against the official Contributor Covenant 2.1 text shows an identical word sequence after whitespace normalization and the documented contact substitution; the two new tests pass on the canonical text and detect the deliberately broken old-omission sources (fidelity-test-guard-...-vm.json, coc-fixed-word-comparison-...-vm.json). An earlier worker commit that omitted two words is preserved in history and is not part of this PR.
  • Byte continuity: the asset and community files are unchanged between the previously verified head c80db04 and this head (134-f53-presentation-byte-continuity.json).
  • Native Windows host run on this head (supplemental): 1308 passed, 18 skipped, 37 subtests with the quality validation passing.
  • Hosted CI on this exact head: all 14 required check runs (validate-package, pytest on ubuntu/windows/macos, validate; push and pull_request) completed with success; the PR is mergeable and clean against main with zero review threads. The labels the forms reference exist (type:bug, type:feature, status:needs-triage).
  • Reviews on this exact head and base, all approve with no findings and the acceptance criteria met: two independent Opus reviews (both claude-opus-5-5, native identities verified from the agent transcripts) and one Codex gpt-6.1-sol review at max effort (native Codex session verified; the exact static review protocol was present in its prompt; lifecycle gates are coordinator-owned and were checked by the coordinator).

Boundaries

Activation keys, consent, private assets, approval gates and specialist entry points are untouched. No registry release, visibility change, repository setting or live external action is part of this PR. It shares no file with the open PRs #13 and #123.

Family consistency

No shared-skill change; no sibling PR affected.

🤖 Generated with Claude Code

CompleteDotTech and others added 12 commits November 1, 2026 05:27
Co-Authored-By: Claude Haiku 5.5 <noreply@anthropic.com>
Disable blank issues and link to Discussions and private security advisories.

Co-Authored-By: Claude Haiku 5.5 <noreply@anthropic.com>
Refs #134

Co-Authored-By: Claude Haiku 5.5 <noreply@anthropic.com>
…nd CoC (#134)

Co-Authored-By: Claude Haiku 5.5 <noreply@anthropic.com>
…ms (#134)

- assets/social-preview.png: byte-identical copy of the accepted own-132
  render social.png (1280x640, sha256 5d318b92b04518de4a86af0429ef864a97390f6e4cc245a9d7cf78b18a433152),
  equal to receipt.json and the visual-windows replay bytes. Not hand edited,
  not regenerated, not uploaded; *.png is already binary in .gitattributes.
- CODE_OF_CONDUCT.md: Contributor Covenant 2.1, contact Timothy.Gregg@complete.tech
  (no invented inbox).
- Issue forms bug_report.yml and feature_request.yml (existing standard labels
  only) and config.yml. Owner fix of the Haiku results: the config and bug
  form no longer point at Discussions or private vulnerability reporting,
  which are disabled on this repository, and the forms contain no email.
- tests/test_own_presentation.py guards the PNG size and hash, form YAML and
  labels against references/standard/labels.yml, and the code of conduct contact.
- CHANGELOG line under Unreleased/Added.

Prior work: searched #132/#133 own assets and the org default templates
(pick-your-ai-org-github/.github defaults per references/orgs-and-projects.md);
no existing social preview, code of conduct or issue forms in this repo.

Lineage: docs/images/.showcase.json has no social entry, so lineage rests on
the receipt and the own-132 render (icon_sha256 a1bbf17b... matches
assets/icon.png).

Evidence (local only): pytest tests/test_own_presentation.py
tests/test_package_files.py 13 passed; ruff check on the new test clean;
validate_quality parse_structured_files, gate_changelog, gate_privacy and
gate_package_extras ok; negative check in a scratch copy (nonexistent label,
truncated PNG) fails 3 tests as intended. validate_package.py and
test_package_contract.py unchanged from origin/main. VM: not run. CI: pending.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Haiku 5.5 <noreply@anthropic.com>
…gest (#134)

Add a pledge-token check that fails on the omitted 'caste, color,' tokens and
a whitespace-normalized SHA-256 check against the canonical CoC text.

Co-Authored-By: Claude Haiku 5.5 <noreply@anthropic.com>
)

Merge hk/134 round 2 (tests/test_own_presentation.py) and record the Code of
Conduct fidelity regression in the changelog.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Haiku 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review Summary

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

Review Status Commit Review trigger
🔒 Security Review ⚠️ Failed 2026-11-01T10:48:59.427737Z
We couldn’t complete this review. Comment @codex security review to try again.
f53bc96 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.

@chatgpt-codex-connector

Copy link
Copy Markdown

The account paying for this security review has reached its Codex usage limits. The payer can check the Codex usage dashboard. For personal accounts, using credits requires enabling “Use credits for security reviews” in Code review settings. If you do not manage the paying account, contact this repository's admins.

@CompleteDotTech
CompleteDotTech merged commit f5fa292 into main Nov 1, 2026
14 checks passed
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.

Commit the social preview image, issue forms and code of conduct for the repository's own presentation

1 participant