Skip to content

Focus organization feature intake on consumer needs and expected behavior #14

Closed

Description

Describe the change

Let feature requesters describe their need, motivation, and expected behavior without choosing an implementation. The organization-owned feature form is the shared intake; no consumer-local copies are added. The consumer-need prompts, direct requests, conditional failure/limit example, canonical planning/routing links, and factual feedback/internal-planning boundary are preserved.

The confirmed Epic/PBI scope does not remove technical Task/Bug decisions or delivery plans. MSXOrg/docs#230 merged on 2026-11-03 at 8c9d9353eb154d6072b3ed1d825a78d58a4665d3; the prior unmerged-source statements are historical. The form links the current planning and routing pages.

Acceptance criteria

  • The form asks who benefits, why the need matters, and for a situation/action/expected-result example; a failure or limit example is conditional. No technical solution or special scenario format is required.
  • Preserve the existing form name/title/top-level description, exact feature and triage labels, absent native issue type, field order/IDs/types/required flags, one required description textarea, and blank-issue availability.
  • Keep external feedback distinct from linked internal planning and preserve technical Task/Bug plans.
  • Ship no added source-string/prose/shape snapshot suite or replacement validator. Record honest one-time static, rendering, and live-link evidence instead of calling it runtime coverage or hosted CI.
  • The existing MSXOrg/.github#15 closes only this Task after authorized review and merge. Do not bypass code-owner, last-push, thread, validation, or the coordinator's exclusive merge-slot prerequisites.

Constraints and non-goals

Only the feature form remains changed against main. No Bug/patch/general forms, other community files, Task/Bug planning policy, consumer copies, live labels, workflow/configuration, toolchain, CI, rulesets, scheduler, or merge settings are changed. Separate MSXOrg/.github#11/MSXOrg/.github#12 validation and MSXOrg/.github#13 hooks are not revived here.

Technical decisions

The complete 119-line FeatureIntake.Tests.ps1 file was added by this PR. All 12 cases asserted fixed YAML metadata, structural shape, exact phrases/URLs, or blank configuration. Its built-in Markdown conversion exercised no owned runtime. The current testing rule prohibits those added source-string and snapshot assertions. The user-directed review supersedes the earlier limit on removing them: delete the whole added file, with no redesign, simulation, replacement test/tooling, or new issue. A fresh pre-removal run passed all 12 cases, so the removal is policy conformance, not hiding a failure. No owned-runtime coverage or conflicting user content decision was found.

Removal commit 9a4da3a0dacf7cfc68cad80270884886bcdc1ad9 changes only that added test file. The feature form is byte-for-byte identical to candidate 589285cfb6c2ecc761c5308de4527d2dd2c54bd4, blob 19d6abbbf5b1a4a5b48ce5710be9f7e79f0be742. Against base 0c67251812ea306543f3a14ab473ae357cfb76ac, the PR now contains one modified feature form, 17 additions and 7 deletions. No tests remain in the final tree, and no current suite pass is claimed.

The fixed writing baseline and official STE guidance remain the sources for the unchanged prose. Validation defaults have separate provenance: current Docs.yml selects Super-Linter 4ce20838b8ab83717e78138c5b3a1407148e0918 without a YAML override. Its published default configuration, blob 2aa49bd1867e24acdea4172191922df6135b69c6, is used only from session storage. It is not installed or described as this repository's CI configuration; no rules are weakened. Exact default bytes are preserved, and dependencies/python/yamllint.txt pins the matching yamllint==1.38.0.

Implementation plan

  • Read the current testing authority and every added-suite case; verify no owned-runtime coverage or conflicting content decision and record the passing pre-removal baseline.
  • Remove only the added suite in one focused commit without a replacement; preserve the form bytes and every other source file.
  • Inspect the YAML/interface once, compare original/prior/candidate diagnostics with the exact published validator defaults, render Markdown through GitHub, and check both actual canonical pages/anchors.
  • Refresh final-head review/threads/checks/effective protections, record current readiness and the global merge hold, and hand off the exact candidate without merging.

Current verification evidence

Actual command or operation Result
python - (one-time PyYAML recursive inspection and raw Git-byte comparison) 20 nodes, 6 mappings, 2 body elements, 1 required textarea. All non-prose keys/order/types/values and blank configuration match the original base; current form bytes exactly match 589285c.
yamllint --format parsable --config-file $configuration $target.Path; repeat with --strict, using the published default above All 6 original/prior/candidate runs in normal and strict modes return exit 0 with 0 diagnostics; installed version 1.38.0 matches the validator dependency pin. No baseline formatting change.
gh api --method POST markdown --input - with actual introduction, mode=gfm, context=MSXOrg/.github Native GitHub HTML contains exactly 2 canonical links.
python - (one-time unauthenticated HTTPS requests and actual HTML inspection) Both linked pages return HTTP 200; actual page anchors issue-planning and issue-hierarchy exist. Neither form link has a fragment.
git diff --name-status origin/main...HEAD and git diff --check Exactly one modified feature form; whitespace check passes.

These are static/interface/rendering/network observations, not owned-runtime tests, GitHub form-submission end-to-end coverage, or hosted CI. Earlier 12/13-test results and older automated reviews belong only to their recorded historical heads; they are not current-head readiness evidence.

The final explicitly requested Copilot review approves exact head 9a4da3a0dacf7cfc68cad80270884886bcdc1ad9 against base 0c67251812ea306543f3a14ab473ae357cfb76ac, with no active code issues or inline comments. All 5 submitted reviews are read: 4 historical COMMENTED and this APPROVED result. Complete thread pagination finds 0 threads. GitHub reports MERGEABLE/CLEAN and native review decision APPROVED. The only check run is the successful Copilot reviewer; there are 0 statuses and the GraphQL rollup is empty. No actually failing or named required check is reported, but Organization defaults validation has not executed at this head. Reviewer execution is not hosted form validation. Effective organization rules still preserve squash-only integration, stale-review dismissal, code-owner review, last-push approval, and resolved threads, with no named required-status-check rule. Native Task blockers are empty; separate validator MSXOrg/.github#12 remains unmerged. Missing execution is not a pass.

The PR remains open/non-draft. GitHub auto-merge is null, the merge queue is empty, and Agent merge is enabled only for reviews/CI/conflicts with merge_pr=false. No merge-setting change was made. Root holds an exclusive global merge slot elsewhere; no merge is authorized in this session until that slot is handed off. This Task stays open until its authorized reviewed PR is merged.

Activity

  1. MariusStorhaug commented on Oct 31, 2026

    @MariusStorhaug
    MemberAuthor

    Baseline structure and routing checks pass on the original form (4 tests, 0 failures/skips), and separate draft MSXOrg/.github#15 is open. This creates early visibility without pushing known failing tests. Consumer-prompt assertions and the form correction remain next; canonical source/readiness evidence is still pending.

  2. MariusStorhaug commented on Oct 31, 2026

    @MariusStorhaug
    MemberAuthor

    Exact consumer-prompt assertions ran before the form changed: the original form passes all 4 structure/routing tests and fails the 7 desired-prompt tests, with no failed discovery containers or skipped tests. The existing runner returns exit 1 as required; PowerShell lint is clean. The test-first commit remains local until the form correction makes the full suite green.

  3. MariusStorhaug commented on Oct 31, 2026

    @MariusStorhaug
    MemberAuthor

    The existing validation workflow was checked before finalizing the suite: its runner provisions Pester only, not powershell-yaml. The test decision is narrowed to dependency-free, whole-form structure assertions plus the existing independent YAML linter. This avoids imposing a parser-installation change on the separate CI delivery while retaining exact prompt, metadata, routing, and rendered-link checks.

  4. MariusStorhaug commented on Oct 31, 2026

    @MariusStorhaug
    MemberAuthor

    The feature-intake prompt change and dependency-free regression evidence are committed and pushed at 1004e86180ec984992e77b1ff88a6e087274b9e7 in draft MSXOrg/.github#15. All 11 tests pass without powershell-yaml; the original form still gives 4 passes and 7 intended failures, and anonymous native-type and quoted-required fixtures are rejected by the whole-form assertion. YAML lint, PowerShell lint, and whitespace checks pass. Current-head automated review and canonical source/readiness correspondence remain in progress.

  5. MariusStorhaug commented on Oct 31, 2026

    @MariusStorhaug
    MemberAuthor

    The frozen MSXOrg/docs#228 handoff is verified at 1c8f98cabe64b12aaa5fa9fb5f51b9d03f5de9de. It permits equally clear plain-language scenarios and preserves external feedback, native routing, and technical Task/Bug plans. Final correspondence calls for a direct routing-page link and conditional failure/limit examples, so those narrow assertions will fail before refreshing the form. Both whole-page canonical URLs already resolve; no new main-branch anchor or completed source publication is claimed.

  6. MariusStorhaug commented on Oct 31, 2026

    @MariusStorhaug
    MemberAuthor

    The frozen-source correspondence checks ran before the final form refresh: 10 tests pass and exactly 2 fail for the missing direct native-routing link and conditional failure/limit example, with no discovery failures or skips. The initial current-head Copilot round at 1004e86180ec984992e77b1ff88a6e087274b9e7 has no inline/open code issues; its summary correctly keeps source/publication and hosted validation evidence distinct. The new test-first commit remains local until the form correction passes all 12 tests.

  7. MariusStorhaug commented on Oct 31, 2026

    @MariusStorhaug
    MemberAuthor

    The frozen-source refresh is committed and pushed at 5edc236cf2bc365931483487a5a0d471b3779629. All 12 tests and shared YAML/PowerShell lint pass. The form links already-resolving canonical Planning and Hierarchy pages without unpublished anchors and includes a conditional failure/limit example. Metadata, external feedback, and one required free-text field remain intact. Anonymous experiments also accept ordinary English 'when' and reject explicit Gherkin solicitation. The live PR is verified as an open, independent draft targeting main with no auto-merge; a fresh exact-head review remains next.

  8. MariusStorhaug commented on Oct 31, 2026

    @MariusStorhaug
    MemberAuthor

    Frozen source correspondence and the PR evidence are reconciled at 5edc236cf2bc365931483487a5a0d471b3779629 against docs source 1c8f98cabe64b12aaa5fa9fb5f51b9d03f5de9de. The form uses the existing current Planning and Hierarchy routes, with no unpublished new fragments. Consumer examples, external-feedback separation, preserved native routing, and technical Task/Bug plans correspond to the handoff. The draft remains open for source publication and hosted validation/enforcement readiness; the refreshed exact-head review is now requested.

  9. MariusStorhaug commented on Oct 31, 2026

    @MariusStorhaug
    MemberAuthor

    The refreshed exact-head Copilot round and complete summary are verified at 5edc236cf2bc365931483487a5a0d471b3779629: no inline/open code issues or unresolved threads. All 12 focused tests and local lint/scope checks pass. The plan is checked off with explicit remaining source-publication and hosted validation/enforcement evidence; the native Task remains open and the independent PR remains draft for human review and landing readiness.

  10. MariusStorhaug commented on Nov 4, 2026

    @MariusStorhaug
    MemberAuthor

    The user-directed writing campaign confirmed the narrow correction within this existing outcome. Baseline 5edc236cf2bc365931483487a5a0d471b3779629 passes its 12 existing tests but retains thanks, a future linking promise, and question-form requests. The existing Task now records the test-first wording steps. The live PR is open and non-draft with GitHub auto-merge null; this correction will preserve that state and all merge settings.

  11. MariusStorhaug commented on Nov 4, 2026

    @MariusStorhaug
    MemberAuthor

    Before the form change, the direct-writing suite rejects candidate 5edc236cf2bc365931483487a5a0d471b3779629 with exactly 7 passes and 6 intended failures, 13 discovered tests, 0 skips, and 0 failed containers. Failures cover thanks/future-promise/direct introduction, consumer-need/motivation/scenario/conditional prompts, and the factual feedback boundary. Unchanged metadata, one required field, blank feedback intake, canonical links, and no technical-solution requirement still pass. Shared PowerShell lint reports 0 diagnostics. The failing test state remains local until the prose correction passes.

  12. MariusStorhaug commented on Nov 4, 2026

    @MariusStorhaug
    MemberAuthor

    The correction is committed locally as d879bd211cbc382bcc9f9c646ed8893ab4184aea, one small change with the coupled tests. All 13 tests pass with no skips or discovery failures; shared YAML and PowerShell lint pass with 0 PowerShell diagnostics. An independent PyYAML recursive comparison checks 20 nodes and 6 mappings against 5edc236cf2bc365931483487a5a0d471b3779629: exactly the introduction and field-description prose values differ. Every key/order/type/metadata value, label, canonical URL, field ID/required flag, single textarea, and blank-issue configuration is preserved. No new fields, policy, dependencies, or CI files are added.

  13. MariusStorhaug commented on Nov 4, 2026

    @MariusStorhaug
    MemberAuthor

    The writing correction is pushed at d879bd211cbc382bcc9f9c646ed8893ab4184aea; all three narrow writing-plan steps are complete. Before/after wording and verification are preserved in this Task and the linked dated PR evidence. The PR state and merge settings were not changed.

  14. MariusStorhaug commented on Nov 4, 2026

    @MariusStorhaug
    MemberAuthor

    The fixed Testing.md source is verified: new tests must not exist only to enforce prose phrases or source-string shape. The newly added direct-request/no-thanks It will be removed; its 7-pass/6-fail before-change result remains historical one-time evidence. The form prose is unchanged, and the final suite will return to its 12 existing tests with only coupled maintenance. The inherited exact-text suite is not asserted to fully align with the new testing rule.

  15. MariusStorhaug commented on Nov 4, 2026

    @MariusStorhaug
    MemberAuthor

    Final persistent candidate 589285cfb6c2ecc761c5308de4527d2dd2c54bd4 removes only the newly added prose-freezing It. All 12 maintained tests and both shared linters pass; the verified form prose and non-prose contract are unchanged. The provisional 13-test result remains historical one-time evidence, and the inherited suite tension with pinned Testing.md is explicit rather than described as full alignment.

  16. MariusStorhaug commented on Nov 4, 2026

    @MariusStorhaug
    MemberAuthor

    Final candidate 589285cfb6c2ecc761c5308de4527d2dd2c54bd4 has 12 passing maintained tests, clean shared lint, and a clean exact-head automated code-review round with zero inline comments. The dated before/after record preserves one-time writing evidence and explicitly records inherited testing-policy tension. PR state remains open/non-draft and GitHub auto-merge remains null; no settings or readiness gates were changed.

  17. MariusStorhaug commented on Nov 11, 2026

    @MariusStorhaug
    MemberAuthor

    The current Testing.md and all 119 lines of the added suite are reviewed. No owned-runtime coverage or conflicting content decision exists. All 12 cases pass before removal, but their purpose is to freeze source prose/shape. The user-directed policy correction removes the whole added file without a replacement and preserves the form byte-for-byte; the new plan and current merge hold are recorded in the body.

  18. MariusStorhaug commented on Nov 11, 2026

    @MariusStorhaug
    MemberAuthor

    Local commit 9a4da3a0dacf7cfc68cad80270884886bcdc1ad9 removes only the 119-line added suite. The final base diff is one form file, and form blob 19d6abbbf5b1a4a5b48ce5710be9f7e79f0be742 is unchanged byte-for-byte from 589285c. Fresh one-time inspection checks 20 YAML nodes/6 mappings, two body elements and one required textarea; all non-prose contract values match the original base. The exact published Super-Linter default (4ce2083, blob 2aa49bd1) yields 0 diagnostics/exit 0 for original, prior candidate and current form. Native GitHub Markdown returns exactly two links; both actual canonical pages return HTTP 200 and contain the expected heading anchors. No replacement test/tooling/config or hosted-validation claim is added.

  19. MariusStorhaug commented on Nov 11, 2026

    @MariusStorhaug
    MemberAuthor

    Current truth is refreshed for 9a4da3a0dacf7cfc68cad80270884886bcdc1ad9: the entire added snapshot suite is removed, with no replacement and no form-byte change. Historical passing-suite claims are no longer presented as current coverage. The body records exact static/rendering/link counts, published validator-default provenance, merged source guidance, current native review/check/protection evidence, and the exclusive global merge hold. No consumer-content decision is unresolved.

  20. MariusStorhaug commented on Nov 11, 2026

    @MariusStorhaug
    MemberAuthor

    Preparation is complete at 9a4da3a0dacf7cfc68cad80270884886bcdc1ad9: one form in the PR diff, preserved blob 19d6abbbf5b1a4a5b48ce5710be9f7e79f0be742, no added test/replacement, six zero-diagnostic normal/strict lint observations, native GitHub rendering and two live HTTP-200 page/anchor checks. The exact-head review approves with 0 threads; native state is CLEAN/APPROVED. Only the reviewer check executed, not Organization defaults validation. Protections are unchanged, GitHub auto-merge is null, Agent merge merge_pr=false, and no merge occurred while the exclusive global slot remains undelegated. No content decision is unresolved.

  21. MariusStorhaug commented on Nov 11, 2026

    @MariusStorhaug
    MemberAuthor

    Completed by the ordinary exact-head guarded squash of #15 on 2026-11-11. Accepted head: 9a4da3a0dacf7cfc68cad80270884886bcdc1ad9; squash/main: d9dbfaca73dd4accae141eb3d86b43f57a15a7a1; actual prior main: 8e57cad9bd6ae7e973aa566903239e732b3e3e21. Native pre-merge review was APPROVED at the exact head, with zero fully paginated threads and no failed or named required check. No admin, force, bypass, alternate approval, or settings change was used. Fresh YAML/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 change from prior main is the accepted feature form, blob 19d6abbbf5b1a4a5b48ce5710be9f7e79f0be742; the prohibited added snapshot suite is absent, all earlier README/contribution content remains exact, and zero recognized PR templates remain. The delivery leaf is closed and the exact remote topic branch is absent. No live submission, package, Pages, or consumer-rollout result is claimed.

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