[documentation-writing-alignment] Clarify repository entry points for contributors and agents

Describe the change

Context and request

Contributors, PSModule repository maintainers, and agents need accurate first-read context for this organization-defaults repository. The writing-alignment review uses PSModule/.github source 4e0092de8f208b11e0d4607ced93471607aa748e and the fixed MSX documentation baseline. This Task owns one focused documentation-only draft PR for the entry points README.md, AGENTS.md, and profile/README.md.

Confirmed evidence

Source text or observed fact	Expected result and authority
`README.md` identifies the special public repository and says GitHub uses its files when a repository has no corresponding file, but does not name its audience or explain the issue-template folder override.	State the audience and supported default-file interface concisely. README-Driven Context: Target audience requires an explicit audience and supported interfaces. GitHub default-file guidance distinguishes individual fallback files from a local issue-template/configuration folder, which replaces the inherited folder.
`AGENTS.md` directs the reader to the README for how defaults are "enforced"; the README describes GitHub fallback behavior, not repository enforcement.	Describe the actual read purpose and retain the ordered, imperative README-then-contribution sequence. A contract is not proof of enforcement; see Documentation Model and executable agent text.
`profile/README.md` uses the image alt text `Landscape`. Direct inspection of the image shows small robots around connected GitHub and PowerShell symbols.	Give the image concise, descriptive alt text under Markdown: Style beyond the linter. Preserve the image URL and the organization mission heading.

Acceptance criteria

A first-time reader can identify the repository purpose, its contributor/maintainer audience, and the GitHub default-file interface from a concise, present-tense README.
The README states default-file precedence accurately, including the issue-template/configuration folder override, without claiming that defaults are copied into consumer clones or that repository CI enforces these rules.
Agent instructions retain the exact read order and paths. Descriptive wording names fallback behavior rather than unsupported enforcement.
The profile image has descriptive alt text grounded in direct image inspection. Its heading and image URL remain unchanged.
Prose follows en-US and source-supported ASD-STE100 Issue 9 writing practices. Descriptive prose is declarative and evergreen; direct instructions stay imperative.
Only README.md, AGENTS.md, and profile/README.md change. Preserve paths, existing headings/anchors, links, community policies, wrapper syntax, and all machine interfaces.
The draft PR records concrete before/after evidence, affected-link inspection, existing applicable static checks or their absence, and the limits of STE verification. It remains draft, open, and unmerged with no auto-merge or Agent merge.

Constraints and reviewed differences

This Task does not redesign the documentation, create a spec/design hierarchy, add validation tooling or dependencies, invent enforcement, or change GitHub settings. The title Infusing GitHub with PowerShell is an organization mission/brand statement, not an implementation claim, and stays unchanged. .github/copilot-instructions.md and .claude/CLAUDE.md remain thin, valid pointers to AGENTS.md. .github/CONTRIBUTING.md, SUPPORT.md, and SECURITY.md stay outside the write scope of this Task. The detailed Issue 9 procedural review supersedes their earlier overview no-change classification. Separate PSModule/.github#94 owns their concrete reading, condition-first, and short reporting instructions; policies, routes, headings, emails, and links stay unchanged. The attributed Contributor Covenant 3.0 in .github/CODE_OF_CONDUCT.md is controlled external policy text, not a local STE rewrite target.

Technical decisions

Use the fixed MSX baseline for Natural Language, Writing Guide, Documentation, Documentation Model, and artifact templates. These special-purpose entry points keep their native formats; they are not capability specs or full task guides. Apply the official STEMG explanation, FAQ, and Issue 9 rules/dictionary where detail matters. Keep the manual and extracted reference text local; word counts and lint are not proof of full STE conformance.

The tracked source tree contains no Markdown/link validation script or linter configuration. A registered historical validation workflow is not evidence that the file exists on main; the content API returns 404 for that workflow path. Use existing relevant tools if available and report manual inspection honestly. Do not revive the withdrawn validation effort or restore a PR template.

