Skip to content

[documentation-writing-alignment] State public and agent entry context directly #17

Closed

Description

Describe the change

Context and request

Visitors and agents need an accurate entry into MSX documentation and this repository's community defaults. Add concise, factual orientation to the public profile and correct the agent read-order description without changing its executable sequence. This delivery leaf covers one focused prose-only draft PR.

Evidence and sources

At source 0c67251812ea306543f3a14ab473ae357cfb76ac, profile/README.md:1 contains only the brand slogan. It does not identify what MSX provides or where readers find its shared standards. AGENTS.md:5 describes the root README as explaining “how its defaults are enforced,” but the root README explains GitHub fallback, documentation, and media, not an installed enforcement mechanism.

The fixed Documentation Model requires evergreen current-contract prose and distinguishes a normative contract from implementation evidence. Natural Language requires direct en-US prose and executable agent instructions. Documentation keeps context close to its subject and links canonical guidance. The pinned MSX home page and this repository's root README provide the factual source for MSX standards, ways of working, and community defaults. Apply the Writing Guide and official STEMG explanations.

Acceptance criteria

  • The public profile gives concise, present-tense orientation and working canonical links to MSX documentation and relevant community-default context.
  • The profile states only facts supported by the pinned MSX home page and repository evidence. It does not invent a mission, product guarantee, CI enforcement, security guarantee, or new policy.
  • The brand slogan remains an accepted branding difference rather than a claimed STE-compliant technical statement. Preserve its heading/anchor unless a verified need requires a change.
  • AGENTS.md retains the exact README-then-CONTRIBUTING read order and working paths. Its descriptions match the actual documents and do not claim installed enforcement.
  • .claude/CLAUDE.md and .github/copilot-instructions.md retain their existing thin-pointer syntax. The root README and CONTRIBUTING remain with the existing PR authors use canonical guidance without repository templates #8 owner.
  • The issue and PR retain before/after evidence and exact validation commands with results. The PR remains in draft; no merge or Agent merge change occurs.

Technical decisions

Owned change paths are profile/README.md and AGENTS.md; review the two agent wrappers for a no-change result. Keep the existing document shapes, identifiers, read order, and brand heading. Link canonical guidance rather than copying standards. Root README audience clarification is coordinated through #8, not duplicated in this PR. No new documentation hierarchy, generated output, tooling, dependency, or repository audit file belongs in this slice. The base has no Markdown/link validation scripts; do not describe the unmerged #12 check as enforced.

Implementation plan

  • Read the owned documents, wrappers, pinned sources, and root context; capture the missing orientation and unsupported enforcement statement before editing.
  • Make surgical prose changes, keep one logical change per small commit, and open the scoped draft PR early.
  • Verify every factual statement against its source; verify the exact read order, wrapper resolution, heading stability, and all added links.
  • Run the existing applicable checks and git diff --check; record exact commands and results and any unavailable check, without claiming full STE conformance.
  • Review the final diff, update this plan with evidence, link only the delivery work it resolves, and leave the PR in draft.

Activity

  1. MariusStorhaug commented on Nov 4, 2026

    @MariusStorhaug
    MemberAuthor

    Baseline evidence before editing

    The checked source is 0c67251812ea306543f3a14ab473ae357cfb76ac. The worktree is clean. This delivery changes only profile/README.md and AGENTS.md.

    Acceptance check Before result
    Factual profile orientation FAIL: the profile contains only the brand heading.
    Canonical documentation link FAIL: no link exists.
    Community-default context and link FAIL: no context or link exists.
    Accurate README description FAIL: AGENTS.md claims that the README describes enforcement.
    Accurate contribution-guide description FAIL: the guide links central guidance but does not describe change and review steps.
    Exact README-then-CONTRIBUTING read order PASS
    Read-order target files exist PASS
    Imperative Read in this order: instruction PASS
    Existing profile and AGENTS headings PASS
    Exact thin-pointer syntax PASS
    Both wrappers resolve to root AGENTS.md PASS
    Root README, CONTRIBUTING, PR template, and wrappers unchanged PASS

    The inline PowerShell assertions return 7/12 passed, 5 expected failures, exit 1, before any document edit. Source inspection confirms the failed claims. The baseline can also be inspected with these exact commands:

    git show 0c67251812ea306543f3a14ab473ae357cfb76ac:profile/README.md
    git show 0c67251812ea306543f3a14ab473ae357cfb76ac:AGENTS.md
    git show 0c67251812ea306543f3a14ab473ae357cfb76ac:.github/CONTRIBUTING.md

    All three commands succeed. The first returns only the existing slogan heading. The second contains how its defaults are enforced and how a change is made and reviewed. The third links central MSX documentation.

    The fixed standards source is MSXOrg/docs commit 1b0d4893c8fefabe604d04393068a8ff6f848082, under src/docs/. The Documentation Model, Natural Language, Writing Guide, Markdown, Documentation, home page, README-Driven Context, and applicable workflow, PR, and commit sources are available and read. The official STE description, FAQ, and Issue 9 DOI record are available. The local Issue 9 PDF MD5 is 9c720341c350ed77943b2c73d01c716f, which matches the official record. The local reference confirms active voice, imperative instructions, and the 25-word descriptive sentence limit. Reference files remain local; this is not a full STE conformance claim.

    The tree has no Markdown/link validation scripts, shared Markdown configuration, or workflow directory. No check from unmerged #12 is treated as installed or enforced. No tooling or dependency will be added. The optional parent ..\AGENTS.md path is absent; the repository's root AGENTS.md and both actual wrapper routes are available.

    Next verification: repeat the acceptance checks after the two prose changes; inspect each factual statement against the pinned home page and local README; inspect both added link destinations; run git diff --check; confirm exact wrapper content, read order, headings, and the two-path diff. The draft PR closes only #17 and remains draft without merge automation.

  2. MariusStorhaug commented on Nov 4, 2026

    @MariusStorhaug
    MemberAuthor

    Implementation is persistent in a draft PR

    The focused draft PR opened after the first logical commit, before the agent-description change.

    • ce0a2f3c7646fcbe4d06cb0fa5c857034ba164eb: the profile links MSX guidance and community defaults.
    • 5b6191d042d48503124cdfcad9a062182be546db: the agent read-order descriptions match their target documents.

    Only profile/README.md and AGENTS.md differ from 0c67251812ea306543f3a14ab473ae357cfb76ac. The original profile heading remains exact. The two wrappers, root README, contribution guide, and PR template have no changes. The repeat acceptance run returns 12/12 passed, 0 failed, exit 0. Final source, scope, and review evidence follow before handoff. The PR remains draft; no merge automation is enabled.

  3. MariusStorhaug commented on Nov 4, 2026

    @MariusStorhaug
    MemberAuthor

    Final delivery evidence

    The focused draft PR retains the final source, before/after evidence, exact commands and results, standards alignment, convergence scope, and approved final-source review. The evidence below is copied from the verified PR record. The PR remains draft and unmerged.

    Technical details

    Scope and persistent source

    The comparison is 0c67251812ea306543f3a14ab473ae357cfb76ac...e90ab70966ccfa12f7c20a486fb40f5846062c9a. The PR contains only profile/README.md and AGENTS.md: nine added lines and two removed lines. The worktree is clean.

    Three small commits retain the implementation sequence:

    • ce0a2f3c7646fcbe4d06cb0fa5c857034ba164eb: add profile context and links; open this draft before the agent edit.
    • 5b6191d042d48503124cdfcad9a062182be546db: correct both agent read-order descriptions.
    • e90ab70966ccfa12f7c20a486fb40f5846062c9a: use file of that type for the default-file explanation after the source-vocabulary review.

    The root README, contribution guide, PR template, forms, and SECURITY/SUPPORT policies are not changed. Root README audience clarification remains with its existing owner. No tooling, dependency, generated output, or documentation structure is added.

    Source and factual review

    The fixed authority is MSXOrg/docs commit 1b0d4893c8fefabe604d04393068a8ff6f848082, under src/docs/. The source review covers Documentation Model, Natural Language, Writing Guide, Markdown, Documentation, README-Driven Context, and the applicable workflow, contribution, PR, commit, branching, and completion guidance.

    Changed statement Verified evidence
    MSX documentation contains shared standards and ways of working for humans and agents. The pinned MSX home page, especially its scope and documentation map.
    The community-defaults repository contains shared GitHub files; GitHub uses a default when a repository has no file of that type. The baseline root README and actual tracked community files.
    The root README covers community defaults, MSX documentation, and shared media. The same baseline README, inspected in the worktree and through GitHub.
    CONTRIBUTING links MSX contribution guidance. The baseline contribution guide, which points to central MSX documentation.

    The official STE description, FAQ, and Issue 9 DOI record are available. The local Issue 9 PDF has MD5 9c720341c350ed77943b2c73d01c716f, which matches the official record. The review uses the relevant verb, instruction, descriptive-writing, and dictionary guidance. The manual and extraction remain local.

    The added prose uses en-US, present tense, active voice, and short sentences. Its plain-text sentence lengths are 14, 8, and 15 words. Read in this order: remains imperative. Ways of working retains the source's technical term. The existing slogan is an accepted branding difference, not a claimed STE-compliant technical statement. Neither these checks nor a word count establish full STE conformance.

    All required pinned MSX and official STE sources are available. The custom instruction's literal parent ..\AGENTS.md path is absent. The repository root AGENTS.md is available, was read, and is the verified destination of both actual wrappers. No source or access blocker prevents this delivery.

    Before and after acceptance evidence

    The pre-edit record retains the baseline failures. The same 12 acceptance checks return seven passes and five expected failures before editing, then 12 passes and no failures after editing. The final wording is included in the passing run.

    Check Before After
    Profile orientation Missing; only the slogan exists. Shared guidance and its human/agent audience are stated.
    Canonical documentation link Missing. https://msx.no/docs/ is present and returns HTTP 200.
    Community-default context and link Missing. The repository link and default-file explanation are present; the link returns HTTP 200.
    README description Claims that the README describes enforcement. Describes community defaults, MSX documentation, and shared media.
    Contribution-guide description Claims that the guide describes change and review steps. Describes the link to MSX contribution guidance.
    Remaining seven route/format/no-change checks Pass. Pass without changing the instructions, headings, targets, or protected files.

    The exact read order remains README.md, then .github/CONTRIBUTING.md. Both target files exist. Both H1 texts are identical to the baseline, so their existing heading anchors remain stable. No heading or fragment is added.

    No-change wrapper Exact syntax Resolved target
    .claude/CLAUDE.md @../AGENTS.md Root AGENTS.md
    .github/copilot-instructions.md Follow the instructions in [AGENTS.md](../AGENTS.md). Root AGENTS.md

    Exact acceptance check

    This PowerShell block was run before and after the edit. The baseline exits 1 with five expected failures. The final source exits 0 with 12/12 passed; 0 failed. The text assertions verify explicit content and invariant routes; the source table above supplies the factual review.

    $baseline = '0c67251812ea306543f3a14ab473ae357cfb76ac'
    $profile = Get-Content -LiteralPath 'profile\README.md' -Raw
    $agents = Get-Content -LiteralPath 'AGENTS.md' -Raw
    $readOrder = @([regex]::Matches($agents, '(?m)^\d+\. \[[^\]]+\]\(([^)]+)\)') | ForEach-Object { $_.Groups[1].Value })
    $profileHeading = [regex]::Match($profile, '(?m)^# .+').Value.TrimEnd()
    $baselineProfileHeading = (git show "${baseline}:profile/README.md" | Select-Object -First 1).TrimEnd()
    $agentHeading = [regex]::Match($agents, '(?m)^# .+').Value.TrimEnd()
    $baselineAgentHeading = (git show "${baseline}:AGENTS.md" | Select-Object -First 1).TrimEnd()
    git diff --quiet $baseline -- README.md .github\CONTRIBUTING.md .github\pull_request_template.md .claude\CLAUDE.md .github\copilot-instructions.md
    $protectedFilesUnchanged = $LASTEXITCODE -eq 0
    $agentPath = (Resolve-Path -LiteralPath 'AGENTS.md').Path
    $checks = [ordered]@{
        ProfileOrientation = ($profile -match 'shared standards' -and $profile -match 'ways\s+of working' -and $profile -match '(humans|people) and agents')
        CanonicalDocumentationLink = $profile.Contains('https://msx.no/docs/')
        CommunityDefaultContext = ($profile.Contains('https://github.com/MSXOrg/.github') -and $profile -match 'GitHub uses a default file')
        NoEnforcementClaim = $agents -notmatch '\benforc'
        ContributionPointerDescription = ($agents -match 'link to MSX contribution guidance' -and $agents -notmatch 'made and reviewed')
        ExactReadOrder = (($readOrder -join '|') -ceq 'README.md|.github/CONTRIBUTING.md')
        ReadTargetsResolve = ((Test-Path -LiteralPath 'README.md' -PathType Leaf) -and (Test-Path -LiteralPath '.github\CONTRIBUTING.md' -PathType Leaf))
        ImperativeInstruction = $agents.Contains('Read in this order:')
        HeadingStability = ($profileHeading -ceq $baselineProfileHeading -and $agentHeading -ceq $baselineAgentHeading)
        ThinPointerSyntax = ((Get-Content -LiteralPath '.claude\CLAUDE.md' -Raw).Trim() -ceq '@../AGENTS.md' -and (Get-Content -LiteralPath '.github\copilot-instructions.md' -Raw).Trim() -ceq 'Follow the instructions in [AGENTS.md](../AGENTS.md).')
        WrapperResolution = ((Resolve-Path -LiteralPath '.claude\..\AGENTS.md').Path -ceq $agentPath -and (Resolve-Path -LiteralPath '.github\..\AGENTS.md').Path -ceq $agentPath)
        ProtectedFilesUnchanged = $protectedFilesUnchanged
    }
    $checks.GetEnumerator() | ForEach-Object { '{0}: {1}' -f $_.Key, $(if ($_.Value) { 'PASS' } else { 'FAIL' }) }
    $failed = @($checks.Values | Where-Object { -not $_ }).Count
    '{0}/{1} passed; {2} failed' -f ($checks.Count - $failed), $checks.Count, $failed
    if ($failed -gt 0) { exit 1 }

    Other checks and results

    Exact command Result
    git diff --check 0c67251812ea306543f3a14ab473ae357cfb76ac Passed after both edits and after the final wording change.
    git diff --cached --check Passed before each of the three commits.
    git diff --check 0c67251812ea306543f3a14ab473ae357cfb76ac...HEAD Passed for final commit e90ab70966ccfa12f7c20a486fb40f5846062c9a.
    git diff --name-only 0c67251812ea306543f3a14ab473ae357cfb76ac Returned exactly AGENTS.md and profile/README.md.
    git diff --exit-code 0c67251812ea306543f3a14ab473ae357cfb76ac...HEAD -- .claude\CLAUDE.md .github\copilot-instructions.md README.md .github\CONTRIBUTING.md .github\pull_request_template.md Passed with no diff.
    curl.exe --fail --location --silent --show-error --max-time 60 --output NUL --write-out 'HTTP %{http_code}; URL %{url_effective}\n' 'https://msx.no/docs/' Passed; HTTP 200 at that canonical URL.
    curl.exe --fail --location --silent --show-error --max-time 60 --output NUL --write-out 'HTTP %{http_code}; URL %{url_effective}\n' 'https://github.com/MSXOrg/.github' Passed; HTTP 200 at that repository URL.
    git --no-pager status --short Passed with no output; the worktree is clean.

    Both HTTP destinations were also read to confirm the expected content, not only a successful status. The profile uses an absolute repository link so it reaches the same context from both the organization profile and the repository view.

    The following GitHub GFM render commands succeed for the final source. Shape assertions confirm one H1, two paragraphs, and two canonical links for the profile; one H1 and one two-step ordered list for AGENTS.md. The wrapper-resolution command returns the same root AGENTS.md for both paths.

    $profile = Get-Content -LiteralPath 'profile\README.md' -Raw
    $profileHtml = (@{ text = $profile; mode = 'gfm'; context = 'MSXOrg/.github' } | ConvertTo-Json -Compress | gh api --method POST markdown --input -) -join "`n"
    $agents = Get-Content -LiteralPath 'AGENTS.md' -Raw
    $agentsHtml = (@{ text = $agents; mode = 'gfm'; context = 'MSXOrg/.github' } | ConvertTo-Json -Compress | gh api --method POST markdown --input -) -join "`n"
    Resolve-Path -LiteralPath '.claude\..\AGENTS.md', '.github\..\AGENTS.md' | Select-Object -ExpandProperty Path

    Markdown/link lint was not run: the baseline has no corresponding scripts, shared Markdown configuration, package manifest, or workflow directory. The availability probe finds no installed markdownlint-cli2, markdownlint, or pymarkdown command. No dependency is installed. Unmerged #12 is not treated as installed or enforced validation.

    foreach ($name in @('markdownlint-cli2', 'markdownlint', 'pymarkdown')) { $command = Get-Command -Name $name -ErrorAction SilentlyContinue; if ($null -eq $command) { '{0}: unavailable' -f $name } else { '{0}: {1}' -f $name, $command.Source } }
    git ls-files -- '*.ps1' '.github/workflows/*' '*markdownlint*' '*markdown-lint*' 'package.json' 'pyproject.toml'

    The probe reports all three commands unavailable. The tracked-file query returns no matches. The local/manual checks above are evidence for this delivery, not installed CI enforcement.

    Standards and framework alignment

    The final pass checks the applicable pinned process and writing sources against the whole diff. No mission, guarantee, policy, enforcement mechanism, or response promise is added.

    Changed surface Standards checked Framework docs checked Result
    profile/README.md Documentation Model, Natural Language, Writing Guide, Markdown, Documentation, README-Driven Context; relevant Issue 9 rules None (no framework-specific docs). Facts match the pinned MSX home page and repository README. Aligned; the brand heading is the accepted branding difference in the delivery leaf.
    AGENTS.md Natural Language, Writing Guide, Markdown; ordered and verifiable agent instructions None (no framework-specific docs). Descriptions match README and CONTRIBUTING. Fixed in this PR; exact instruction order and paths are preserved.

    Convergence, plan, and review

    The scoped convergence command is:

    gh issue list --repo MSXOrg/.github --state open --search 'documentation-writing-alignment in:title' --limit 25 --json number,title,body,url

    It returns delivery leaves #16, #17, and #18. The two-file diff satisfies only #17. The form and reporting-policy asks are not satisfied by this change, so no additional closing reference is added. The native blocked-by query returns an empty list.

    The issue plan records source review, small commits, early draft creation, factual and route checks, and validation evidence. This PR carries the final alignment, convergence, and review record.

    The explicit command gh pr edit 20 --repo MSXOrg/.github --add-reviewer '@copilot' succeeds after the final push. The final-source review is APPROVED for e90ab70966ccfa12f7c20a486fb40f5846062c9a, with zero inline comments and no active review issues. Its remote review check completed with success. This is a review result, not a Markdown/link CI result.

    The PR remains open and draft, assigned to its author. GitHub auto-merge is null; Agent merge is disabled and its merge action is false. No merge or merge-automation change is made. The repository has no versioned producer route in this source tree, so no release decision block or release label is added.

  4. MariusStorhaug commented on Nov 11, 2026

    @MariusStorhaug
    MemberAuthor

    Campaign merge hold (2026-11-11): the user explicitly selected "Hold the six merges until validation is available (Recommended)". The current default branch has no authored validation workflow and this PR has no actual validation checks; manual prose/interface inspection is not counted as CI. Hold #20 until actual validation is available or a new explicit owner decision changes this hold. This is not authorization to add tooling, change rules, waive checks, or revive withdrawn validation work. Prepared source and existing PR/Agent-merge settings stay unchanged.

  5. MariusStorhaug commented on Nov 11, 2026

    @MariusStorhaug
    MemberAuthor

    Fresh exact-head preparation - 2026-11-11

    The fresh review covers head e90ab70966ccfa12f7c20a486fb40f5846062c9a
    against actual base 0c67251812ea306543f3a14ab473ae357cfb76ac.
    Both live IDs are unchanged. The isolated worktree is clean and its relevant
    file blobs match that exact head. The diff contains only AGENTS.md and
    profile/README.md (9 added lines, 2 removed lines). No source, policy,
    settings, labels, automation, or merge change is made.

    Fresh check Exact command or retained operation Result
    Scope and source diff git --no-pager diff 0c67251812ea306543f3a14ab473ae357cfb76ac...e90ab70966ccfa12f7c20a486fb40f5846062c9a -- AGENTS.md profile\README.md Re-read the complete two-file diff against the actual base. No content decision or blocking prose finding.
    Whitespace git diff --check 0c67251812ea306543f3a14ab473ae357cfb76ac...e90ab70966ccfa12f7c20a486fb40f5846062c9a Passed, exit 0.
    Content, headings, read order, wrappers Re-run the 12 acceptance assertions retained in this PR's technical evidence, with the explicit live base/head and blob checks. 12/12 passed, 0 failed. Both H1 texts, the brand heading/anchor, Read in this order:, README-then-CONTRIBUTING paths, and both exact wrapper syntaxes remain intact.
    Profile sentences Strip Markdown links from the three body sentences and count words. 14, 8, and 15 words. Source facts match the pinned MSX index and actual README/CONTRIBUTING contents. No full STE-conformance claim.
    Markdown lint Command below; cached markdownlint-cli2 0.24.0 / markdownlint 0.42.0. Passed, exit 0; Linting: 2 files. Direct library results independently return both actual file keys, each with zero violations. This is not an empty scan.
    Canonical links Both real curl.exe GET commands below, with the actual response bodies retained and inspected. 2/2 HTTP 200 at their unchanged canonical URLs; documentation and community-default content found.
    Native Markdown interface Both exact-head sources sent to gh api --method POST markdown --input - with mode=gfm, context=MSXOrg/.github. 2/2 rendered files pass. Profile: 1 H1, 2 paragraphs, 2 canonical links. AGENTS: 1 H1, 1 paragraph, 1 ordered list with 2 items, links README.md then .github/CONTRIBUTING.md.

    The authoritative current shared config is
    MSXOrg/docs at f9b335d0b78a3eead0b7efa573936e86cb1e7265,
    path .github/linters/.markdown-lint.yml,
    blob d48dd486e4d3a968fceee23a62a84a71694b88c2.
    The retained bytes have SHA256
    e20531ba6049449453700f72d8bbcb2d6ae136e016e06c022f69d30686e261dc.
    This blob is identical to the campaign's original pinned configuration.
    The config and response/render evidence remain in session artifacts, outside
    the repository. No dependency was installed and no repository validator,
    configuration, test, or CI file was added.

    $artifacts = 'C:\Users\marst\.copilot\session-state\c6b62647-1f95-4d7e-9c4a-e0510d6b64cb\files'
    $config = "$artifacts\shared-markdown-lint-f9b335d0.yml"
    npx --no-install --offline markdownlint-cli2 --config $config 'AGENTS.md' 'profile\README.md'
    
    curl.exe --fail --location --silent --show-error --max-time 60 --output "$artifacts\fresh-2026-11-11-msx-docs.html" --write-out 'HTTP %{http_code}; URL %{url_effective}' 'https://msx.no/docs/'
    curl.exe --fail --location --silent --show-error --max-time 60 --output "$artifacts\fresh-2026-11-11-community-defaults.html" --write-out 'HTTP %{http_code}; URL %{url_effective}' 'https://github.com/MSXOrg/.github'
    
    $head = 'e90ab70966ccfa12f7c20a486fb40f5846062c9a'
    foreach ($path in @('profile/README.md', 'AGENTS.md')) {
        $text = (git show "${head}:$path") -join "`n"
        @{ text = $text; mode = 'gfm'; context = 'MSXOrg/.github' } |
            ConvertTo-Json -Compress |
            gh api --method POST markdown --input -
    }

    The CLI summary 0 issues in 0 files counts files with reported issues.
    The run explicitly reports Linting: 2 files. An additional invocation of
    the same cached core linter, with the same loaded authoritative YAML config,
    returns this non-empty file result set:

    {
      "linter": "markdownlint 0.42.0",
      "fileCount": 2,
      "violations": 0,
      "results": {
        "AGENTS.md": [],
        "profile\\README.md": []
      }
    }

    The factual review re-reads the campaign-pinned MSX index at
    1b0d4893c8fefabe604d04393068a8ff6f848082, the pinned Natural Language,
    Writing Guide, and Markdown guidance, and this worktree's root README and
    contribution guide. The profile only describes shared guidance and GitHub
    default-file behavior. Both agent descriptions match their target documents.
    The accepted brand text and behavior remain unchanged.

    Current review, checks, and effective protections

    gh api graphql --input - confirms reviewDecision=APPROVED,
    mergeable=MERGEABLE, mergeStateStatus=CLEAN, and 0 review threads,
    with no further thread page. Review
    5768290832
    is APPROVED on the exact live head. The older 5b6191d... review is DISMISSED
    and is not current approval evidence. REST review comments total 0.

    gh api repos/MSXOrg/.github/commits/e90ab70966ccfa12f7c20a486fb40f5846062c9a/check-runs
    reports one completed successful run, copilot-pull-request-reviewer.
    Its action is Running Copilot Code Review, event dynamic. This is review
    execution, not Markdown/link validation.

    gh pr checks 20 --repo MSXOrg/.github and the same command with --required
    both return no checks reported, exit 1. GraphQL's status rollup is null.
    The legacy status API returns state=pending with 0 status contexts.
    There are no reported failing check runs or legacy failure contexts.
    Two app check suites (113345654978, 113345656479) remain queued with null
    conclusion, but each suite has 0 check runs; they are not passed checks.
    The third suite is the successful review execution.

    Hosted Markdown/link CI is still absent, not passed. The source tree has
    no validation workflow/scripts/configuration. This local operational evidence
    does not install or reinterpret a hosted required check.

    gh api repos/MSXOrg/.github/branches/main/protection returns HTTP 404,
    Branch not protected, but it is not evidence that no protections apply.
    gh api repos/MSXOrg/.github/rules/branches/main and
    gh api repos/MSXOrg/.github/rulesets/19735160 confirm the active inherited
    organization ruleset GitHub Flow:

    • no deletion, no force push, and required linear history;
    • pull-request-only squash merge;
    • stale-review dismissal, code-owner review, last-push approval, and thread
      resolution requirements;
    • an extra approval requirement for unattributed changes;
    • required_approving_review_count=0, with the requirements above still active;
    • no named required-status-check rule in the effective rule list.

    The base has no .github/CODEOWNERS, root CODEOWNERS, or docs/CODEOWNERS.
    No code-owner identity is inferred. current_user_can_bypass reports
    pull_requests_only; this capability is not used. No protection or bypass
    setting is changed.

    The PR is open and non-draft, with auto_merge=null, and it is not merged.
    The exclusive global merge slot remains held by Process/root. This preparation
    does not grant or use that slot. No genuine content decision or source/access
    blocker remains.

  6. MariusStorhaug commented on Nov 11, 2026

    @MariusStorhaug
    MemberAuthor

    Completed by the ordinary exact-head guarded squash of #20 on 2026-11-11. Accepted head: e90ab70966ccfa12f7c20a486fb40f5846062c9a; squash/main: c90c09d7b501edbe919cef222f7cc1ce6004b810; actual prior main: d3d56f6d40df924831d836c373c87a9680b77a08. Native exact-head approval, zero fully paginated threads, prerequisites, and effective protections were read before merge. No admin, force, bypass, alternate approval, or settings change was used. Fresh Markdown/native-render/link/interface validation was operationally accepted; hosted source-validation CI remains absent, not passed. Post-merge full-tree comparison proves that the only changes from prior main are the exact accepted AGENTS and profile README blobs; both thin wrappers and every earlier accepted README/contribution/feature/security/support blob remain exact. No snapshot suite or recognized PR template exists. Actual main integration, delivery-leaf closure, and absence of the exact remote topic branch are verified. These Git-served entry files require no invented Pages, package, live-agent, or consumer-rollout result.

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions