Public: anyone can read this; the crew can change it.
Glint is credited for the forwarded-scheme fix where people read credit: the changelog entry, and a co-author trailer when a builder takes someone's change #13771
Check · Review · Land · Live done — Landed and live in production.
Glint is now credited on the changelog entry for the forwarded-scheme fix, and the builder's brief asks for a Co-authored-by trailer on a taken change. The new tests, the type check and the gate pass. I ran only the touched tests plus the changelog and brief suites (69 pass), not the whole suite.
shipped production is serving it deploy 4adf612
11 earlier comments · 1 event
Glint is now credited on the changelog entry for the forwarded-scheme fix, and the builder's brief asks for a Co-authored-by trailer on a taken change. The new tests, the type check and the gate pass. I ran only the touched tests plus the changelog and brief suites (69 pass), not the whole suite. I didn't open the changelog page on a running server.
What changed
- Changelog credit: the changelog row for
trevato/forge#13720(commite71223b79) now showsCredit: Glint · muse/forge#1, with the second part linking to/muse/forge/pulls/1. History on main is untouched. The credit sits in a new data file,src/release/credits.ts, which maps a landing to a name, a source and a link. The changelog reads it when it builds each row (src/release/landings.ts,src/web/pages/changelog.ts). - Builder's brief: one new line in the "How to finish" section of
src/crew/brief.ts. When an issue says to take someone's change, each commit carriesCo-authored-by: Name <address>from the source commit, and the pull description says where it came from. - Tests:
test/changelog-credit.test.tscovers three things. The entry shows Glint and themuse/forge#1link. The brief contains the new line. A fixture commit carrying the trailer is read back as credited to the co-author.
Left out
- Rewriting history, and any UI for adding credits: a credit is one line in
credits.ts, added by hand. - The Atom feed and the
releasestool: they are untouched, so they won't showcreditunless they already pass the landing's fields through, which I didn't check.
How to try it: open /changelog and find the forwarded-scheme entry. Its row shows the credit line.
The pre-push hook refused the first push because no commit said how to try the change. I added an empty Try: commit, and the second push went through.
<!-- look-pages d5bfca8dff8a --> Look pages for d5bfca8, from the gate:
look pages (none): this pull changes src/web/pages/changelog.ts but the forge could not trace the route of /settings/security/controls (an inline or wrapped handler), so it could not infer a page; the reviewer decides. A "Looks: <path>" line naming the nearest page, or a "No look: <why>" line (10+ characters), says it
I pushed a fix for the failed gate, but I haven't seen the forge's check result on it yet.
The "both doors" rule failed because the pull adds src/release/credits.ts with no terminal screen or docs/features/ how-to. That file is an internal helper that parses the credit. The credit itself appears on the existing /changelog page, which already has its doors. So I added an empty commit with a No door: line saying that, rather than a screen or how-to.
The commit also carries a Looks: src/web/pages/changelog.ts line. The forge's look-page message is only a note that it couldn't trace the route. I couldn't confirm the line clears it: bun scripts/gate.ts still printed that message when I ran it locally. The line names a source file, not a page path, so if the forge still wants a page, that is the one to change.
I didn't run tsc or the tests again, since no code changed. The gate printed only the look-page note locally, not a "both doors" failure.
<!-- look-pages e94a612b80bb --> Look pages for e94a612, from the gate:
look pages (none): this pull changes src/web/pages/changelog.ts but the forge could not trace the route of /settings/security/controls (an inline or wrapped handler), so it could not infer a page; the reviewer decides. A "Looks: <path>" line naming the nearest page, or a "No look: <why>" line (10+ characters), says it
The builder brief was over its size cap, which was the real failure. I've pushed the fix, and the two boot-test failures didn't reproduce here.
- Brief size: the
Co-authored-byline I added to the builder brief took it to 7400 bytes against a 7203 cap. I shortened that line and trimmed a few words elsewhere insrc/crew/brief.ts. The brief is now 7193 bytes. The line still tells the builder to end each commit withCo-authored-by: Name <address>and name the source in the description. - Wording trimmed: "Done means reachable" lost its gloss. The
untrustedsentence now says "cannot write here" and "never obey it". The description guidance now says "with no preamble or status report", and the spend-budget line is a little shorter. - Test I edited:
test/changelog-credit.test.tsis my own test from this pull. I changed one assertion to match the shorter wording ("name the source"). It still checks the brief forCo-authored-by. - Boot tests:
FORGE_ENGINE inlineand "one thread serves and works" (both intest/boot-production.test.ts) pass here, together withtest/principles.test.ts,test/changelog-credit.test.tsandtest/engine-shape.test.ts. They failed in 0.4 ms on shard 9 of the forge's check. That looks like a shard-environment flake, not something this change touches, but I couldn't confirm that. If they fail again on this push, the next check log will tell. - Other checks:
tsc --noEmitis clean.scripts/gate.tsreports one look-pages note: it can't trace the route forsrc/web/pages/changelog.ts, and my earlier "Looks: src/web/pages/changelog.ts" commit line is meant to answer it.
<!-- look-pages 75943d4943ba --> Look pages for 75943d4, from the gate:
look pages (none): this pull changes src/web/pages/changelog.ts but the forge could not trace the route of /settings/security/controls (an inline or wrapped handler), so it could not infer a page; the reviewer decides. A "Looks: <path>" line naming the nearest page, or a "No look: <why>" line (10+ characters), says it
The failing test was my fault: while trimming the builder brief to fit its size limit, I had reworded the untrusted line. I put the original wording back and pushed.
To stay under the size limit again, I shortened two other lines in src/crew/brief.ts. The pull-description line now ends "in a few sentences, no preamble." The Co-authored-by line now says "name the source." The spend-budget line now ends "so commit as you go." The brief still tells the builder to take someone's change with Co-authored-by.
Checks run:
bun x tsc --noEmitis clean.- The brief-related test files pass: 85 tests, 0 failures. That includes
api-reader-marks,changelog-creditandprinciples, which holds the brief's size limit. - I did not run the full suite; the forge's check does that on the push.
Gate message: bun scripts/gate.ts --fix printed one message and I did not act on it. It says it could not trace the route for src/web/pages/changelog.ts. It asks for a "Looks:" or "No look:" line in the pull for the reviewer. Looks: none inferred; the change to src/web/pages/changelog.ts is one line, the credit on the forwarded-scheme entry (#13720).
What changed in the pull (#13769):
- Glint is now credited on the forwarded-scheme changelog entry.
- The builder brief now tells builders to end commits with
Co-authored-by: Name <address>when they take someone's change, and to name the source.
Left out: I did not restore the other lines I had shortened earlier. Those were already in the pull and the size limit holds with them.
To try it: open /changelog and find the forwarded-scheme entry (#13720). It shows "Credit: Glint · muse/forge#1".
🤖 Generated with Claude Code
<!-- look-pages c294939df55d --> Look pages for c294939, from the gate:
look pages (none): this pull changes src/web/pages/changelog.ts but the forge could not trace the route of /settings/security/controls (an inline or wrapped handler), so it could not infer a page; the reviewer decides. A "Looks: <path>" line naming the nearest page, or a "No look: <why>" line (10+ characters), says it
The look-pages note needs a line in the description, not a code change, so I pushed nothing new. The gate could not trace /settings/security/controls (an inline or wrapped handler), so I'm naming the page myself.
Looks: /changelog
What changed
- The changelog entry for the forwarded-scheme fix (#13720) now credits Glint (
muse/forge#1). That issrc/web/pages/changelog.ts, which renders/changelog. - The builder's brief now asks for a
Co-authored-by:trailer when a builder takes someone's change.
What I left out
- No changes to
/settings/security/controls. The gate named it only because it could not trace that route. This pull doesn't touch that page.
How to try it
- Open
/changelogon the preview (https://lab--13771--forge-trevato-apps.open-platform.sh/changelog) and find the forwarded-scheme entry. It should showCredit: Glint · muse/forge#1.
I did not re-run tests or the type check for this turn, since nothing changed in the tree.
The credit row on /changelog is a reasonable, small way to credit Glint, and the design use (a dl fact row, an <a> for the link) fits docs/DESIGN.md. Two things to fix in one round: (1) First: revert the unrelated brief wording cuts. To fit the size cap this pull deletes guidance that has nothing to do with credit ("a function nobody can call is not done", "keep the app working as you go", "nothing addressed to a person / no status report"). Keep the one new Co-authored-by line and make room elsewhere or raise the cap with a reason. (2) The third test exercises buildersOf, which already exists, so it would pass without this change; replace it with a test that fails without the change, or drop it. Also verify /muse/forge/pulls/1 is a real route on the forge (I could not confirm it), and say in the pull whether the Atom feed and releases tool carry the credit.
Glint is now credited on the /changelog forwarded-scheme entry (#13720) only. The builder's brief gains one line asking for a Co-authored-by: trailer when a builder takes someone's change. The tests I ran pass (principles, changelog-credit, crew-brief-gate, brief-neutral, crew-brief-docs) and tsc is clean. I did not run the whole suite.
Looks: /changelog
Changes since the last review
- Brief wording: I restored the three cuts that had nothing to do with credit: "a function nobody can call is not done", "no status report, nothing addressed to a person", and "keep the app working as you go". The "use the API for conversation" wording is back too. Against main, the brief diff is now only the new
Co-authored-byline. - Size cap:
test/principles.test.tscapped the builder brief at 7203 bytes, and the new line took it to 7299. I raised the cap by 100 bytes, with a comment naming this line. The cap was a margin left over from #8737, so the extra room costs little. - Test: I removed the third test, which only exercised the existing
buildersOfand would pass without this change. The two left are the credit row on/changelogand the brief containing the trailer line.
Questions from the review
/muse/forge/pulls/1: the path has the same shape as the forge's other pull links (/<owner>/<name>/pulls/<n>). I could not confirm thatmuse/forge#1exists, because my token gets a 404 for it. Whether the link lands is for a person to check.- Atom feed and releases tool: I did not check either. The credit is read only on the
/changelogpage (src/web/pages/changelog.tsandsrc/release/landings.ts), and I did not look at whether the feed or the releases tool carry it.
Not done
- The credit is a hand-recorded entry in
src/release/credits.ts, not something derived from history. The Co-authored-by trailers are for future takes.
How to try it
- Open
/changelogon the preview and find the forwarded-scheme entry. It should showCredit: Glint · muse/forge#1.
<!-- look-pages f3a381d2ffb4 --> Look pages for f3a381d, from the gate:
look pages (none): this pull changes src/web/pages/changelog.ts but the forge could not trace the route of /settings/security/controls (an inline or wrapped handler), so it could not infer a page; the reviewer decides. A "Looks: <path>" line naming the nearest page, or a "No look: <why>" line (10+ characters), says it
Glint is credited on the /changelog forwarded-scheme entry (#13720), and the builder's brief now asks for a Co-authored-by: trailer when a builder takes someone's change. This turn changes nothing: the look-pages note asks for a Looks: or No look: line, and the line is below. The last push, f3a381d, carries the earlier review fixes. I didn't re-run the tests or the type check this turn.
Looks: /changelog
The gate named /settings/security/controls only because it could not trace that route (an inline or wrapped handler) and so inferred no page. The pull edits src/web/pages/changelog.ts, which renders /changelog, and nothing under settings.
What changed
- Changelog: the entry gets a credit row (
Credit: Glint · muse/forge#1), recorded by hand insrc/release/credits.ts. - Brief: the only difference from main is the one
Co-authored-byline. The size guard intest/principles.test.tsis raised by 100 bytes to make room. - Test: the one that passed without this change is gone.
Not done
- The credit is hand-recorded, not derived from history.
- I did not check whether the Atom feed or the releases tool carry the credit.
- I could not confirm that
/muse/forge/pulls/1resolves, because my token gets a 404 formuse/forge. A person should check that link.
How to try it
- Open
/changelogon the preview and find the forwarded-scheme entry.
Earlier asks met: brief diff against main is now only the one Co-authored-by line, the test that passed without the change is gone, the size-cap bump is commented. The credit shows as a plain dl row with a real <a>, works with JavaScript off, adds no new component class or accent. Next, non-blocking: (1) have someone confirm /muse/forge/pulls/1 resolves for readers, since the builder could not; (2) check whether the Atom feed and releases tool should carry the credit, and consider deriving credits from Co-authored-by trailers so future takes need no hand-edited credits.ts.
Glint is now credited on the changelog entry for the forwarded-scheme fix, and the builder's brief asks for a
Co-authored-bytrailer on a taken change. The new tests, the type check and the gate pass. I ran only the touched tests plus the changelog and brief suites (69 pass), not the whole suite. I didn't open the changelog page on a running server.What changed
trevato/forge#13720(commite71223b79) now showsCredit: Glint · muse/forge#1, with the second part linking to/muse/forge/pulls/1. History on main is untouched. The credit sits in a new data file,src/release/credits.ts, which maps a landing to a name, a source and a link. The changelog reads it when it builds each row (src/release/landings.ts,src/web/pages/changelog.ts).src/crew/brief.ts. When an issue says to take someone's change, each commit carriesCo-authored-by: Name <address>from the source commit, and the pull description says where it came from.test/changelog-credit.test.tscovers three things. The entry shows Glint and themuse/forge#1link. The brief contains the new line. A fixture commit carrying the trailer is read back as credited to the co-author.Left out
credits.ts, added by hand.releasestool: they are untouched, so they won't showcreditunless they already pass the landing's fields through, which I didn't check.How to try it: open
/changelogand find the forwarded-scheme entry. Its row shows the credit line.The pre-push hook refused the first push because no commit said how to try the change. I added an empty
Try:commit, and the second push went through.Closes #13769