Implementation plan

Read the three owned sources and their thin instruction pointers. Establish the exact source identity, target audience, GitHub inheritance evidence, and before-change acceptance evidence before editing.
Make a small first commit that clarifies README context and the agent read purpose, then push and open the focused draft PR early with this Task as its only closing delivery leaf.
Read the profile image through the authenticated image tool and make a separate small commit for accurate alt text, without replacing the image or mission heading.
Inspect the full diff for en-US, STE practices, evergreen descriptive wording, direct instructions, preserved headings/paths, and all affected links. Run existing applicable checks without adding tooling.
Update this Task and the PR with completed plan evidence and source-bound before/after results. Leave the PR in draft for user review.

Repository inventory and retained differences

The comparative review covers PSModule/.github source 4e0092de8f208b11e0d4607ced93471607aa748e: 82 tracked files, comprising 9 Markdown sources, 5 native issue-form/configuration YAML sources, 2 Git settings files, and 66 media assets. The scope is documentation clarity, en-US, source-supported STE practices, artifact format, and evergreen declarative descriptive prose. Only confirmed prose/format gaps become campaign delivery Tasks in this repository; no functional, tooling, policy, or restructuring work is inferred.

Reviewed surface	Classification and evidence
`README.md`, `AGENTS.md`, `profile/README.md`	Entry-point gaps owned by this Task: audience/interface precision, fallback-versus-enforcement read purpose, and descriptive alt text. Existing mission wording and all headings remain.
`.github/ISSUE_TEMPLATE/01-bug.yml`, `02-patch.yml`, `99-general.yml`	Direct-intake prose gaps are independently owned by PSModule/.github#91, with no shared write paths or prerequisite order.
`.github/CONTRIBUTING.md`	No change: concise canonical pointers; the MSX contribution URL and Process-PSModule documentation URL were fetched successfully. Shared standards are not copied locally.
`.github/SUPPORT.md`, `.github/SECURITY.md`	No change: direct procedure steps, specific evidence, private reporting routes, and existing policy force. The three relative links from Support resolve to tracked files. Imperatives are required procedure syntax, not a defect in declarative prose.
`.github/copilot-instructions.md`, `.claude/CLAUDE.md`	No change: both resolve to root `AGENTS.md`. Native Markdown-link and `@../AGENTS.md` forms remain executable thin pointers.
`.github/CODE_OF_CONDUCT.md`	Controlled external policy text: compared to the canonical Contributor Covenant 3.0 source. Preserve its wording, attribution/license, local support email, and enforcement policy. Do not invent a present-state claim or rewrite external text for STE.
`.github/ISSUE_TEMPLATE/10-feature.yml`	Existing-owner boundary: PSModule/.github#89 supersedes the older main-branch copy and is held unchanged by its existing owner. That owner confirmed no conflict on the other forms. This campaign does not claim that the old copy is aligned or modify the approved replacement.
`.github/ISSUE_TEMPLATE/config.yml`	No prose change: preserve the machine key `blank_issues_enabled: true`.
`.gitattributes`, `.gitignore`	No change: native settings/patterns and accurate section labels are not narrative resources.
`media/`	66 graphic assets, including generated artwork and external icons. No tracked narrative page links these local asset paths. Preserve the artwork and source copyright/license metadata; the externally hosted profile banner is inspected separately for its alt text.

No tracked license file, generated narrative documentation, release record, decision record, research document, capability spec/design, or documentation-template hierarchy exists. None is created to satisfy a template. The canonical artifact template index was read; these entry points and native GitHub forms retain their own formats.

Source and validation boundaries

The shared criteria are fixed at MSXOrg/docs commit 1b0d4893c8fefabe604d04393068a8ff6f848082. The five required documentation/writing standards, Documentation Model, applicable template index, README guidance, comparative-review playbook, and delivery formats were read. The official STEMG explanation and FAQ were available. The official Issue 9 PDF was downloaded for local reference and matched the published MD5 9c720341c350ed77943b2c73d01c716f; its rules for active voice, direct procedures, sentence structure, and descriptive text were consulted. The manual and extracted text are not republished. Static checks and word counts are not proof of full STE conformance.

