Skip to content

contrib/inbox: learnings from a requirements-driven full build - #804

Open
markvanrooijen wants to merge 1 commit into
MendixMau:masterfrom
markvanrooijen:contrib/2026-11-19-usecasediscovery-learnings
Open

markvanrooijen wants to merge 1 commit into
MendixMau:masterfrom
markvanrooijen:contrib/2026-11-19-usecasediscovery-learnings

Conversation

@markvanrooijen

Copy link
Copy Markdown

Two harvest drafts for contrib/inbox/, written by bin/harvest-learnings.sh at the close of a full, requirements-driven build (Stage 7). Both were checked for client data before submitting: they hold the project name only, no script names, paths or people.

  • 2026-11-19-MendixUseCaseDiscovery-metrics.md: the exec trend over 136 runs (outcomes, speed, lint).
  • 2026-11-19-MendixUseCaseDiscovery-patches.md: three project copies of toolkit scripts were behind the shipped version (_common.sh, exec.sh, test-stack-up.sh). None had a local fix to bring back.

Bugs from the same project, filed separately: #802 (otel.js, Jaeger 2.x v3 API) and #803 (monkey.js scores HTTP 551 validation feedback as a crash); mxcli: mendixlabs/mxcli#1910.

🤖 Generated with Claude Code

…ild (metrics, stale-bin notes)

Co-Authored-By: Claude Opus 5.5 <[email protected]>
@MendixMau

Copy link
Copy Markdown
Owner

Outside PR check: MERGE. Two contrib/inbox/ harvest drafts, 43 added lines of markdown only. I read every added line. I did not run any code: the PR has none.

  • Safety: no hidden or bidi characters. The only non-ASCII characters are ·, — and →. There are no URLs, no code, and no instructions aimed at an agent. Nothing touches workflows, hooks or scripts.
  • Client data: each draft names only the project, MendixUseCaseDiscovery. There are no script names, paths, people or client names. check-pr-discipline is clean. The leak guard needs the repo's denylist, so CI will confirm it; no CI run is shown yet for this fork PR.
  • Value: real field metrics from a full requirements-driven build (136 execs). One signal is worth acting on: lint rose on 65% of execs, from 23 to 157 findings over two days. This belongs in the next inbox triage. The patches draft only says three installed scripts were stale, with no local fixes, so it can be deleted at triage.

Review: MERGE: inbox drop, which carries no quality bar under CONTRIBUTING. It is markdown only and safe. Context cost 0 words (not routed). Time cost none. Merge once CI is green.

Thanks @markvanrooijen, and for filing #802 and #803 with --auto.


Generated by Claude Code

@MendixMau

Copy link
Copy Markdown
Owner

Follow-up from the inbox sweep (#811). Both drops in this PR triage to DELETE:

  • the metrics file is a printout with no claim to promote;
  • the patches file is a stale-bin list with 0 local fixes.

Their key signal (lint rose on 65% of execs) is now recorded in the over-engineering audit. The filenames and the From: line also carry a project repo name.

Recommendation: close this PR unmerged and keep the name off master. My earlier MERGE verdict still holds on safety, but there is no remaining value to merge. Maintainer's call.

Thanks again @markvanrooijen. The field metrics fed directly into tonight's audit.


Generated by Claude Code

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.

2 participants