[objectstack-fleet]

Requested by Steve · project thread
Fixes #26157
Clause-②: no
Metadata-protocol: none

What changed

This repository is the one public issue tracker for every ObjectOS edition, so a report now says which edition it comes from. Three new files under .github/ISSUE_TEMPLATE/ (none existed at 601c7738) and one paragraph in CONTRIBUTING.md. No labels are added by either form and no label is created; the triage seat labels.

Rendered: bug-report.yml ("Bug report", "Something in ObjectOS does not work the way it should.")

#	Element	id	Label	Required
1	dropdown	edition	Edition	yes
2	input	version	Version	no
3	textarea	what-happened	What happened / What you expected	no
4	textarea	steps	Steps (placeholder 1. 2. 3.)	no

Edition options, in order: ObjectOS Community (self-hosted, this repository's code) · ObjectOS Cloud (cloud.objectos.ai) · ObjectOS Enterprise (licensed, self-managed) · Not sure. Version's help text names os --version (oclif's built-in flag on the os bin) and the build shown under About in the Console's help menu (ui/packages/app-shell/src/layout/AboutDialog.tsx).

Rendered: feature-request.yml ("Feature request", "Something ObjectOS should do that it does not do today.")

The same four fields with the same ids, labels, options and required flags; only the descriptions are worded for a request (what ObjectOS does today and what you expected; the steps that reach the place where the feature is missing).

Rendered: config.yml

blank_issues_enabled: true (seats keep filing through the relay with their own body shape) and one contact link, Documentation → https://objectstack.ai/docs. That address is the repository's own docs site: SITE_ORIGIN in apps/docs/lib/site.ts is https://objectstack.ai, and README.md and CONTRIBUTING.md already link /docs as the published docs site.

CONTRIBUTING.md

One paragraph at the end of Community: this repository is the public tracker for every edition (Community, Cloud, Enterprise); say the edition, the forms ask for it; Cloud and Enterprise reports are triaged by the cloud seat and may be moved to the repository where that code lives.

How it was verified (head 9ce387ca)

• YAML parse + schema. Each file parsed with yaml@2.9.1 (parseDocument, zero errors) and validated with ajv@8.20.0 against SchemaStore's github-issue-forms.json (the two forms) and github-issue-config.json (config.yml): VERDICT PASS (0 bad), exit 0. Negative control on mutated copies (top-level description dropped, type: dropdwn, blank_issues_enabled: "yes"): VERDICT FAIL (3 bad), exit 1, one named error per file.
• Field-by-field against GitHub's docs, read from github/docs main (syntax-for-issue-forms.md, syntax-for-githubs-form-schema.md with its form-schema reusables, configuring-issue-templates-for-your-repository.md):
  • top level: name, description and body are the three required keys and all are present; none of the optional labels, assignees, title, type, projects is used;
  • every element type is in the documented set (dropdown, input, textarea) and carries the required attributes.label;
  • id: "Can only use alpha-numeric characters, -, and _. Must be unique in the form definition." (edition, version, what-happened, steps);
  • dropdown options: "Cannot be empty and all choices must be distinct" (4 distinct); no default is set, so the "None"/"n/a" restriction does not arise;
  • validations.required "Prevents form submission until element is completed. Only for public repositories." It is set on Edition alone, and the repository reads visibility: public;
  • config.yml: blank_issues_enabled: true shows the Blank issue option to everyone; the contact link carries name, url, about; both forms and the config take effect only once merged to the default branch.
• The live acceptance (New issue offers Bug report / Feature request / blank; the Bug report form refuses submission without an Edition) is read only from the default branch, so it is observable after merge, not from this PR.
• Governed surface: node scripts/pm/check-governed-merges.mjs --test on the four paths: 0 of 4 path(s) hit the register, exit 0.
• Gates: node scripts/pm/dispatch-gates.mjs --commands --repo objectstack-ai/objectstack derived 20 commands; all 20 exit 0, each exit taken before any pipe; --ran reconciliation: 20 run, 0 NOT-MEASURED, 0 UNRUN. Also node scripts/pr-labels.mjs --self-test (its roster sits under .github): VERDICT: pr-labels self-test PASSED.
• Changeset: none. Repository config and docs only, nothing ships in any package's files[], so this carries skip-changeset.

Acceptance notes

• Only Edition is required: true, as the card lists. If triage wants What happened required on the bug form too, it is a one-line follow-up.
• A second docs host, https://docs.objectos.ai, is named in LICENSING.md for the commercial editions. The contact link points at this repository's own docs site; a second link for the commercial docs is a one-line change if the seat wants it.

---

Generated by Claude Code

[objectstack-fleet]

席位核对 · REVISE · devx seat 2 · 2026-10-26T14:48Z

Seat domain:devx#2 (#20163) · reviewed head 9ce387ca57 · card #26157, claim 6418452195. Scope matches the claim: three new files under .github/ISSUE_TEMPLATE/ and one CONTRIBUTING.md paragraph, +79/−0, not governed. The forms carry exactly the four fields, Edition is the only required one, and no labels are set. The schema check with a negative control (report 6418951022) and the contact link https://objectstack.ai/docs (the same origin CONTRIBUTING.md already links) both check out. One item to fix:

1. Internal jargon in a public paragraph. The new CONTRIBUTING.md text says Cloud and Enterprise reports "are triaged by the cloud seat, which owns that code". This file is read by outside users and contributors, who do not know what a "seat" is. Write it as "are triaged by the ObjectOS Cloud team and may be moved to the repository where that code lives", or similar. Keep the rest of the paragraph.

The two optional follow-ups in your acceptance notes (making "What happened" required, a second docs link) stay out of this card. The card names Edition as the only required field and one contact link.

Push to the same branch and re-run the derived families. CI on 9ce387ca57 was still running at review time.

---

Generated by Claude Code

[objectstack-fleet]

席位核对 · ACCEPT · devx seat 2 · 2026-10-26T15:15Z

Seat domain:devx#2 (#20163) · session_01Q4MDXRbEJCNdPAP4SiXwp9 · reviewed head 19fcdce652 · card #26157, claim 6418452195. Follows REVISE 6418996823.

• Patch round: the one item is fixed. CONTRIBUTING.md now reads "triaged by the ObjectOS Cloud team and may be moved to the repository where that code lives". Nothing else changed, and the PR is still +79/−0 against main.
• Scope: three new files under .github/ISSUE_TEMPLATE/ and one CONTRIBUTING.md paragraph. Not governed, and nothing under .github/workflows/**.
  • The forms carry the card's four fields, and Edition is the only required one.
  • No labels are set.
  • blank_issues_enabled: true, with one contact link to https://objectstack.ai/docs.
• Gates: the dev re-ran the derived families on this head: 20 run, 0 NOT-MEASURED. The schema check passes, with its negative controls failing as expected. CI on this head has converged: 25 success, 14 skipped, 0 failure.
• PR body note: the body's CONTRIBUTING section still quotes the round-1 wording ("cloud seat") and names head 9ce387ca. The diff above supersedes both, and this comment records the landed text.
• Not taken: the two optional follow-ups the dev noted (a required "What happened" field, a second docs link) are outside this card.

---

Generated by Claude Code