The tracked source tree contains no Markdown/link validation script or linter configuration. GitHub still lists a historical community-validation workflow, but the workflow content path returns HTTP 404 on main; its old successful runs were for a withdrawn branch, not evidence of present enforcement. The withdrawn validation owner confirmed no active ownership of campaign form paths. PSModule/.github#87 remains separate unimplemented YAML validation work. No new linter, dependency, workflow, hook, retained prose snapshot test, or validation promise is introduced.

The environment references a parent ..\AGENTS.md that does not exist. The tracked root AGENTS.md, README, and local contribution guide were read in the defined order; no unavailable parent policy is invented.

Deferred observations after source inspection

The approved replacement in PSModule/.github#89, not only the older main-branch feature form, retains the lines "Thank you for suggesting a feature" and "Maintainers will review your feedback and decide how to route it." The existing owner reports a user-directed hold on that approved copy during separate testing-policy work. Feature prose therefore remains an explicit existing-owner hold; this campaign does not claim complete alignment for it, duplicate its PR, or override the preserved-copy decision.

The SVG title in media/githubwatchers.svg reads GitHub Tags. This unused artwork-metadata observation is outside the narrative-prose change boundary: no tracked documentation page references the local media assets. The campaign preserves imported graphic content and attribution rather than adding an unrelated asset correction. No new issue or dependency is created for that observation.

Before-change audit

The worktree is clean at source 4e0092de8f208b11e0d4607ced93471607aa748e. The delivery branch is psmodule-entry-points. This is a native Task with no blocked-by dependencies and no native parent.

The manual acceptance checks precede the edits:

Check	Before-change evidence	Required result
First-read audience and interface	`README.md:3-5` names the special repository and general fallback, but no reader roles or supported file types.	Name maintainers and contributors of PSModule repositories and the community-file and issue-form interface.
File and folder precedence	The README has no issue-template/configuration folder exception.	Explain per-file fallback and the complete local `.github/ISSUE_TEMPLATE` override.
Agent read purpose	`AGENTS.md:5` says defaults are "enforced."	Describe GitHub default-file behavior. Keep the README-then-contribution order and exact paths as direct instructions.
Image alternative	`profile/README.md:3` says `Landscape`.	Describe the small robots around connected GitHub and PowerShell symbols, as seen through the authenticated image tool. Keep the heading and URL.

All seven agreed MSX source files at 1b0d4893c8fefabe604d04393068a8ff6f848082 are available and read. The official STE explanation, FAQ, and DOI record are available. The read-only local Issue 9 PDF has MD5 9c720341c350ed77943b2c73d01c716f, which matches Zenodo. The manual and extracted text stay local. The review applies the relevant rules, dictionary guidance, and domain terms; it does not claim full STE conformance.

The GitHub default-file documentation confirms local-file precedence, location order, and the complete issue-template/configuration folder override. The repository is public. These are GitHub behaviors, not repository CI claims.

There is no tracked Markdown/link script, linter configuration, test suite, or workflow source. GitHub still lists Community file validation, but the content API returns HTTP 404 for .github/workflows/Validate-Community-Files.yml on main. No validation tooling will be added or restored. Exact-head check status will be recorded after the pushes.

The thin .github/copilot-instructions.md and .claude/CLAUDE.md pointers both resolve to root AGENTS.md and need no change. Contribution, support, and security guidance retains the central or private routes. The controlled Contributor Covenant text stays unchanged. All files outside the three owned paths stay unchanged.

Establish source identity, source availability, and concrete before-change evidence.
Commit README and agent context, then open the focused draft PR.
Commit descriptive profile alt text separately.
Record exact-head acceptance, links, static checks, coverage limits, and draft retention.

User decision resolves the feature-copy hold

The main coordinator relayed the user's new decision verbatim: "Revise the prose and preserve the form behavior (Recommended)". The feature-form owner is authorized to revise prose in existing PSModule/.github#89 while preserving the form's machine contract, intake behavior, separate testing-policy cleanup, and existing PR lifecycle/Agent-merge settings. This resolves the earlier approved-copy hold; feature prose is included in the campaign's reviewed coverage rather than treated as a permanent exception.

The existing owner received the fixed MSX baseline, official STE sources, precise remaining prose evidence, compatibility constraints, and the requirement to refresh source-bound Task/PR evidence without asserting the old form blob remains unchanged. No duplicate issue/PR is created and neither new implementation child gains write ownership of the feature form.

First commit and draft PR

Commit README context and direct agent read instructions: accc3a57df0556b3013dfacf5c3876deb9d0a34c.
Push the first meaningful change and open the focused draft PR before the separate image change.

The first commit changes only README.md and AGENTS.md. git diff --check passes. GitHub's Markdown renderer shows the expected README paragraphs and the same two ordered read targets. The documented local files exist. The new GitHub reference and unchanged central contribution routes are available.

The image is directly inspected. Its descriptive alt text is the separate next commit. The profile heading and image URL remain unchanged. Exact-head and coverage evidence follows that push. The PR stays draft, open, and unmerged, without auto-merge or Agent merge.

Profile commit

Directly inspect the canonical attachment through read_github_image.
Commit and push only the descriptive alt-text change in 9f6a8a5c9618976ac3f337df3d00f764fb8eecac.

The alt text is Small robots around connected GitHub and PowerShell symbols. The before/after diff changes no other profile content. The mission heading and canonical image URL remain exact. GitHub's Markdown renderer retains the heading and exposes the descriptive alt attribute.

Both small commits are pushed. The final acceptance audit now uses the exact completed head, not the initial draft head. The PR remains draft, open, and unmerged.

Refined community-guidance classification

Detailed consultation of the official procedural rules identifies a small community-guidance delivery boundary that supersedes the earlier overview-level no-change judgment for .github/CONTRIBUTING.md, .github/SUPPORT.md, and .github/SECURITY.md. PSModule/.github#94 owns their focused draft PR: a concrete reading action, a finite condition-first before-posting instruction, private-reporting availability before the Security-tab action, and shorter security reporting-category/evidence instructions.

This is not a policy correction. All reporting categories, optionality, private routes, emails, supported-version rules, repository-policy precedence, public-disclosure prohibitions, coordination responsibilities, links, headings, and normative force remain unchanged. The new child ca241e23-f496-49dd-976b-2cac4a975364 has those three paths exclusively. Other entry-point/form children keep their existing non-overlapping ownership; the Contributor Covenant, native agent pointers, machine configuration, and graphic assets remain unchanged.

Completed entry-point audit

The focused draft PR is complete at exact head 9f6a8a5c9618976ac3f337df3d00f764fb8eecac, compared with source 4e0092de8f208b11e0d4607ced93471607aa748e. The remote PR head, local HEAD, and upstream match. The worktree is clean. The comparison contains two small commits and only README.md, AGENTS.md, and profile/README.md.

Acceptance result	Evidence
Purpose, audience, and supported interface are explicit.	README names maintainers and contributors of PSModule repositories and the contribution, conduct, security, support, and issue-form defaults.
Precedence is accurate and source-bound.	README states per-file fallback, supported `.github`/root/`docs` order, and the complete local issue-template/configuration folder override. The official GitHub reference is available and supports these statements. No clone-copy or CI enforcement claim is added.
Agent instructions remain executable.	Both steps use `Read`. `README.md` precedes `.github/CONTRIBUTING.md`, with exact paths. Unsupported enforcement wording is removed.
Image alternative matches direct observation.	The authenticated attachment shows small robots around connected GitHub and PowerShell symbols. The alt text names that content. The mission heading and canonical image URL remain exact.
Stable interfaces and scope are preserved.	All three existing headings and anchors are unchanged. GitHub renders the three files at the immutable head, including the two ordered instructions and descriptive image `alt` attribute. Every other repository file is unchanged.
Writing and format review is complete.	Changed prose uses en-US, present-tense descriptions, active wording, stable technical terms, and imperative instructions. Special-purpose formats stay intact. The PR contains the per-surface standards/alignment table.

git diff --check 4e0092de8f208b11e0d4607ced93471607aa748e 9f6a8a5c9618976ac3f337df3d00f764fb8eecac passes. One-time invariant inspection verifies the exact changed-path set, unchanged headings, ordered read paths, and image URL. The new GitHub reference, canonical attachment, documented local targets, and unchanged central contribution links are available. Both thin instruction pointers resolve to root AGENTS.md.

The explicitly requested Copilot review is APPROVED on this exact head and reports no active issues. There are zero inline review comments.

Existing CI evidence is separate: after the review, the exact head still has zero check runs, zero status contexts, and zero workflow runs. The combined status is pending with no contexts, not a test result. No tracked Markdown/link suite or linter configuration exists. The historical registered validation workflow still has no source file on main (HTTP 404). No tooling, dependency, workflow, PR template, or retained snapshot test is added.

All seven agreed MSX sources are read at 1b0d4893c8fefabe604d04393068a8ff6f848082. The official STE explanation, FAQ, and DOI record are available. The read-only local Issue 9 PDF MD5 matches Zenodo: 9c720341c350ed77943b2c73d01c716f. The manual and extracted text stay local. This is a source-guided writing review, not a claim of full STE conformance or certification.

No live consumer-repository inheritance experiment, issue submission, settings change, or interactive screen-reader session is run. Rendered-alt inspection is not a full accessibility test. There is no automated Markdown/link suite to execute.

The thin instruction pointers need no change. Contribution, support, and security guidance retains the central and private routes. The controlled Contributor Covenant text stays unchanged. All forms, configuration, policies, media, and validation files remain outside the diff. The scoped campaign issue search finds no additional delivery leaf satisfied by this change; the PR closes only #90.

Read the owned sources and pointers; establish exact identity, official inheritance evidence, and before-change acceptance evidence before editing.
Commit README and agent context, push, and open the focused draft PR early.
Inspect the image directly and make the separate small alt-text commit.
Inspect the full writing, paths, headings, links, rendered output, and exact-head checks without adding tooling.
Record source-bound before/after results and completed plan evidence in this Task and the PR.

The PR remains DRAFT, OPEN, and UNMERGED. Auto-merge is null. Agent merge is disabled and its merge action is false. No implementation or source-availability blocker is found. The requested draft retention remains in effect; the clean review does not waive absent CI or authorize readiness or merge.

Companion-guide ownership refinement

The detailed Issue 9 procedural review supersedes the earlier overview no-change classification of .github/CONTRIBUTING.md, .github/SUPPORT.md, and .github/SECURITY.md. Separate PSModule/.github#94 owns their concrete reading, condition-first, and short reporting instructions. Policies, routes, headings, emails, and links stay unchanged.

The stale assertion is replaced in this Task body. The PR companion-document evidence and non-closing references identify that separate ownership. This Task and its PR still own only README.md, AGENTS.md, and profile/README.md. The three guides are not edited here. The thin pointers and controlled Contributor Covenant retain their no-change result for this Task.

All five original plan checkboxes are complete. Exact source head 9f6a8a5c9618976ac3f337df3d00f764fb8eecac, the two commits, acceptance evidence, and clean review remain unchanged. The PR still closes only #90, remains draft/open/unmerged, and has neither merge feature enabled.

Repository writing-review handoff

The requested documentation review and focused-PR handoff are complete for PSModule/.github. The comparison starts at 4e0092de8f208b11e0d4607ced93471607aa748e and uses the fixed MSX writing baseline. This is a draft-delivery milestone, not source integration or a claim that the delivery Tasks are closed. No merge or automatic landing was performed.

Inventory and delivery boundaries

The 82 tracked files comprise 9 Markdown sources, 5 native issue-form/configuration YAML sources, 2 Git settings files, and 66 media assets. All 14 human/agent/native-schema documentation sources were read and classified. Ten documentation sources have focused changes across the four PRs below. Their write sets are disjoint; no shared index or heading rename is needed.

Part	Owned paths	Delivery leaf and PR	Exact reviewed head
Repository and profile entry points	`README.md`, `AGENTS.md`, `profile/README.md`	PSModule/.github#90, PSModule/.github#93	`9f6a8a5c9618976ac3f337df3d00f764fb8eecac`
Bug, patch, and general intake prose	`.github/ISSUE_TEMPLATE/01-bug.yml`, `02-patch.yml`, `99-general.yml`	PSModule/.github#91, PSModule/.github#92	`a6c020d4e2227397e4766f3f6daefb8d360116a6`
Community guidance	`.github/CONTRIBUTING.md`, `.github/SUPPORT.md`, `.github/SECURITY.md`	PSModule/.github#94, PSModule/.github#95	`1c5bb816275f066b3c9a5752ebc8643a155eb2ae`
Feature intake prose, reused existing delivery	`.github/ISSUE_TEMPLATE/10-feature.yml`	PSModule/.github#88, PSModule/.github#89	`7eedb8a44c00bfa0f38d541ea88a7d7d791eaa19`

The three new PRs remain draft, open, and unmerged. The existing feature PR retains its user-directed open, not-draft, unmerged state. Auto-merge is null on all four, and Agent merge is disabled. Each PR has exactly one native Task closing leaf. All four Tasks remain open, with completed implementation-plan bodies and source-bound audit evidence. The new deliveries use two small commits each and opened drafts before their second changes. The feature revision uses one small ordinary commit on its existing branch; no duplicate PR was created.

Confirmed outcomes and preserved contracts

The entry points name the audience, explain actual GitHub default-file precedence, keep the executable read order, and describe the inspected profile image. The forms use direct prompts without courtesy filler or response-time promises. Community instructions state prerequisites before actions and keep report categories and evidence in short sentences. Descriptive resource prose remains current-state and declarative; procedure and agent actions remain imperative.

The orchestrator read every complete exact-head diff. One-time static maintenance inspection independently confirmed all three bug/patch/general machine contracts, ten permitted prose values, and four exact code examples. The feature comparison permits only its three display values; its non-prose contract and removed-test state are unchanged. Community inspection confirmed six stable headings, eight exact links, three local targets, two mailto routes, supported-version policy, public-disclosure prohibition, and private handling responsibilities. Direct review also checked report-category scope, evidence, optionality, and condition ordering. The full four-PR inventory contains ten modified sources and no added or deleted repository file.

Retained differences and deferred observations

.github/copilot-instructions.md and .claude/CLAUDE.md remain valid thin native pointers to AGENTS.md. Their syntax and targets need no change.
.github/ISSUE_TEMPLATE/config.yml retains blank_issues_enabled: true. Git settings and their concise section comments remain unchanged.
The attributed Contributor Covenant 3.0 remains controlled external policy text. Its wording, license/attribution, and local private reporting address are not rewritten for STE.
The organization mission heading and profile image URL remain exact. The 66 local graphic assets and their external attribution/license metadata remain unchanged. The unused media/githubwatchers.svg title reads GitHub Tags; no tracked narrative page references local media assets, so this is a deferred artwork-metadata observation, not an added prose PR or issue.
No tracked license file, generated narrative docs, release record, decision record, research document, capability spec/design, or documentation-template hierarchy exists. None is created or converted merely to fit a template.
The initial overview no-change judgment for the community guides is superseded by the detailed procedural review and their focused delivery above. The feature-copy hold is resolved by the user's prose-revision decision, not treated as a permanent writing exception. Its separate testing-policy/lifecycle hold remains intact.

Sources, verification, and limits

The required MSX documentation/writing/model/template sources were read at the fixed commit. The official STEMG explanation, FAQ, and Issue 9 DOI/PDF were available. The PDF MD5 matched Zenodo, 9c720341c350ed77943b2c73d01c716f. Relevant rules and selected dictionary entries were consulted locally; the manual and extracted text are not republished. This is a source-guided writing-practice review, not full STE certification. A prose scan, sentence count, static check, or approval is not proof of complete STE conformance.

All four exact heads have clean automated review results, recorded in their PRs. The live review-check state is narrower than general CI: #93 has no check runs or status contexts; #92, #95, and #89 each have a successful copilot-pull-request-reviewer check. These review checks do not establish Markdown lint, link-checker, test-suite, or broader CI execution. The source tree has no authored Markdown/link validation suite or workflow. The registered historical validation definition returns 404 on main; it is not restored or dispatched.

Existing whitespace inspections pass. Existing strict YAML passes for the feature form. The other three forms retain six unchanged long-comment-URL errors and three document-start warnings, down from sixteen line-length errors; no new diagnostic or suppression is introduced. PSModule/.github#87 remains separate, unimplemented YAML validation work. No validator, dependency, hook, workflow, runtime simulation, or retained source/prose snapshot test is added.

No live issue-form submission/routing test, downstream inheritance experiment, mailbox delivery, security report, or interactive screen-reader test was performed. The source/link/render/alt inspections are the evidence for these documentation changes. The referenced parent ..\AGENTS.md is absent; the tracked root instructions and required README/contribution sequence were followed without inventing parent policy.

No implementation or source-access blocker remains for the requested focused-PR handoff. The explicit validation limits and the independent feature testing-policy hold remain visible; neither author review nor this closeout marks a PR ready or waives those limits.

Navigation Menu

Repository navigation

[documentation-writing-alignment] Clarify repository entry points for contributors and agents #90

Describe the change

Context and request

Confirmed evidence

Acceptance criteria

Constraints and reviewed differences

Technical decisions

Implementation plan

Repository inventory and retained differences

Source and validation boundaries

Deferred observations after source inspection

Before-change audit

User decision resolves the feature-copy hold

First commit and draft PR

Profile commit

Refined community-guidance classification

Completed entry-point audit

Companion-guide ownership refinement

Repository writing-review handoff

Inventory and delivery boundaries

Confirmed outcomes and preserved contracts

Retained differences and deferred observations

Sources, verification, and limits

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

[documentation-writing-alignment] Clarify repository entry points for contributors and agents #90

Description

Describe the change

Context and request

Confirmed evidence

Acceptance criteria

Constraints and reviewed differences

Technical decisions

Implementation plan

Activity

MariusStorhaug commented on Nov 4, 2026

Repository inventory and retained differences

Source and validation boundaries

MariusStorhaug commented on Nov 4, 2026

Deferred observations after source inspection

MariusStorhaug commented on Nov 4, 2026

Before-change audit

MariusStorhaug commented on Nov 4, 2026

User decision resolves the feature-copy hold

MariusStorhaug commented on Nov 4, 2026

First commit and draft PR

MariusStorhaug commented on Nov 4, 2026

Profile commit

MariusStorhaug commented on Nov 4, 2026

Refined community-guidance classification

MariusStorhaug commented on Nov 4, 2026

Completed entry-point audit

MariusStorhaug commented on Nov 4, 2026

Companion-guide ownership refinement

MariusStorhaug commented on Nov 4, 2026

Repository writing-review handoff

Inventory and delivery boundaries

Confirmed outcomes and preserved contracts

Retained differences and deferred observations

Sources, verification, and limits

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions