Issues on mixed usage with private instance fields

While we define an identical private field name to a private declaration, although they are similar to normal instance field declarations, they behave differently on semantics.

private #hello;
const hello = 'hello';
class Example {
  #hello = 'crap!';
  [#hello] = 'world!';
  hello = 'crap!';
  [hello] = 'world!';

  sayHello () {
    console.log(this.#hello);
    // => 'crap!'
    console.log(this[#hello]);
    // => 'world!'

    console.log(this.hello);
    // => 'world!'
    console.log(this[hello]);
    // => 'world!'
  }
}

const ex = new Example();
console.log(ex.#hello);
// => 'world!'

Start with the mixed-usage example in this issue and compare its private and computed field access cases against the proposal's intended semantics. Determine whether the differing behavior is intentional and document the resolution in the proposal; no repository file or test is named.