Does not respect configuration hooks

まず example codecept.conf.js と @codeceptjs/configure のフックを確認し、次に表示された設定とフックによって調整された値を比較します。UI が設定をどのように解析して表示するかを追跡します。setBrowser、setHeadlessWhen、setTestHost、setCommonPlugins などのフックで設定された構成が UI に表示されるか、その動作が意図的なものとして文書化されていれば完了です。

The UI does not appear to account for configuration set through hooks from @codeceptjs/configure.

As an example, I have the following codecept.conf.js:

const {
  setHeadlessWhen,
  setCommonPlugins,
  setBrowser,
  setTestHost
} = require('@codeceptjs/configure');

const productionHost = 'https://example.com';

setBrowser(process.env.BROWSER || 'chromium');
setHeadlessWhen(process.env.HEADLESS);
setTestHost(process.env.TESTHOST || productionHost)
setCommonPlugins();

exports.config = {
  name: 'example-ui-tests',
  tests: './integration/**/*.test.ts',
  output: './output',
  helpers: {
    Playwright: {
      show: true,
      waitForNavigation: 'networkidle',
    },
  },
  bootstrap: null,
  include: {
    I: './custom-steps.js',
  },
  require: ['ts-node/register']
};

When I run the UI and view the config, it's as follows:

{
 "output": "./output",
 "helpers": {
  "Playwright": {
   "show": true,
   "waitForNavigation": "networkidle"
  }
 },
 "include": {
  "I": "./custom-steps.js"
 },
 "mocha": {},
 "bootstrap": null,
 "timeout": null,
 "teardown": null,
 "hooks": [],
 "gherkin": {},
 "plugins": {
  "screenshotOnFail": {
   "enabled": true
  }
 },
 "stepTimeout": 0,
 "stepTimeoutOverride": [
  {
   "pattern": "wait.*",
   "timeout": 0
  },
  {
   "pattern": "amOnPage",
   "timeout": 0
  }
 ],
 "name": "example-ui-tests",
 "tests": "./integration/**/*.test.ts",
 "require": [
  "ts-node/register"
 ]
}

It doesn't seem to be applying any hooks to the parsed config. Is this intended behavior with a workaround or a bug?